View Single Post

  #1  
Old 08-22-2008, 04:54 AM
Default strange tcpip issue

OK please be gentle, it must be 15 years since I last touched a vax./vms

So VMS 7.3 installed and working on a subnetted network. (tcp on a vax. new
to me, it was all decnet and lat in my day).


So. my company use the RFC1918 scheme globally the UK has 10.32.0.0/12
assigned to it. When we get to my home I have a wonderfully generous /28
subnet mask applied.

so whilst my dhcp router dishes out address with a netmask of
255.255.255.240 which is picked up by my PC/linux boxes etc. I issue the
command on my vms system


TCPIP> ifconfig -a
LO0: flags=100c89
inet 127.0.0.1 netmask ff000000 ipmtu 4096

QE0: flags=c63
inet 10.34.220.88 netmask ff000000 broadcast 10.255.255.255 ipmtu 1500

QE1: flags=c43
inet 192.168.17.125 netmask ffffff00 broadcast 192.168.17.255 ipmtu
1500

TN0: flags=80

so interface QE0 which is assigned using dhcp is picking up the correct ip
address, but ignores the subnet mask and assigns the wrong mask of
ff000000, and incorrect broadcast address.

my pc etc on the same network gives me
Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : netgear.com
IP Address. . . . . . . . . . . . : 10.34.220.89
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . : 10.34.220.81
So I know my router/dhcp configs are right.

I had seen similar in old systems years ago, where ip stacks did not
properly support subnet masking. But I would have thought DEC would have got
this right.

Advice please guys how do I fix this


Reply With Quote