DHCP range has invalid end range value
-
This bug has been around for a few versions. Does anyone know how to get around it?
The end range is obviously wrong and if I try and set a range 192.168.0.100 - 192.168.0.200, it says it's out of bounds when clearly it shouldn't be.
-
Your subnet mask is wrong, you have 255.255.255.255 giving you a valid range of 192.168.0.2 to 192.168.0.0 or less than nothing.
Increase your subnet mask to give you the range of addresses you want - typically /24 would be 255.255.255.0 giving you 192.168.0.2 - 192.168.0.254
-
Your subnet mask is wrong, you have 255.255.255.255 giving you a valid range of 192.168.0.2 to 192.168.0.0 or less than nothing.
Increase your subnet mask to give you the range of addresses you want - typically /24 would be 255.255.255.0 giving you 192.168.0.2 - 192.168.0.254
Hmm you're right but I don't recall setting this anywhere. I'll have to look to see where this is configured.
-
So is there any other way to set this explicitly than to create them either over SSH or console? That was the only way I could set the correct subnet mask where I could tell. I couldn't find it anywhere in the GUI.
-
It's part of the interface definition:
Interfaces->Lan0->IPv4 Address and chose "24" from the drop down list of CIDR masks.
It's defaults to /32 on interfaces other than LAN if I remember right, so it's easy to miss.
-
This bug has been around for a few versions. Does anyone know how to get around it?
Not a bug, your interface is a /32 which means it's in its own world, nothing else on that subnet. It's correct in preventing you from configuring what you're trying to configure, as it's invalid. As divsys noted:
Interfaces->Lan0->IPv4 Address and chose "24" from the drop down list of CIDR masks.
-
Cool thank you for clarifying divsys.
Seed
-
No problem, I'm happy to say I learn a little more every day I check through the forums :)