Configure RPI Internet Access
In order to issue git clone or git pull requests needed to install the repositories we use to control the test stand, the RPi needs to have access to the internet. Additionally, for operator control to work, the RPi needs to have an assigned IP address so that information and commands can be passed. This page assumes the use of an ethernet cable to connect the controlling (Windows) PC and the RPi created in earlier steps of this guide.
In order to provide an IP address to the RPi, the PC needs to act as a router on the network interface that the RPi is connected to. We will be using a 3rd party piece of software to do this named TFTPD because the Windows DHCP server is not configurable enough to reliably assign an IP.
Download Tftpd64-4.64-setup.exe here
While TFTPD64 will manage the IP address pool, we still need to enable the network interface as a server. Navigate to your internet adapter settings. One way to do this is to right click on the internet icon on the taskbar and click Open Network & Internet settings and then Change Adapter Options in the window that opens.
The connection of interest will be labeled Ethernet X:
Right-click it and open Properties, and then click on Internet Protocol Version 4 (TCP/IPv4) in the list in the new window. Click on Properties.
This is the window where we can configure the server hosted on this network interface. Normally, Obtain an IP address automatically acts as a DHCP server, but because we need to manage our IP address pool more directly, we need to configure things so they match our settings elsewhere. Tick 'Use the following IP Address' and enter the following settings:
IP Address: 192.168.137.1
Subnet Mask: 255.255.255.0
The IP Address is the address of the 'router' we are making, and it must share the same first 3 octets of information as all devices it is hosting. This setting restricts the RPi to having an IP Address of 192.168.137.XXX. The subnet mask is default.
You may optionally configure an alternate DNS such as Google's 8.8.8.8.
Now that we can manage the Windows DHCP more directly, open TFTPD64 (preferably as administrator to save your settings for the next usage).
Navigate to the DHCP tab in Settings, and apply the following settings:
IP pool start address: 192.168.137.10
Size of pool: <At least 5>
Lease (Minutes): 2880
Def. Router (Opt 3): 192.168.137.1
Mark (Opt 1): 255.255.255.0
Under DHCP Settings, tick Bind DHCP to this Address and select 192.168.137.1 in the drop-down. It should now look (roughly) like this:
Press OK, and now the PC should be configured. You can use the Log Viewer tab to verify that there is network activity when the RPi is plugged in, and the DHCP server tab to manage what IPs in the manageable pool are in use. Right-click an IP to release it so that it is free for the RPi if if acquires the wrong IP.
A DHCP server handles connections from clients and assigns them an IP. We expect the RPi to be reachable at a particular IP, but cannot use static IP with a DHCP server, so we need to enable the RPi to request a particular IP from the DHCP server.
This is a thorough guide to setting up RPi networking
SSH into the Pi.
Without a requested IP, the Pi may be assigned an IP outside the TFTPD pool:
If you run the command cat /etc/network/interfaces you should see the following:
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source /etc/network/interfaces.d/*
Run the command sudo nano /etc/dhcpcd.conf to edit DHCP behavior of the RPi and add the following to the end of the file:
interface eth0
request 192.168.137.10
Use CTRL+x and save the modified file. Now the Pi will request the correct IP when connecting to a DHCP server, and receive it if the DHCP server is configured to have that IP available. Use sudo reboot, SSH back into the RPi, and then run ifconfig again to verify this.
The RPi now has an IP, but no access to the internet. You can confirm this by running the command ping 8.8.8.8 and watching it time out (use ctrl+c to escape this early):
Back on the host PC, return to the adapter settings. This time open the properties of the connection providing internet to the PC. Navigate to the Sharing tab. Tick Allow other network users... and select the Ethernet connection from before as the Home networking connection drop-down.
Do note that for some reason, when the RPi is disconnected from the PC, the internet sharing needs to be restarted. Do this by entering the properties, unticking the box, hitting OK, then reopening properties and reticking the box.
If done correctly, running the ping 8.8.8.8 command should return something like:
