Hello Bruce, * Bruce A. Mah <[EMAIL PROTECTED]> wrote: > I think that suz@ and ume@ are the people who have worked in this area > most recently, hopefully one of them will speak up. You didn't give a > lot of details...please give (at a minimum) the version of FreeBSD > you're using and more details about the interface over which you're > having this problem. > > I saw this on RELENG_6 sometime after some IPv6 ND changes that were > merged in late last year. I have a gif(4) tunnel to my ISP over which I > do IPv6. The GIF tunnel was originally configured as a point-to-point > interface and I got the same messages you mentioned. My workaround was > to configure the gif(4) interface as a /127, which was obviously only > possible because the two interface addresses on each end of the tunnel > just happened to differ only in their least-significant bits. (I know > this isn't the right solution.)
I'm seeing the messages on the machine in Eindhoven (running RELENG_6 from a few days/weeks ago), but they also show up on my HEAD machine at home. Below is the output of `ifconfig gif0` on my machine at home: | gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280 | tunnel inet 83.181.147.170 --> 193.109.122.244 | inet6 fe80::202:a5ff:fe58:4927%gif0 prefixlen 64 scopeid 0x7 | inet6 2001:7b8:310::1 --> 2001:7b8:2ff:a4::1 prefixlen 128 As far as I know, the latest FreeBSD releases show an error message when assigning an address with a non-128 prefixlen. -- Ed Schouten <[EMAIL PROTECTED]> WWW: http://g-rave.nl/
pgpZs2A6tlyA3.pgp
Description: PGP signature
