Is this a bug or a very needed feature? Changing interface LAN IP locks use out!
-
I'm guessing something changed since the introduction of 2.x. When I first started using it, I remember not being able to change the DHCP range until applying the LAN settings. I started using the console to change the LAN when staging a box and haven't tried it since. I just checked on 2.1 and it indeed works fine.
<rosannerosannadanna>Oh, Ok. Nevermind</rosannerosannadanna> -
If you are doing it remotely, you don't have to care about losing your LAN IP before you change your DHCP settings. If you're local, use the wizard. Nothing scary about it, it will fill in the current settings as you go.
As others have pointed out if you follow the procedure as noted, it works. See the post a few up by phil.davis. It works fine if you do it that way locally.
Jimp: as a very active user of pfSense I and others on this thread have tried to give input on this broken process (to my opinion). It's up to devs to decide whether this takes priority or not. There is enough reason for it to work in a simple way and to allow everyone to enjoy the feature without headache. I DO know how to change LAN subnet using the current procedure and I DO know how it works but that is NOT the point of this thread.
Thanks for all the input.
-
It is fine as is. Let's say I have a 192.168.0.0/23 interface, and only have a DHCP scope defined for 192.168.1.0/24. If I decide that I only need a /24 and change my interface address to 192.168.0.0/24, what should happen to that DHCP scope? Should it automatically be changed to 192.168.0.0/24? What if there's something on that range conflicting? There are too many variables to have it automagically switch the scopes, because there is no mind-reader module yet.
-
It is fine as is. Let's say I have a 192.168.0.0/23 interface, and only have a DHCP scope defined for 192.168.1.0/24. If I decide that I only need a /24 and change my interface address to 192.168.0.0/24, what should happen to that DHCP scope? Should it automatically be changed to 192.168.0.0/24? What if there's something on that range conflicting? There are too many variables to have it automagically switch the scopes, because there is no mind-reader module yet.
Sounds like you DID NOT read my first post. Please go ahead and read it.
Back to your reasoning, why does the wizard automatically pickup a "192.168.0.10 - 254" range right now? Is that a VERY GOOD practice? Why 10? Why 254? There are no standards to these things and that has not been my argument all along. In your case maximizing the number of IPs to reflect the full subnet potential minus the first 10 maybe a good idea. Also go ahead check and see what the wizard picks for your /23. And how come you don't have a problem with that???
My main issue with this is that the box locks if you forget to change the DHCP Server range. I have said that many times and answer I am getting is be careful - well, why create a door lock with warnings all over it to put the key in only one way or it will never open easily? why do that when we can allow for a key to insert any way or have a better lock where it won't be so fussy?
-
It does not lock the box. You can manually set an IP and get in.
The defaults are just that – defaults. Once the user changes a setting, the defaults no longer apply and any automatic method of trying to "guess" a new range will be inherently flawed or confusing. End of discussion.