Sending DHCP NACK by default to out-of-range "requested IP address"
-
Yeah, so you are using a broken OS produced by MS and ranting at pfSense forum. Makes a lot of sense. NOT!
-
Yeah, so you are using a broken OS produced by MS and ranting at pfSense forum. Makes a lot of sense. NOT!
I'm not ranting. You are, right now.
My objective was mainly to discuss whether or not the behaviour I've observed really is non-compliant or just weird (it makes a big difference, you know), and whether the addition of the discussed option to pfSense would make sense. You could have noticed that by reading my first post, which explicitly mentions that I've already found a solution.
So you are just here to bash on me and you don't intend to add anything to the discussion. Makes a lot of sense. NOT! -
Here's a work around, but it will require some effort of your part. Since it tries to use the previous address in the same subnet, then perhaps you can force it temporarily to use a different subnet. You can do this either by temporarily changing the subnet in psSense and causing each computer to release/renew or just grab a cheap router, configured for a different network, and then connect each computer to it, then put them back on the real network.
BTW, I have been working with networks for about 20 years and have often found MS breaks things.
-
Here's a work around, but it will require some effort of your part. Since it tries to use the previous address in the same subnet, then perhaps you can force it temporarily to use a different subnet. You can do this either by temporarily changing the subnet in psSense and causing each computer to release/renew or just grab a cheap router, configured for a different network, and then connect each computer to it, then put them back on the real network.
BTW, I have been working with networks for about 20 years and have often found MS breaks things.
Thanks for the suggestion, but as I've mentioned in the original post I already have a functioning workaround which is arguably more viable.
