{"id":737,"date":"2023-07-06T23:26:41","date_gmt":"2023-07-06T22:26:41","guid":{"rendered":"https:\/\/www.hilltop-cottage.info\/blogs\/adam\/?p=737"},"modified":"2023-08-10T23:44:04","modified_gmt":"2023-08-10T22:44:04","slug":"connecting-a-raspberry-pi-etc-direct-to-a-pc","status":"publish","type":"post","link":"https:\/\/www.hilltop-cottage.info\/blogs\/adam\/connecting-a-raspberry-pi-etc-direct-to-a-pc\/","title":{"rendered":"Connecting a Raspberry Pi (etc) Direct to a PC with a USB-LAN Adapter"},"content":{"rendered":"

There are a number of articles on the web which describe how to connect a Raspberry Pi direct to a Windows PC with a USB to LAN adapter. This can be quite handy when tinkering, especially with an original version 1. This article is quite good<\/a> but I struggled to make it work. This article explains the problem and solution… but read that article first, as I don’t explain a few things!<\/p>\n

The root of the problem is that I was using a USB to LAN adapter. It appears that Windows (Windows 11 at least) does not trust these devices because the network is fixed as being “Public”; I could not find a way to change this. The second part of my initial downfall was that when TFTPD64* started up, and Windows Firewall popped up the “public or private network” challenge, I thought nothing of allowing it to proceed with “private”. Thus, the firewall is between my USB-LAN dongle and the DHCP server.<\/p>\n

* – an alternative is OpenDHCPServer.<\/p>\n

If, like me, you missed the chance to choose “public” when starting the DHCP server software, you need to find your way into Windows “Settings”, then “Privacy & Security > Windows Security > Firewall & network Protection > Allow an app through firewall” (take a breath)… click the “Change settings” button then scroll down the list and enable the entry for tftpd64 or opendhcpserver for “public”.<\/p>\n

Oh: one thing which the article above was not clear on was to use a different subnet ip address for the USB-LAN dongle than the PC is on. e.g. if your PC is 192.168.1.4, don’t use any 192.168.1.* address for the static IP entry.<\/p>\n

And What About Internet Connection?<\/h2>\n

While the procedure in the above-mentioned article is fine for accessing the Pi from your PC, as soon as you need to access the internet from the Pi, it is aparrent that you can’t! Network interactions time out because there is no route for network traffic from the dongle adapter to the PC’s LAN\/WiFi.<\/p>\n

This is easily solved using “Sharing”. First thing: shut the Pi down. Starting with your PC’s “real” network adapter, right-click > Properties > Sharing (tab) > select the top “Allow” and choose the dongle for “Home networking connection”.<\/p>\n

This will change the dongle’s IP addres so a return to TFTPD64 will be required to change settings, after which the Pi can be powered on again to get its new IP address. Changed settings I used:<\/p>\n