The Question is:
Bug report, is Compaq aware of this problem with TCP/IP Services V5.0a?
We've worked around it, but thought you should know...
We use a program to produce a script of TCP/IP commands for setting and
maintaining our box's config. The program's parser zero-fills all octets in
any TCP/IP address so they are a fixed length . For example, address
18.104.22.168 gets scripted as 128.250.114.045.
However, TCP/IP incorrectly evaluates such zero filled addresses. In this
example, attempts to set address 128.250.114.045 gets stored in the TCPIP
database as 22.214.171.124.
TCPIP> show ver
DIGITAL TCP/IP Services for OpenVMS Alpha Version V5.0A
on a AlphaStation 200 4/166 running OpenVMS V7.1
TCPIP> set inter we0/host=128.250.114.045
TCPIP> show inter we0
Interface IP_Addr Network mask Receive Send MTU
WE0 126.96.36.199 255.255.255.0 (... etc)
The Answer is :
The behaviour reported here is fully expected, and is common
across various BSD-style IP stacks.
Please do not use leading zeros in the IP address, unless you
intend to specify that the portion of the IP address involved
is in octal. A similar caveat with leading 0x specifications,
as these will be interpreted as hexadecimal notation.