No Internet Connection ?
-
I have WAN on a static IP of 192.168.1.153, It is receiving from a Router with the IP of 192.168.1.1 as well I used the Ping host option on the pfSense console, I pinged Googles DNS servers and I sent 3 packest and I received 3 of them so I guess that works, I pinged the router, all is fine, but when I tired to ping my PC it failed… Is that normal ? My PC is on 192.168.1.6 right now, I am going to change it to 192.168.4.6 and try to ping it then, still wasn't able to ping it, any ideas now ?
Nathan
-
My PC is on 192.168.1.6 right now, I am going to change it to 192.168.4.6 and try to ping it then, still wasn't able to ping it, any ideas now ?
Please post the ping command and response. That combination is nearly always more informative than "not able to ping".
You previously said:
@nathan715:I can connect to it through the second NIC (xl0), I do have to change me PC IP and Gateway IP accordingly, ( 192.168.4.6 - 192.168.4.1 )
Is that still true?
-
For the Ping command all I do is press 7 on the console then type in my IP 192.168.1.6
the response it,
PING 192.168.1.6 (192.168.1.6): 56 data bytes
–-192.168.1.6 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet lossPress ENTER to continue.
And yes If I change my IP to 192.168.4.6 I can connect to 192.168.4.1 (what I assigned the second NIC )
-
Its important to get the details correct. Your PC with IP address 192.168.1.6 is conected to the pfSense LAN interface?
-
Yes, It is, I though I said that already, or at least though that would have been obvious, but yes it is connected there,
-
or at least though that would have been obvious,
I suspect this connection would not have been obvious to someone who understands subnets and how routing works.
You ping 192.168.1.6. The ping goes out on the interface on the subnet of which 192.168.1.6 is a member - in this case the WAN interface.
Your PC needs to have an IP address in the subnet of the pfSense interface to which it is connected.
-
I am going to change it to 192.168.4.6 and try to ping it then, still wasn't able to ping it, any ideas now ?
Nathan
I have, I had no luck,
-
What is the response to pfSense shell command:```
ping -c 5 192.168.4.6 ; arp -a -n -
Sorry it took me so long to get back to you, I was very busy, But here it is,
[2.1-BETA0][root@pfsense.localdomain]/root(1): ping -c 5 192.168.4.6;arp -a -n
PING 192.168.4.6 (192.168.4.6): 56 data bytes–- 192.168.4.6 ping statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss
? (8.8.4.4) at (incomplete) on xl0 expired [ethernet]
? (192.168.4.6) at 00:14:22:34:d7:1f on xl0 expires in 992 seconds [ethernet]
? (192.168.4.1) at 00:04:75
a1:2f on xl0 permanent [ethernet]
? (192.168.1.1) at 30:85:a9:3a:4a:a8 on bfe0 expires in 1200 seconds [ethernet]
? (192.168.1.153) at 00:e0:18:ba:c0:52 on bfe0 permanent [ethernet]
[2.1-BETA0][root@pfsense.localdomain]/root(2):It was an annoyance to type out but there it is,
Nathan
-
The ARP data shows at the time a MAC address for 192.168.4.6 was known. Is that MAC address correct? Is that system enabled to respond to pings?
The following ARP entry has me curious:
@nathan715:? (8.8.4.4) at (incomplete) on xl0 expired [ethernet]
That suggests that at some time in recent past your pfsense thought 8.8.4.4 was on the same subnet as xl0! What netmask do you have on your interfaces?
Perhaps you have been tweaking various things and the system has some memory of various tweaks that have not been completely undone.
I suggest you reboot your pfSense box and attempt to ping 192.168.4.6 again. If you don't get a ping response then check the PC is configured to respond to pings and try pinging the pfSense box from the PC.