1
20.1 Legacy Series / DHCPv4: Leases Page Appears Not to Update Reliably
« on: March 18, 2020, 06:33:18 am »
Recently converted my pfSense host to OPNsense 20.1.2-amd64 and am trying to acquaint myself with operations and the GUI.
BLUF: Sometimes the DHCPv4 Leases page updates as expected, but sometimes not. In some cases, even when a client picks up the IP I have defined in the static table, the Status column in the Leases table sometimes indicates an offline condition rather than online - even after the client picked up the correct IP, and the client is operational and serving up its webpages on the expected IP.
Details: Originally I had the intended network particulars (IP address, mask, gateway) "hard-coded" into my Canon printer. Today, I changed the configuration of the printer so it would obtain settings from the network but immediately thereafter the printer came up with some goofy IP and mask settings, so I dug deeper and discovered that the printer had to be configured to look for the "DHCP" protocol in particular (several other automatic configuration protocols were available). After setting the printer to use DHCP, and cycling power, the intended IP was picked up from OPNsense.
Even after refreshing the browser Leases page, clearing browser cache, and even trying a different browser entirely, the Leases page still shows the printer offline, even as I was able to call up the printer's own webpage.
Of course, in the time it has taken to draft this note, and changing nothing else, NOW the Canon is showing as online.
I've seen this offline/online indicator issue with other clients as well, but the Canon offered an opportunity for detailed testing.
Is this a known issue? If so, apologies, I did look around for pre-existing posts. Thank you.
BLUF: Sometimes the DHCPv4 Leases page updates as expected, but sometimes not. In some cases, even when a client picks up the IP I have defined in the static table, the Status column in the Leases table sometimes indicates an offline condition rather than online - even after the client picked up the correct IP, and the client is operational and serving up its webpages on the expected IP.
Details: Originally I had the intended network particulars (IP address, mask, gateway) "hard-coded" into my Canon printer. Today, I changed the configuration of the printer so it would obtain settings from the network but immediately thereafter the printer came up with some goofy IP and mask settings, so I dug deeper and discovered that the printer had to be configured to look for the "DHCP" protocol in particular (several other automatic configuration protocols were available). After setting the printer to use DHCP, and cycling power, the intended IP was picked up from OPNsense.
Even after refreshing the browser Leases page, clearing browser cache, and even trying a different browser entirely, the Leases page still shows the printer offline, even as I was able to call up the printer's own webpage.
Of course, in the time it has taken to draft this note, and changing nothing else, NOW the Canon is showing as online.
I've seen this offline/online indicator issue with other clients as well, but the Canon offered an opportunity for detailed testing.
Is this a known issue? If so, apologies, I did look around for pre-existing posts. Thank you.