[ale] Ok, this is wierd...

[John Wells]

Remember that 020 is an octet...i.e. an octal number.

Since you have a leading zero, it's simply converting 020 to the decimal
value (16) and pinging that address.  That host seems to be up, while the
host at 20 seems to be down.

020 octal = 16 decimal

Note that in the replies, it's indicating 192.168.2.16 as the replying host.

John

Christopher Bergeron said:
> Can anyone explain why this is happening?  If I ping 192.168.2.20 (two
> dot twenty) I get 100% packet loss.  However, when I ping 192.168.2.020
> (two dot zero-two-zero) I get 0 % packet loss. Detail below.
>
> [root at tomahawk /root]$ ping 192.168.2.20
> PING 192.168.2.20 (192.168.2.20) from 192.168.1.50 : 56(84) bytes of
> data.
>
> --- 192.168.2.20 ping statistics ---
> 3 packets transmitted, 0 packets received, 100% packet loss
> [root at tomahawk /root]$ ping 192.168.2.020
> PING 192.168.2.020 (192.168.2.16) from 192.168.1.50 : 56(84) bytes of
> data. 64 bytes from 192.168.2.16: icmp_seq=0 ttl=125 time=58.346 msec
> 64 bytes from 192.168.2.16: icmp_seq=1 ttl=125 time=59.957 msec
>
> --- 192.168.2.020 ping statistics ---
> 2 packets transmitted, 2 packets received, 0% packet loss
> round-trip min/avg/max/mdev = 58.346/59.151/59.957/0.841 ms
>
> Ok, now I know it's Monday AM, but is Murphy already up at this hour
> just to throw a wrench in my day?
>
> Any leads are appreciated...
> -CB
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale



_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale