Changing LAN IP - what am I missing?

[malebron]

I have a pretty simple vanilla config here. Flat network, a couple of unmanaged switches, Adguard Home.

All I want to do is change the LAN IP from the standard 192.168... to something else.

I changed the IPv4 address under Interfaces/LAN, and ensured any addresses under Services/ISC DHCPv4/LAN were changed from 192.168... to match the new IP. I also changed the lease time to ~30mins.
After a reboot nothing worked. I can't connect to Opnsense at the new IP or get a new IP lease on my Mac. The console looks as I would expect.
After too much time spent rebooting devices, messing with Mac network settings etc I restored to a backup via the console, and all works as before.

I assume I'm missing something obvious. What else must I do to make this change?

Thanks for any help!

[bartjsmit]

Connect to the console and use option 2

[malebron]

Thanks. The console menu option is clearly the best way to change the OPNsense IP, but that was not my problem.

It turns out the issue was AdGuard Home, although it's running as a service in OPNsense, it does not pick up the new IP automatically - and there is nothing related to IP in AdGuard Home's GUI. I have this configured as my primary DNS - No DNS no Internet!

To fix this, the AdGuard Home service must be stopped and the configuration file AdGuardHome.yaml must be edited manually from the CLI. In my case this required the root user.

I know this is not a common action, but posting here in case it helps someone else.

[dseven]

Hmm. Not sure how AGH could prevent DHCP from working.....