> On Thu, Apr 25, 2002 at 01:15:22PM -0400, Coffin Michael C wrote:
> > I had coded the third octet as .035. instead of .35. VM's TCPIP took the
> > 152.225.035.249 without any difficulty. But all of my Linux/390 guests
> > CHANGED the .035. to .29 - so this same address on a Linux/390 guest would
> > be 152.225.29.249. I was totally perplexed, and after hours of scratching
> > my head I changed one of these to just .35. and low and behold it worked!
>
> ifconfig appears, therefore, to act like many Unix utilities: a leading
> "0" means that the number is to be interpreted as octal.
>
> Octal 35 is 3*8 + 5, or....29. I bet you can use 0x1D to get 29 as
> well.
I happen to have a box it doesn't matter if I misconfigure so I tried it. You
can (but I'm sure that's a recent change. I'm certain it didn't a while ago).
Someone might report it as a bug - we now have this ridiculous situation:
[root@numbat root]# ifconfig eth0 192.168.1.011
[root@numbat root]# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:40:F4:28:A0:3A
inet addr:192.168.1.9 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:58923479 errors:27 dropped:1 overruns:20 frame:0
TX packets:37011741 errors:0 dropped:0 overruns:2 carrier:0
collisions:197384 txqueuelen:100
RX bytes:3622792122 (3454.9 Mb) TX bytes:3221846063 (3072.5 Mb)
Interrupt:10 Base address:0x3000
[root@numbat root]# host 192.168.1.011
Host 11.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
[root@numbat root]#
--
Cheers
John Summerfield
Microsoft's most solid OS: http://www.geocities.com/rcwoolley/
Note: mail delivered to me is deemed to be intended for me, for my disposition.
==============================
If you don't like being told you're wrong,
be right!
