Upgraded to piaware 10.1 and now I have two issues:
#1 - My 978 receiver is no longer working. How do I get the 978 receiver back online?
#2 - My DHCP reservation in my pfSense router does not work any more. I verified the MAC address of my piaware and it is correct. But my piware is pulling a DHCP address from the pool, not the address of the reservation. How do I get the reservation to be recognized by piaware? Or how do I set a static IP address in piaware?
Your router is assigning the address, not the Pi. Check into the router or whatever you use to assign DHCP addresses. Have fun.
Yes, the pi is getting the IP address from my router. But not the correct one.
My router has a DHCP reservation for: 192.168.20.20 linked to the MAC address of the ethernet adaptor of the pi. The pi somehow ended up with an address of 192.168.20.103, which is in the DHCP pool range.
Why is the pi pulling a DHCP address from the router and NOT the IP address from the reservation that is linked to the piās MAC address?!?!?
I HATE why updates break working configurationsā¦
Recently upgraded to 10.1 SD image and had no issues with static IP. I run pfSense (w/ISC DHCP backend) and have a static IP/MAC mapping. Pi3B provisioned with legacy IP address from pfSense router after booting from the reimaged SD card. I did have to edit /boot/firmware/piaware-config.txt to get the 978 receiver working again. All I did was copy relevant lines from the old file. Hopefully you have that available.
I have a DHCP reservation in my pfsense router, with the MAC address of the piās ethernet interface verified to match, of 192.168.20.20. The pi is pulling a DHCP pool address of 192.168.20.103 from the router. NO idea why the reservation, which has been in existence since I started years ago with piaware 7 (then 8 & 9), is no longer working. Multiple reboots, power off for a while & turn back on, always result in the same non reservation IP address of 192.168.20.103 after upgrading to piaware 10, using the same hardware (pi4) that 7, 8, & 9 have run on.
As setting for a static IP in the pi as a workaround, I have found no information on how to properly setup a static IP.
For the 978, I do not have the original config file. That was overwritten in reflashing the SD card with the āupgradeā to 10 and I did not think to find and save it. There was NO suggestion of saving the previous configuration in the update instructions, or where I was located. I didnāt think about it and expected the ānewā installation of 10 to work with both receivers like my original piaware 7 did when I installed it.
In Piaware SD Card version 8, the OS was Bullseye, which had dhcpcdas networking app, and static IP was set using it.
In version 10, the OS is Bookworm, which has Network Manager, and Static IP can be set iusing command sudo nmtui .
Please see my following post to setup Static IP using Network Manager:
This is also given in item (5) of my post linked above.
That was your first error.
Two obsevations about SD cards:
The considered opinion here is to remove / replace a working SD card before an upgrade so you have a working system to go back to if you are not happy with the upgrade. Starting with a zero-hour SD card gives you the best chance of longevity with your new install.
Iām a little unclear how your network is setup.
You have pfsense running on a Pi? And two dongles (ADS-B and UAT) running on a different Pi?
I donāt have a strong grip on the subtlies of DHCP, but as I understand it, nothing āpullsā an IP from the DHCP server.
Either it has a coded static IP, in which case it will use it regardless of any other device also using the same IP.
Or
The device powers up, anounces itself on the network and requests an IP.
The DHCP server hands out an available IP āfrom itās pool of available IPāsā
Different DHCP servers can behave slightly differently - this caught me when I changed routers and their behaviour was not the same.
The first could be configured to assign any IP to a specified MAC
The second (as highlighted above), would only assign an IP from itās pool.
Reservations on IP addresses in the router are always made inside the defined pool of IP addresses. Static device IPās should be defined outside of the DHCP scope in order to avoid conflicts on leasing IP addresses.
For example I have a DHCP scope of 100 IPās inside my network so the reserved addresses based on the MAC address of the device should be in that range of 100 IPās.
Static IPās are set outside of that DHCP addresses so they should start outside of that DHCP scope.
All is depending on model and make of the DHCP server, different suppliers can have different approaches. Some allow reservations for a small number of devices, others will allow none and linux based DHCP will usually allow you to make unlimited reservations, the last option allows you to create the complete reservation system on one spot.
I think the router doesnāt know your piās MAC address because it canāt find it, as you have described.
Assign a static IP address to your pi through your router. And, donāt forget to make the commensurate changes in your piaware config dot text file.
wireless-type static
wireless-address 192.168.1.xxx
wireless-netmask 255.255.xxx.xxx
ā¦using your unique addresses. Save and restart piaware.
It took me about fifteen or so reboots ā¦ kidding. 