Factory reset on 2.2.6 DHCP leases do not show on status page.
-
As discovered here : https://forum.pfsense.org/index.php?topic=97204.0 , Diagnostics: Factory defaults will propose two NIC devices, probably wrong (as you already discovered).
A third NIC (OPT1) etc will not receive any initialization, so 'DHCP' isn't even possible (NO IP, no mask, not range, nothing).
Before using OPT1, you have to set it up.I advise you to 'read' the file I showed you in the other thread. It will explain things ;)
-
Hmmm, and? Go reconfigure the DHCP server? It's not like any settings survive your "clean" upgrade.
I DID reconfigure. Simple settings. See attached screen shots. It is giving out addresses, it is just not showing them on the status page.
 -
As discovered here : https://forum.pfsense.org/index.php?topic=97204.0 , Diagnostics: Factory defaults will propose two NIC devices, probably wrong (as you already discovered).
A third NIC (OPT1) etc will not receive any initialization, so 'DHCP' isn't even possible (NO IP, no mask, not range, nothing).
Before using OPT1, you have to set it up.I advise you to 'read' the file I showed you in the other thread. It will explain things ;)
I did set it up. Why would you assume I did not set it up?
-
Why would you assume I did not set it up?
Why would anyone assume you DID set it up from this? - "reset a 2.2.3 to factory defaults, then installed 2.2.4."
-
…...it is just not showing them on the status page.
I PRESUME this page Status: DHCP leases (right ?).
Did you have a look at the Status: System logs: DHCP - do you see any DHCP server activity, like requests (like DHCPDISCOVER) coming in on your OPT1 NIC - you can recognize them because IP's like 10.0.0.1xx will be dealt out) ?Edit : Any firewall rules on your OPT1 ?
-
Why would you assume I did not set it up?
Why would anyone assume you DID set it up from this? - "reset a 2.2.3 to factory defaults, then installed 2.2.4."
I'm not sure if you are aware, but there is a character limitation to the post title, and I could not fit in "configured after clean install". I'm really sorry that I did not spell that out if it led to the conclusion that I did not configure the DHCP server.
Now that we have established that, is there any particular reason the system would not show the leases on the status page?
-
Probably because the DHCP server didn't dealt out any IP's yet …. ;)
See also my previous post.
-
…...it is just not showing them on the status page.
I PRESUME this page Status: DHCP leases (right ?).
Did you have a look at the Status: System logs: DHCP - do you see any DHCP server activity, like requests (like DHCPDISCOVER) coming in on your OPT1 NIC - you can recognize them because IP's like 10.0.0.1xx will be dealt out) ?Edit : Any firewall rules on your OPT1 ?
It shows the server handing out addresses on the OPT1 net in the log. I just have your bog standard IPv4 to any rule on the OPT1.
-
Probably because the DHCP server didn't dealt out any IP's yet …. ;)
See also my previous post.
It handed out several IP addresses already.
-
I just have your bog standard IPv4 to any rule on the OPT1.
Like the one shown here https://forum.pfsense.org/index.php?topic=97025.0 (message number #5) ?
If yes, Apply message number 6 ! -
I just have your bog standard IPv4 to any rule on the OPT1.
Like the one shown here https://forum.pfsense.org/index.php?topic=97025.0 (message number #5) ?
If yes, Apply message number 6 !That is not relevant.
-
About 30 minutes after the DHCP server handed out addresses on the OPT1 interface, the leases finally show up on the DHCP status page. Anyone seen this behavior before?
-
The file on disk with all the leases is rewritten rather often by the pfSense DHCP -server.
I tend to say: every time it deals out a new lease.
You can see for yourself when it is doing so in the Status: System logs: DHCP page.
I'm pretty sure it's far more often then "after a 30 minutes delay" ….. that doesn't seem normal to me.You're running pfSense on what kind of device ?
-
The file on disk with all the leases is rewritten rather often by the pfSense DHCP -server.
I tend to say: every time it deals out a new lease.
You can see for yourself when it is doing so in the Status: System logs: DHCP page.
I'm pretty sure it's far more often then "after a 30 minutes delay" ….. that doesn't seem normal to me.You're running pfSense on what kind of device ?
APU platform with msata SSD.
-
UPDATE:
if you use
System> Advanced> Miscellaneous> Use RAM Disks
PFsense will not show your DHCP leases in the GUI until the "Periodic DHCP Leases Backup" initiates at the set time.
-
Sounds like you might have a bug there.
Have you been able to tell if the GUI display updates ONLY at the backup interval or definitely at the backup interval and then upon changes afterwards?
If you set the "Periodic" time down to a short interval (I'm guessing that's how you found this one) it should be possible to see/force a lease expiry and track the issue.
Unfortunately I don't have a nano setup to test on.I'd say it's worth a post to:
https://redmine.pfsense.org/projects/pfsense/issues?set_filter=1
for Ver 2.2.5
Thanks for you efforts tracking this one…...
-
I just did a "factory defaults" in 2.2.6-RELEASE and am seeing the same thing. The leases show up in the DHCP log, but not on the status page. It is not just for OPT1, this is also on the LAN interface.
-
Hi,
I can confirm this behaviour after doing a configuration restore on a fresh installed 2.2.6 system.
DHCP works fine, is churning out DHCP leases, logs correctly to the system log but dhcp leases page is not updated accordingly.
