LAN client cannot connect
-
@stephenw10 sistem/routing/gateway
WAN_DHCP Default (IPv4) WAN
WAN_DHCP6 Default (IPv6) WAN -
@stephenw10 diag/routes
Route IPv4
default 192.168.1.xxx re1 (wan)
127.0.0.x lo0
192.168.1.x/24 re1 (wan)
192.168.1.xxx lo0
192.168.100.x/24 re0 (lan)
192.168.100.x lo0
Rotte IPv6
default xxxxxxxxxxxxxxxre1 re1 (wan) -
@stephenw10 Status/Gateways
Gateways
WAN_DHCP (default) 192.168.1.xxx 192.168.1.xxx Connected Interface WAN_DHCP Gateway
WAN_DHCP6 (default) xxxx::xxx:xxxx:xxxx:xxxx%re1 xxxx::xxx:xxxx:xxxx:xxxx%re1 Connected Interface WAN_DHCP6 Gateway -
@Spectrum do you suggest to delete this option in the lan network (re0)?
-
I'm only suggesting you delete any gateways defined on LAN in System > Routing > Gateways.
However it should be working as it is?
-
@stephenw10 sistem / routing / gateway have only wan . lan no longer appears. the pc is connected pero many sites can't access. i'm thinking maybe i need to see if it accepts both http and https. am i doing the thinking wrong?
-
@stephenw10 Unable to reach the site
Unable to find the IP address of the server of en.wikipedia.org.Try:
Checking the connection
Checking the proxy, firewall, and DNS configuration
Running the Windows Network Diagnostics tool
ERR_NAME_NOT_RESOLVEDthis i see when visite web like wikipedia
-
Can you ping 8.8.8.8 from pfSense?
-
@stephenw10 ping 8.8.8.8 : 56 data bytes
3 packets transmitted, 3 packets received, 0% packet loss -
Ok great try to ping google.com from pfSense.
If that succeeds try to ping google.com from a client on the LAN.
-
@stephenw10 pfsense shell google.com 3 packets transmitted, 3 packets received, 0% packet loss
web gui diag/ ping
8.8.8.8 3 packets transmitted, 3 packets received, 0% packet loss (lan)
1.1.1.1 3 packets transmitted, 3 packets received, 0% packet loss (lan)
google.com 3 packets transmitted, 3 packets received, 0% packet loss (lan)
wikipedia.org 3 packets transmitted, 3 packets received, 0% packet loss (lan)
wikipedia.org 3 packets transmitted, 3 packets received, 0% packet loss (wan) -
Ok try that same test from a client on the LAN.
-
@stephenw10 how
-
Just run some pings from a client on the LAN.
The client cannot open web pages but pfSense clearly can reach external sites and can resolve DNS.
So either the client is being blocked (the default firewall rules should pass it though) or it cannot resolve.
Testing with ping should show that. -
@stephenw10 Diag/Ping
Ping
Host name wikipedia.org
IP protocol
IPv4
Source address
LAN
--- ping statistics from wikipedia.org ---
10 packets transmitted, 10 packets received, 0.0% packet lossPing
Host name giallozafferano.it
IP protocol
IPv4
Source address
LAN
--- ping statistics from giallozafferano.it ---
10 packets transmitted, 0 packets received, 100% packet loss -
Try pinging from a client not from pfSense.
That second address doesn't appear to respond to ping so that's not a problem:
steve@steve-NUC9i9QNX:~$ ping giallozafferano.it PING giallozafferano.it (52.17.217.40) 56(84) bytes of data. ^C --- giallozafferano.it ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2037ms -
@stephenw10 ok, cmd windows.
ping 8.8.8.8
--- ping statistics from 8.8.8.8 ---
4 packets transmitted, 4 packets received, 0.0% packet lossping 1.1.1.1
--- ping statistics from 1.1.1.1 ---
4 packets transmitted, 4 packets received, 0.0% packet lossping google.com
--- ping statistics from 216.58.204.142 ---
4 packets transmitted, 4 packets received, 0.0% packet lossping wikipedia.org
unable to find host "wikipedia.org". check correct name and try again -
Hmm, well pfSense can resolve wikipedia.org but the client cannot. Is it configured to use pfSense for DNS?
By default pfSense will pass it;s own interface address to use for DNS via DHCP
-
@stephenw10 I didn't touch anything, I just did as you described. if you can kindly tell me where should I look for this dns thing?
-
Depends what the client is. Is it configured for DHCP?
If it is t should pull the DNS info from pfSense with the DHCP lease.
