Ping Issues
-
Pardon me for this silly question, I have several pfSense boxes and whenever I ping an ip address e.g. 192.168.1.1127 (this is not a typo, it was intentionally done) I'm getting a reply, I'm not sure though if my interpretation is correct. The following ping tests was done using windows xp and from the pfSense box itself:
Ping output:
PING 192.168.1.1127 (208.67.219.132) from 124.105.120.66: 56 data bytes
64 bytes from 208.67.219.132: icmp_seq=0 ttl=52 time=454.116 ms
64 bytes from 208.67.219.132: icmp_seq=1 ttl=52 time=421.197 ms
64 bytes from 208.67.219.132: icmp_seq=2 ttl=52 time=240.471 ms–- 192.168.1.1127 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 240.471/371.928/454.116/93.921 msBTW, I'm using OpenDNS on all the boxes if it matters.
Is this normal? What would be the best explanation for this?
If the ping test was done using a Linux box, I'm getting the correct output which is 'unknown hosts'
TIA
-
This is not related to pfSense but because you use OpenDNS as DNS server.
Also if you set the DNS forwarder of pfSense as your DNS-server and your pfSense box is behind an NAT device and you try to resolve something that doesnt exist you will recieve as answer the public IP of the router in front of the pfSense.
-
The pfSense box is the main and only firewall/router. Your first explanation makes sense to me but what baffles me is why the Linux box behind pfSense produced the correct output and the windows box which is also behind pfSense produced the same result as that of the pfSense WebGUI.
-
That really depends on how your DNS-server responds to dns-requests for a non-existant domain.
Linux is probably intelligent enough to detect that you wanted to ping an IP but that the IP was misswritten.
If you enter 192.168.1.1127 into a webbrowser on windows you can see that it tries to resolve the misswritten IP as if it where a domain-name.
