LAN client cannot connect
-
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.
-
@stephenw10 how can I look at this information?? both to see if it is configured for DHCP?? and in case it is not configured ("If not, you need to pull DNS information from pfSense with DHCP lease")??
-
Just about all clients will connect using dhcp by default and use the DNS information passed that way. But that can be configured manually by the user. You need to check that in Windows to be sure.
You can check Status > DHCP Leases in pfSense to see if your client pulled a lease.
-
@stephenw10 Status/ DHCPv6 Leases nothing here
-
Not v6. Just the v4 leases in Status > DHCP Leases.
-
@stephenw10 i have only status / DHCPv6
maybe is writing status / release DHCP??
-
Ok maybe you disabled IPv4 DHCP when you change the LAN IP.
Go to Services > DHCP Server > LAN and make sure it's enabled.
-
@stephenw10
Services > DHCP Server > LAN
Enable - Enable DHCP server on the LAN interface (yes)
Is this feature already enabled or is it something else I need to look at? -
Yes it should be enabled by default. Check Status > Services.
-
@stephenw10 status/service
service
dhcpd service DHCP
dpinger Demon Monitoring Gateway
ntpd NTP Time Synchronization
syslogd System registry daemon
unbound DNS Resolver
