- May 7, 2002
- 10,371
- 762
- 126
In windows:
In linux:
And finally, from router:
Now, the question is why does pinging 192.168.1.32 from linux or windows jump to a IP that isn't 192.168.1.32?
There are no FW rules enabled.
There are no IPTABLES rules to account for what is going on.
192.168.1.32 is a android device hooked up via WiFi.
So, anyone got any ideas?
*edit, looks like 192.168.1.32 isn't showing up in ARP for some reason.
*edit 2. Issue resolved itself.
No idea how, I just went away for a bite to eat, came back, and it was working as it should.
windows:
linux:
And yes, it is showing up in ARP now.
Code:
Pinging 192.168.1.32 with 32 bytes of data:
Reply from 192.168.1.39: Destination host unreachable.
Reply from 192.168.1.39: Destination host unreachable.
Reply from 192.168.1.39: Destination host unreachable.
Reply from 192.168.1.39: Destination host unreachable.
Code:
ping 192.168.1.32
PING 192.168.1.32 (192.168.1.32) 56(84) bytes of data.
From 192.168.1.17 icmp_seq=1 Destination Host Unreachable
From 192.168.1.17 icmp_seq=2 Destination Host Unreachable
From 192.168.1.17 icmp_seq=3 Destination Host Unreachable
From 192.168.1.17 icmp_seq=4 Destination Host Unreachable
From 192.168.1.17 icmp_seq=8 Destination Host Unreachable
From 192.168.1.17 icmp_seq=9 Destination Host Unreachable
...
Code:
0 192.168.1.32 (192.168.1.32) 64 64 93.18
1 192.168.1.32 (192.168.1.32) 64 64 67.33 -25.86
2 192.168.1.32 (192.168.1.32) 64 64 77.28 9.95
3 192.168.1.32 (192.168.1.32) 64 64 97.24 19.96
...
Round-Trip: 67.325 min, 88.587 avg, 107.915 max (ms)
Packets: 5 transmitted, 5 received, 0% lost
Now, the question is why does pinging 192.168.1.32 from linux or windows jump to a IP that isn't 192.168.1.32?
There are no FW rules enabled.
There are no IPTABLES rules to account for what is going on.
192.168.1.32 is a android device hooked up via WiFi.
So, anyone got any ideas?
*edit, looks like 192.168.1.32 isn't showing up in ARP for some reason.
*edit 2. Issue resolved itself.
No idea how, I just went away for a bite to eat, came back, and it was working as it should.
windows:
Code:
Pinging 192.168.1.32 with 32 bytes of data:
Reply from 192.168.1.32: bytes=32 time=35ms TTL=64
Reply from 192.168.1.32: bytes=32 time=95ms TTL=64
Reply from 192.168.1.32: bytes=32 time=318ms TTL=64
Reply from 192.168.1.32: bytes=32 time=230ms TTL=64
Code:
PING 192.168.1.32 (192.168.1.32) 56(84) bytes of data.
64 bytes from 192.168.1.32: icmp_seq=1 ttl=64 time=240 ms
64 bytes from 192.168.1.32: icmp_seq=2 ttl=64 time=135 ms
64 bytes from 192.168.1.32: icmp_seq=3 ttl=64 time=363 ms
64 bytes from 192.168.1.32: icmp_seq=4 ttl=64 time=282 ms
64 bytes from 192.168.1.32: icmp_seq=5 ttl=64 time=1.44 ms
64 bytes from 192.168.1.32: icmp_seq=6 ttl=64 time=101 ms
64 bytes from 192.168.1.32: icmp_seq=7 ttl=64 time=328 ms
64 bytes from 192.168.1.32: icmp_seq=8 ttl=64 time=247 ms
Last edited: