OPNsense Forum
Archive => 22.7 Legacy Series => Topic started by: orhay on August 05, 2022, 05:11:01 pm
-
Hi, on a fresh install of OPNsense after going thro the wizard and setting every thing up I dont have any internet to the outside
the setup goes like this
ISP Router (192.168.1.1) -> (ISP DHCP 192.168.1.33) OPNsense (OPNsense 192.168.0.1) -> (OPNsense DHCP 192.168.0.100) PC
from the box itself i can ping the outside like so
(https://i.postimg.cc/G2w7mWXb/Screen-Shot-2022-08-05-at-18-04-01.png)
when I try pinging google from my pc I get unknown host and when I try pining 8.8.8.8 I get timedout
➜ ~ ping google.com
ping: cannot resolve google.com: Unknown host
➜ ~ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
My settings are as follows
under Unbound DNS "Use System Nameservers" checked
under Settings General "Allow DNS server list to be overridden by DHCP/PPP on WAN" checked
under Firewall Advanced "Disable reply-to" checked
I did not assign any DNS servers anywhere
-
A very strange setup, it's unsurprising some services aren't working as desired.
When OPN is setup, some sane assumptions are made, like the WAN and LAN interfaces based on discovery, and the system is setup accordingly and it will in general, just work. In your setup, which appears unorthodox, it will require you to set everything up, including firewall rules.
To be honest from:
ISP Router (192.168.1.1) -> (ISP DHCP 192.168.1.33) OPNsense (OPNsense 192.168.0.1) -> (OPNsense DHCP 192.168.0.100) PC
I literally can't make head or tail. And all are private addresses, even the ISP one !
-
Im trying to read between the lines here.
Two things I will suggest.
1. First you must be certain opnsense has connectivity, in opnsense console can it ping say 8.8.4.4
This proves the upstream is working and opnsense gateway can reach the internet. If no connection untick the allow dns override by dhcp and configure dns here as 8.8.4.4 to test again
Once this works goto step 2.
2.do ipconfig/all on the client
Confirm its gateway address is the ip of the lan interface.
Report back what dns resolvers are configured.
Run a tracert 8.8.4.4 and see how far it gets most likely not getting past the gateway