Comment on Help configuring OPNsense VLANs? Tutorials I find seem to quickly become outdated.
Jenseitsjens@lemmy.world 6 days agoIf that’s the only route then your issue starts there. If you want to reach anything other than the local network there needs to be a default route to the gateway.
The default route is sent along the dhcp lease so my suspicion is that the issue is in the dhcp server config.
So what do you think might be the problem with it that I might check? As far as I know, if I’ve been assigned an IP address, DHCP is working.
Jenseitsjens@lemmy.world 5 days ago
DHCP usually provides three things:
In the DHCP lease you for example get the IP 192.168.10.42/24. That IP is assigned to your interface which creates a implizit route like
192.168.10.0/24 dev netinterface. Now you know how to reach other hosts in your local network.In the same DHCP lease, you should also receive a default gateway - likely 192.168.10.1. this would add a route like
default via 192.168.10.1.Without the default route, packets for IPs other than your local network never leave your host because it doesn’t know where to send them to.
DNS servers are also provided, though before troubleshooting that, I would just ping addresses like 8.8.8.8 (google dns) for testing connectivity.
Hey, that’s forward progress! The first I’ve had since this thread! That command did in fact allow me to ping my desktop from my mini PC on the VLAN. It also allowed me to ping 8.8.8.8, which I was unable to do before. On reboot, that default gateway seems to be reset until I run the command again, which makes sense. So I guess my next question is: what does this mean, and how do I fix it? I take it to mean that of those three jobs DHCP is supposed to provide in your list, it’s only done the first one. The DHCP systems in particular are a major change from what OPNsense was just two years ago when the guides I’ve been following were made.