Initial setup - Basic DHCP connectivity on LAN

Started by planar3d, July 31, 2025, 08:35:43 AM

Previous topic - Next topic
Really basic questions here.

I am wiping a Celeron based system (Protectli Vault FW6C) that was running 24.7 and jumping to 25.7. Things were working fine but it is past time to upgrade.

This is a clean install. Drive is wiped and then I run the 25.7 installer. I am not carrying any configuration settings over.

I was looking forward to the Kea ipv6 stuff but in the meantime I just want to get basic ipv4 working and I'll use ISC if I have to.

The WAN is getting an IPv4 address. My problem is the LAN interface. This is a fresh install with stock settings. The only thing I have changed right now is the root password and the only thing connected to the LAN interface is an old laptop running Debian 12; directly via ethernet.

I can get to the OPNsense web interface just fine via 192.68.1.1.

Service -> ISC DHCPv4 does not show a LAN interface. I see no way to control or set DHCP options for the LAN interface yet somehow my laptop's enp0s31f6 interface has an IP address of 192.168.1.164 and I can get out to the wider internet

When I assign 192.168.2.1 to OPT1 can then see OPT1 under Service -> ISC DHCPv4

However, as soon as set an IP range, enable the ISC DHCP server, and apply changes I lose all connectivity on the LAN. The ping command on my laptop says the network is unreachable. Reboots have no affect. I have to resort to the factory reset via console.

I don't know why simply turning on a DHCPv4 service on OPT1 would kill LAN connectivity. Also, why can't I see what DHCP service the LAN is using? There is nothing under leases yet something assigned 192.168.1.164 to my laptop.

July 31, 2025, 08:54:21 AM #1 Last Edit: July 31, 2025, 09:07:08 AM by planar3d
Oh nevermind. I see that dnsmasq is what I am using and should utilize as a bridge before trying a more complicated Kea based config. The old hooks to ISC on the interface and services tabs is where I went astray.