Mike,
I get a different behavior:
On LinuxMint Nadia (3.5.0-27 kernel, ping utility, iputils-sss20101006),
Debian 6, Oracle linux 5 (kernel 2.6.18), solaris 9, Windows 7, and Mac
OS 10.8 I get:
ping 10.1.2.27, 10.001.2.27, 10.1.002.27 works
ping 10.1.2.027 does this: PING 10.1.2.027 (10.1.2.23) 56(84) bytes of
data. which is consistent with 027 octal being changed into decimal 23.
I am not sure why the conversion does not happen on the other octets.
cheers,
ski
On 04/25/2013 07:54 AM, Mike Julian wrote:
Perhaps this is totally normal behavior, in which case, I'm really
curious why:
If I ping an IP with padded zeros in the last octet (eg, 192.168.1.001),
the ping succeeds.
If any other octet is padded (eg, 192.168.001.1), the ping treats the IP
as a hostname and fails. It fails no matter how many octets are padded,
or which ones (excepting the last octet by itself).
I've noticed this behavior on RHEL6 and OSX (10.8).
Any thoughts?
_______________________________________________
Discuss mailing list
Discuss@lists.lopsa.org
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
--
"When we try to pick out anything by itself, we find it
connected to the entire universe" John Muir
Chris "Ski" Kacoroski, Director of LOPSA, s...@lopsa.org,
206-501-9803 or ski98033 on most IM services
_______________________________________________
Discuss mailing list
Discuss@lists.lopsa.org
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
