Duplicate DHCP Leases?
-
@doktornotor I'm done responding to you. You're not helpful, you're down right abusive.
Huge props to JohnPoz for taking the time and listening and trying to help me.
Thanks Johnpoz!
-
So where the heck did your interface names go? The screenshots do not look like what you've shown on any normal system. There's interface name in the breadcrumbs. And interface name in the header below. What help you expect when you actively sabotage providing even the absolutely basic info?
-
dude showing us dhcp edit static mappings menu list is not really showing us anything.. Can you show us the lease your clicking the add static button on. So I deleted the existing lease I had with that same name for my other phone (just got a new one) Yes if I click into an existing lease to create a static it takes me me to the create static page - but you will notice its lists the dhcp server/interface that IP is in.. So my wlan is 192.168.2.0/24
So when I create the lease to create a reservation off the leases page, it takes me to that dhcp server edit static pages. So I then create the lease without giving an IP and it lists it there in the static leases for that dhcp server.. It will then not let me create another static lease with an IP for that same name.. Because a lease already exists with that name.
Your screenshot is not showing you what interface your on??? So is this lease your trying to create the static from a dhcp server that your no longer running?? See my screenshots when I click to add static lease from the dhcp leases page it takes me to the dhcp server that IP belongs too.
If I had to guess, you had an OLD lease that was for a dhcp server that was removed or disabled? Not sure I would call that a bug??
I would suggest you delete any old leases from dhcp servers that no longer on your system. And the try and duplicate.. Your saying when you click a lease that is within a dhcp pool of your dhcp servers it takes you to a create static page that does not list your dhcp server?? See the highlighted sections of my pics
BTW: Dok is a one of the good guys.. He is very helpful and very very knowledgeable not only with pfsense related but pretty much all things IT related.. His post can sometimes come off a bit gruff for those that have not been reading his posts for a long time ;) But I love is fun loving easy going demeanor.. And while he was on a break from this board, he was for sure missed by many of us here. And I for one am very glad he is back, and true to form posting in his straight to the point no holds bar blunt honest opinions that make it so refreshing than most of the drivel and pansy nonsense you read elsewhere. Most likely was tired of having to pull teeth for info, and tired of obfuscated nonsense like hiding a mac, or a rfc1918 address or a hostname when dealing directly with that sort of info ;) I would take his posts to heart, read them in the fun loving way he intends and you will for sure come away with loads of valuable info!!
-
This (Diagnostics => Command Prompt) provides a pretty readable overview of what's configured where
foreach ($config['dhcpd'] as $iface => $leases) { $ifname = convert_real_interface_to_friendly_interface_name($iface); $ifname = convert_friendly_interface_to_friendly_descr($ifname); echo "Static leases on $ifname ($iface):\n"; print_r($leases['staticmap']); }
however since all this information is top secret classified stuff, we won't ever get the output anyway…
-
That is pretty slick dok! And would be very informative to see that output.. But like you said its all top secret.. The black helicopters are most likely circling our houses now for even seeing the redacted output he did post ;) heheeh
-
After going back and looking at my upload, I captured the same screen shot twice and for that I apologize. Please look at these two unedited screen captures.
As for Dok, you can be the smartest guy on the planet but if you can't interface with people you aren't going to get anywhere. Especially when you are trying to help. I work in the customer support industry as do most of us on this forum I'm sure. I have peers who can't relate nor talk to customers and then I have those peers who can. Those who can communicate and discuss issues with customers/client get higher marks and survey results and are much more respected by their clients and management then those who can't.
Not trying to slam you but just making an observation. You can catch more flys with honey then you do with vinegar.
![Status - DHCP Server (Missing Interface).JPG](/public/imported_attachments/1/Status - DHCP Server (Missing Interface).JPG)
![Status - DHCP Server (Missing Interface).JPG_thumb](/public/imported_attachments/1/Status - DHCP Server (Missing Interface).JPG_thumb)
![Services - DHCP - Interface is listed.JPG](/public/imported_attachments/1/Services - DHCP - Interface is listed.JPG)
![Services - DHCP - Interface is listed.JPG_thumb](/public/imported_attachments/1/Services - DHCP - Interface is listed.JPG_thumb) -
What's up with that VLAN1_DBM_PC? It's not assigned, or what?
-
It is assigned. What I was attempting to point out was the blank interface at the top.
-
Ok that is weird, how come its not showing the interface its on in the top menu?
Don't you DARE try to change dok's style!! I agree many of here most likely work in the tech sector and have to put up with customers.. And have to play all nicey nice, etc. When most of the time you just want to scream through the phone listen up you F'ing Moron.. I can not make it any more clear.. Did you finish 3rd grade? ;)
The nice thing about public forums - is you don't have to pretend your talking to a 13 year old girl on her first period. You can be straight and to the point, and hopefully the other person is another techy person and gets it, etc..
I find Dok's posts refreshing and fun to read, you can only slap so much perfume on a pile of shit.. Its still going to be a pile of shit.. So its nice to communicate and exchange information without all the freaking honey and perfume stinking up the place. If its shit, then its shit - but atleast you know what your dealing with ;)
-
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!