Subject: Re: Neighbour Discovery Bug?
To: None <core@ikame.net>
From: None <JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=>
List: current-users
Date: 07/21/1999 12:23:20
>>>>> On Wed, 21 Jul 1999 03:24:02 +0900,
>>>>> itojun@iijlab.net said:
>> Tried to setup an unnumbered tunnel (gif v6 over v4) between
>> netbsd-current and a freebsd-2.2.8/Kame machine, and got into a
>> bit of trouble on the netbsd machine. The netbsd machine didn't
>> manage to do neighbour discovery (of the freebsd machine at the
>> other end) over the tunnel interface (gif0). Got somehting like:
>> ioctl not supported for device message.
>> Solved my problem by numbering the tunnel-ends, but ND over unnumbered
>> tunnels should work, right? (it used to in Freebsd/kame and
>> NetBSD-1.3/kame, I believe).
>> If more info is necessary to figure out what's going wrong, I'd be
>> happy to reproduce it and cut 'n paste some output...
> I believe the above has two issues; one is ND over tunnel, another
> is how to configure unnumbered IPv6-over-IPv4 tunnel.
> KAME does not generate ND messages to gif tunnel. This is one of
> spec non-conformance that should be fixed. The problem we have is
> to interoperate with other end that does not do ND, and that do ND
> with the same codebase.
I guess Feico mentioned autoconfiguration of a global address by RS/RA
exchanges, but you seem to say NS/NA exchanges. Autoconfiguration
should be available even on a gif tunnel. Actually, I use it everyday.
> Could I know how I can repeat your symptom on "ioctl not supported..."?
I'd also like to know it.
BTW: Feico, did you run rtadvd on the freebsd box so that it
advertised RAs on the gif tunnel? If so, please show us your
rtadvd.conf if you don't mind.
JINMEI, Tatuya
Communication Platform Laboratory
Corporate R&D Center, Toshiba
jinmei@isl.rdc.toshiba.co.jp