Outbound SNAT for VLAN Traffic Does not Appear to be Working - No Internet

Started by lomax0990, July 20, 2023, 10:56:35 PM

Previous topic - Next topic
I have a new OpnSense appliance.  My internet was working, but has since stopped and I can't figure out why.

I did a packet capture on my WAN interface which seems to show RFC1918 addressing going to my WAN provider. 

f4:90:ea:00:b8:19   00:01:5c:8d:fd:e4   IPv4, length 78: 10.10.10.4.51368 > 208.67.222.222.53: UDP, length 36

The SRC MAC address from the packet capture is the IP of my WAN interface and the destination MAC is the default gateway from my WAN provider.  So that all seems correct.  I've checked all the gateway, outbound NAT, and route settings that I can find.  I'm running out of idea of what to do next. 

Any ideas why it wouldn't NAT the traffic before sending it out my WAN interface?


Thanks I did read through that article.  However, it doesn't seem like NAT reflection is what I need here.  I just need it to do the basic function of a router and NAT the packets from the different VLAN's coming in to the WAN interface address. 

Doing a tcpdump on the WAN interface I can see I'm sending the RFC1918 sources to the ISP.  I'm sure it's something simple, but I'm new to OpnSense and something just isn't lining up for me.  Here is a tcpdump output from my WAN interface.  Kind of gives you an idea of what I'm talking about.  I don't know why Opnsense isn't NAT'ing the 10.10.40.52 to my WAN address.

20:46:57.457090 IP 10.10.40.52.28616 > 4.4.4.4.domain: 23404+ A? fireoscaptiveportal.com. (41)