Bug #10974
closed
pfSense showing unspecified DHCP assignment range
Added by Mark Whitworth about 4 years ago.
Updated about 4 years ago.
Affected Architecture:
i386
Description
pfSense is assigning addresses from 2 ranges in my VLAN_GUEST space. Some time ago I used that .90-.191 range, but not for some time and as you can see the ranges I've defined are consistent. I'm guessing some old garbage somewhere. Restarting, changing the specified range, etc, hasn't fixed it.
So I confirmed this morning it is still doling out leases in that range after I'd manually deleted them all last night. I had gotten a response i the forum I hadn't seen, and following the steps here it still sounds like there is a bug and some cleanup that didn't happen during some change.
Searching the config.xml, there are references to a opt7 interface that I believe is deprecated. There are approximately 30 contiguous lines that appear to speak only to that DHCP range and associated entries. When I shell in the console reflects opt1-op6 for my 6 specified VLANs.
- Project changed from pfSense Packages to pfSense
- Category set to DHCP (IPv4)
- Status changed from New to Rejected
- Target version deleted (
2.5.0)
Jim Pingle wrote:
This site is not for support or diagnostic discussion.
For assistance in solving problems, please post on the Netgate Forum or the pfSense Subreddit .
See Reporting Issues with pfSense Software for more information.
It wasn't inteneded for support as much as notifying that this unexpected and unintended behavior appeared, and no one has provided any reason as to why. I was willing to help with the investigation, but it's working fine with my changes so hopefully others can at least find this item when they encounter this issue.
That's why the forum is the best place to discuss and diagnose the issue. This isn't the place to bring up "unexpected and unintended behavior" that you can't explain and maybe just don't understand. On the forum you can have a dialog about what's happening, why, and so on. If it does turn out to be a bug, then an issue can be opened with much more specific detail.
Also available in: Atom
PDF