Show Posts
1
General Discussion / Re: WAN to LAN traffic not working
« on: April 09, 2019, 07:45:11 pm »
Fortunately I only spent an hour trying to figure out why my brand new install of OPNSense could pull an WAN IP, would give me a valid DHCP address (v4 & v6), could ping from OPNSense, etc. Everything looked great. Every test I could think of worked perfectly... unless I used my Macbook to hit the Internet. Didn't matter what browser, terminal, nothing. Could not get from LAN to WAN from client. Changed from 192.168.3.x to 10.0.0.x. Dead ends everywhere. Knew it wasn't Unbound, the firewall, rules, because I had not set any up!!
Turns out the Network Settings for Thunderbolt Ethernet had 192.168.1.1 hard-coded in the list of DNS servers. Had to manually remove with the "minus" button. Everything lit up like a Christmas tree. No clue when that got set. Not normally an issue because I'm always on wifi, but my bench PC was busy with another task, so I thought, WTF... how hard can this be to figure out?? Turns out, kind of a PITA.
tl;dr: Could not access the internet after OPNSense default install. The wrong DNS was hard-coded on the client.
Turns out the Network Settings for Thunderbolt Ethernet had 192.168.1.1 hard-coded in the list of DNS servers. Had to manually remove with the "minus" button. Everything lit up like a Christmas tree. No clue when that got set. Not normally an issue because I'm always on wifi, but my bench PC was busy with another task, so I thought, WTF... how hard can this be to figure out?? Turns out, kind of a PITA.
tl;dr: Could not access the internet after OPNSense default install. The wrong DNS was hard-coded on the client.