I believe that if a component of an IP address contains a leading zero, it normally interperted as an octal value. I guess the VM folks play by the "rules".
Paul On Thu, 25 Apr 2002, Coffin Michael C wrote: > Date: Thu, 25 Apr 2002 13:15:22 -0400 > From: Coffin Michael C <[EMAIL PROTECTED]> > Reply-To: Linux on 390 Port <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: 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. :) Paul L. Rogers [EMAIL PROTECTED] Are you prepared for NetDay? http://www.netday.org/ Linux: It works for me. http://www.linuxdoc.org/
