Because a leading zero in the unix/linux world (and much of the mini/micro universe) means an octal number and 035 becomes 3 times 8 plus 5 which equals 29....
Carey Schug Open your home, open your heart, become a foster parent! Coffin Michael C <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 04/25/2002 12:15:22 Please respond to Linux on 390 Port <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: [LINUX-390] IP Addressing Oddity Hi Folks, I recently had to move my VM TCPIP stack for Linux, and my Linux/390 guests (Redhat and SuSE) to a different subnet.� The third octet was changing, so (for example) 152.225.112.249 would become 152.225.35.249.� I made the changes to both VM's TCPIP and my Linux/390 guests in advance of the change then fired everything up. 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! Note:� I made the changes on the SuSE machines in rc.config then ran SuSEconfig, and on the RedHat I made them in ifcfg-ctc0, gateways and I think network. So my question is why did the Linux/390 guests interpret .035. to mean .29., and if that is a "normal" thing - why didn't VM's TCPIP do the same thing? Any advice or opinions are most welcome.� :) Michael Coffin, VM Systems Programmer Internal Revenue Service - Room�6030 1111 Constitution Avenue, N.W. Washington, D.C.� 20224 Voice: (202)�927-4188�� FAX:� (202) 622-6726 [EMAIL PROTECTED]
