Steven Stallion wrote: >James Carlson wrote: > > >>Not being able to reset it seems right to me, but being able to set it >>at all sounds like a bug. >> >>The POINTOPOINT flag is a property of the underlying medium. There's >>no reasonable way that this can be specified by the user, and we >>really shouldn't allow it. (I suspect there are other skeletons >>buried here ...) >> >> >> > >It's pretty easy to duplicate (initial run on snv_89): > ># ifconfig dnet0 plumb ># ifconfig dnet0 10.0.0.1 255.255.255.0 up #missing netmask ># ifconfig dnet0 >dnet0: flags=200000851<UP,POINTOPOINT,RUNNING,MULTICAST,CoS> mtu 1500 > inet 10.0.0.1 --> 255.255.255.0 netmask ff000000 > ether 0:c0:ca:13:a4:9e > >And, an attempt to reset the interface (forcibly setting the broadcast): > ># ifconfig dnet0 down ># ifconfig dnet0 10.0.0.1 netmask 255.255.255.0 broadcast 10.0.0.255 up >ifconfig: SIOCSLIFBRDADDR: dnet0: Cannot assign requested address > >
Yes, I was able to reproduce this myself...it requires an unplumb in order to get it right. The behaviour you're seeing, "ifconfig foo0 ip1 ip2" resulting in a POINTTOPOINT interface is, in my experience, "normal" for unix. (The netmask is just another IP address, in this notation.) However, you should be able to take it out of POINTTOPOINT mode by specifying the netmask... Darren _______________________________________________ networking-discuss mailing list [email protected]
