Figured I’d share this here, but I’ve made a backup of my Raspberry Pi 4 (arm64) SD card. This is an almost completely vanilla installation of Raspbian Lite (arm64) with modifications to:
- Assign DHCP addresses to clients connected on eth0 and wlan0 (bridged to br0)
- Broadcast an AP (DALTZ-TESTBENCH)
- Password is “daltzbench” (no quotes)
- SSH credentials is
pi
with 1 empty space as the password. (" ") - Static IP set to
10.0.66.1
- Assigns DHCP addresses within range
10.0.66.2
-10.0.66.200
Users may want to change the IP range and AP credentials. Users must ensure the static IP of the Pi matches the DHCP range being handed out.
To change the IP range
- Edit
/etc/dnsmasq.conf
, replacing10.0.66.2,10.0.66.200,255.255.255.0,12h
with whatever you want the IP ranges to be assigned to - Edit
/etc/network/interfaces
, replacingaddress 10.0.66.1
with the same10.XX.XX
you did in the previous step
To change the AP details
sudo nano /etc/hostapd/hostapd.conf
- Modify
wpa_passphrase
andssid
with the credentials you want
After everything is all done, reboot. If in a bad state, reflash the image and try again.
Additional remarks
If code (such as LL or Photonvision) relies on the Rio being 10.TE.AM.2
, it will not work properly. To get this to work properly, you can static IP the roboRIO to be a .2
address. MDNS should work just fine.
Oh, and obviously this isn’t competition legal. It probably has horrible latency issues at any sort of a distance and is prone to the SD card randomly borking itself.