New answers tagged


On the Pi, you have to bind the socket to an IP address of one of the Pi's interfaces. You cannot bind it to the PC's IP address. If you want the socket to accept connections from all of the Pi's interfaces, you can use the IP address (or :: in IPv6). On the PC, the server IP should be an IP address that the Pi is bound to. Let's say the Pi is ...


With DHCP enabled, if all is otherwise well, your Pi should get an address on your local network. You will be able to see it in your router's tables or as raspberrypi.local assuming your phone is mDNS-capable. You now need to configure your microSD card to start SSH on boot. The "start SSH" part is covered in the link I posted in the comments. You want ...


I think your issue is having more than one static router defined in /etc/dhcpcd.conf. I got it working by following sudo apt-get install vlan Then sudo nano /etc/network/interfaces.d/vlans auto eth0.2 iface eth0.2 inet manual vlan-raw-device eth0 Then nano /etc/dhcpcd.conf and add interface eth0....


This is often a problem when upgrading your pi. Try to restart, and if it doesn't help, try to ping of, and give us results Edit: post result of: ifconfig Probable solution: I can't see any IPv4 in ifconfig, so it probably doesn't exist, which means you cannot connect to server with IPv4

Top 50 recent answers are included