Cannot use 172.24.0.1 as LAN IP

[nerlins]

I had opnsense using 172.16.0.1 as the LAN IP/ web GUI login. This was as fresh install, and just tinkering and learning.

I wanted to make all my subnets use 172.24.0, .1, .2, etc. I changed the LAN IP to 172.24.0.1/29 and let it reboot, losing access to web GUI and no IP handed out to the host. I then reset to defaults using the monitor and keyboard ports on my Protectli box, and started over. When using the wizard to change from 192.168.1.1/24 to 172.24.0.1/29 for LAN IP the exact some thing happens again.

So what gives. That is a class B private address space. It should be perfectly fine. Am I limited to only using 172.16.0.1???

[marjohn56]

Should work fine. What's your DHCP range set to?

[nerlins]

When you are using the wizard setup, it doesn't allow for a DHCP option to be set. It immediately wants to reboot after a LAN IP change.

[marjohn56]

So set a static on your PC in the correct range and then connect.

[nerlins]

Well of course I tried that...

I rebooted the computer multiple times, cleared DNS cache, set a static IP, but could not connect. If changing it to 172.16.0.1 using the wizard works on a first install, then changing it to 172.24.0.1 should work.

I just tried the exact same procedure on pfsense, and it worked. I had to reboot the PC, so it would let go of the default 192.168.1.100 IP address, and pfsense handed it 172.24.0.2 on reboot. Then I logged into the web GUI.

I am only one month into tinkering with either OS, and trying to figure out which one I like best, and which has the least headaches. I have to move forward now.

EDIT: I don't being stumped. I figured this out. It only works setting up via the console. The wizard broke multiple times. User error was not thinking of manually using the console sooner. I also downloaded a fresh copy of opnsense and performed a new install. Not sure if that made a difference.

Honestly, I think something is wrong with setting the mask as /29 on first install. I bet if I set it as /24 first, then changed the mask and DHCP pool later it might have worked.

[marjohn56]

I'll check it out with a clean install.

[marjohn56]

Yup.. very odd. Guess I'm just used to doing interface setup from the shell and bypassing the wizard when it starts up. Need to raise a ticket on Github for that one.