Tag Info

Hot answers tagged

3

If both the modem and the Raspberry Pi are on the same logical network (e.g. no NAT or routing is involved) then your Raspberry Pi cannot act as a gateway, because it is inside the only network available, and the actual gateway is your modem. This is the case if your modem has an address (say 192.168.1.1/24) and your RPi/computers an address in the same ...


2

I found this thread and this thread that both seem to have a solution. Looks like you may need to use the USB barcode scanner in Windows at least once for some reason. So here are the key steps from this thread: Download and install the Symbol Virtual COM Port Driver on a Windows box or VM. Configure the scanner to do “Simple COM Port Emulation” using ...


1

The file located inside the /home/myusername/ is the one which will be used every time you start a bash session. The file located in /etc/skel/ will be used as a template to create .bashrc files for any new users that are created on the system.


1

Yes, I finally did it, bloody hell! Well, if someone will encounter with similar problems, here's a solution: Download DHCP Server for Windows. It is a 100kB download available here. Go to the IPv4 properties page of the Ethernet adapter and set a fixed IP address, say 192.168.2.1 Run the DHCP Server Wizard (downloaded above) Select the Ethernet adapter ...


1

You can use screen or tmux for that. I would prefer tmux. What tmux does is basically create different tmux sessions which keep on running even if you close your ssh session. When you reconnect later, you can re-open that session and you will see that everything is running fine. This is a standard practice while using ssh. For an even better interface ...


1

As already mentioned, you can use a software like tmux or screen to start a shell and keep it running detached, but you could also use the nohup cmd to start your processes and keep them running even without any open session on the rasp.


1

You need to forward port 80 to the Raspberry Pi at the router. This tells the router that any client connecting to 162.255.119.254:80 (the default http port) should be redirected to the corresponding port on 192.168.0.10 (in this case, 8001). Depending on the brand of your router, the option to forward ports may be listed as "Forwarding", "Virtual Servers", ...


1

There's different check to do: If you have a monitor that you can connect on the raspberry open a command line on the raspberry and Check its IP with ifconfig or ip addr. Is it really 10.190.135.xxx that you want to connect to. Check that you can ping your gateway and the pc you want to connect from. If you installed iptables check with sudo iptables ...



Only top voted, non community-wiki answers of a minimum length are eligible