Router not having WAN access

Started by justjake, March 23, 2026, 07:09:24 PM

Previous topic - Next topic
Ok traceroute via the terminal works a little differently.

The firewall rules seem to be in place.

Quote from: justjake on March 25, 2026, 05:13:03 PMOk traceroute via the terminal works a little differently.
So your OPNsense has WAN connectivity :)

Now do the same from any Client please.

QuoteThe firewall rules seem to be in place.
Then LAN should be able to reach the Internet by IP address for now!
Weird guy who likes everything Linux and *BSD on PC/Laptop/Tablet/Mobile and funny little ARM based boards :)

This is from another device on my opnsense router, not much going on.

Quote from: justjake on March 25, 2026, 06:16:36 PMThis is from another device on my opnsense router, not much going on.
If the traffic does not go past the local gateway then you need to check your routing :
- Is NAT setup correctly ?
- Default Gateway is also the correct one ?

Please note that you also did not use traceroute -n to avoid any DNS Resolving issues.
Weird guy who likes everything Linux and *BSD on PC/Laptop/Tablet/Mobile and funny little ARM based boards :)

Okay, traceroute -n still gave nothing from the media server, and the default gateway is the correct IP address. When you say NAT do you mean the one on the router or the client?

Quote from: justjake on March 26, 2026, 01:44:33 AMand the default gateway is the correct IP address.
I am guessing your OPNsense WAN is simply set to DHCP and should be the Default Gateway : Is that the case ?

QuoteWhen you say NAT do you mean the one on the router or the client?
I mean Outbound NAT in OPNsense : Is it setup correctly ?

In general you never NAT on the Client side ;)



But to be honest I think it might be easier to reset your configuration and just follow the First Boot Setup Wizard correctly to fix this issue, unless you figure out how to fix everything manually...
Weird guy who likes everything Linux and *BSD on PC/Laptop/Tablet/Mobile and funny little ARM based boards :)

The WAN interface is set to DHCP but haven't done much in the settings for it, the screenshots should show all of that.

I've disabled NAT and it all still seems the same.

Although it's a simple setup, being a newb,it was still a bit difficult and i'd prefer not having to do it again. I'd rather learn what i've done wrong to be honest.

Quote from: justjake on March 27, 2026, 08:28:53 PMI've disabled NAT and it all still seems the same.
Disabling NAT is a bad idea at all. This disables the outbound NAT, which might be required to access anything on the WAN side from behind.

Check if the default route is set properly:
System: Routes: Status

The default route should point to the internal IP of the upstream router.

Also check the outbound NAT, if you didn't set up the new source NAT yet.
Firewall: NAT: Outbound
Either automatic or hybrid mode should be enabled and down under automatic rules, you should find rules on WAN for your LAN subnet.

If you have source NAT rules configured, recheck them.

Also ensure, that didn't state a gateway in the LAN interface settings.

Ok, so I have put NAT back on Automatic, there was/is no automatic rules at the bottom of that page.
The default route is passing straight to the "upstream router" or my ISP one.
LAN interface settings has no gateway declared, it says nothing about "gateway" appart from "IPv4 gateway rules" which is set to disabled and I don't think i've ever touched that.

Quote from: justjake on March 27, 2026, 09:53:43 PMOk, so I have put NAT back on Automatic, there was/is no automatic rules at the bottom of that page.
Do you have a WAN rule in Firewall: NAT: Source NAT instead?