Duplicate DHCP Leases?
-
JohnPoz, I wish I knew why but I don't. Been blowing my mind though. I think that relates to the root of my issue.
-
So are they shown under the proper interface when using the above script?
-
I did try the above script but no I do not see those entries under any interface. Which is what's throwing me for a loop.
-
Well, then look at the config.xml. Your configuration just appears badly broken somewhere.
-
If they are getting put back on reboot.. Then they HAVE to be in the config xml.. But yeah I would look to see what is causing your dhcp servers static to not show its interface.
-
So looking at the config.xml for the DHCP section, which BTW: is very cool you can download specific sections (thanks doktornotor), I think I found a clue.
There is a <lan>section, <opt1>section, <opt3>section, and <opt4>section. . .
The ranges for <lan>and <opt1>are NOT exclusive, which I'm not sure how this could be the case. (Full disclosure I inherited this and it's sister box from another tech guy)
Those phantom entries which I cannot remove from the gui are under the <opt1>section, the static entries which are in the <lan>section are under the range that is showing up in the gui.
So since this is a production box, my question becomes, can I just remove that <opt1>section from the downloaded xml file and then upload it to the pfsense installation and in theory everything would work?</opt1></lan></opt1></opt1></lan></opt4></opt3></opt1></lan>
-
I don't recall dok showing you that you could download different sections - that was me ;) heheh
But yes you should be able to delete the sections you don't want and then restore that portion of the xml.
-
Sorry johnpoz, that's my bad! Thank you for showing me that! Can't say I ever really bothered clicking on the drop down cause I always wanted to do a full backup!
So, I think I found a clue to all of this. There are two interfaces that have the same IP on them. LAN_EM1_DBM and VLAN1_DBM_PC. I'm willing to bet my predecessor didn't realize that the default vlan is 1 and didn't have to carve out a seperate vlan1. So the <lan>interface is really LAN_EM1_DBM and <opt1>is really VLAN1_DBM_PC. I'm betting if I remove VLAN1_DBM_PC from VLAN and delete the interface everything should keep using LAN_EM1_DBM and that would remove the ghost entry from DHCP Services which would make the behavior of STATUS DHCP correct. What do you think?</opt1></lan>
-
So that was the issue. Because the vlan1 was assigned as an interface it had a dhcp server that was running a conflicting set of pools for the 192.168.0.x address range which there was already a DHCP server running for LAN_EM1_DBM (which is another interface).
HUGE HUGE HUGE Props to Johnpoz for taking the time and working thru this with me.
Thank you to doktornotor for trying to help me, even though we never really did reach a level of communication.
I've said it before, and I'll say it again. pfSense is a great product! Just works and works well.
Thanks for all the help everyone!
