[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Can't access gateway IP



On Sat, May 4, 2013 at 7:55 AM, Bob Proulx <bob@proulx.com> wrote:
>
> s0lid wrote:
> > ---from debian server---
> > root@debian:~# ping 192.168.1.1
> > PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
> >
> > PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.
> > 64 bytes from 192.168.1.2: icmp_req=1 ttl=64 time=40.5 ms
> > 64 bytes from 192.168.1.2: icmp_req=2 ttl=64 time=1.96 ms
> > 64 bytes from 192.168.1.2: icmp_req=3 ttl=64 time=2.08 ms
> > ^C
> > --- 192.168.1.2 ping statistics ---
> > 3 packets transmitted, 3 received, 0% packet loss, time 2003ms
> > rtt min/avg/max/mdev = 1.967/14.861/40.532/18.152 ms
>
> How did it move from 192.168.1.1 to 192.168.1.2?  Did your machine
> receive an ICMP redirect packet from the router?

Apologies i forgot to include the  "# ping 192.168.1.2" when copy and
pasting the ping result.

>
>
> Please try again with 'ping -v' and post the output.  It might show an
> ICMP redirect being received.

same thing jus tthis.

root@debian:~# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.



>
> I would run 'tcpdump -lni any' on both machines and look for the
> disconnect.  If it is a noisy network then filter with 'host W.X.Y.Z'
> with the address of your client machine.
>
>   tcpdump -lni any host W.X.Y.Z
>

i got this from tcpdump while pinging my gateway

14:06:31.172753 ARP, Request who-has 192.168.1.1 tell 192.168.1.106, length 28
14:06:31.173851 ARP, Reply 192.168.1.1 is-at 40:4a:03:d6:ac:a9, length 46
14:06:50.602659 IP 192.168.1.106 > 192.168.1.1: ICMP echo request, id
2563, seq 1, length 64
14:06:51.611094 IP 192.168.1.106 > 192.168.1.1: ICMP echo request, id
2563, seq 2, length 64
14:06:52.620045 IP 192.168.1.106 > 192.168.1.1: ICMP echo request, id
2563, seq 3, length 64
14:06:53.626974 IP 192.168.1.106 > 192.168.1.1: ICMP echo request, id
2563, seq 4, length 64


Reply to: