> > That way stateless autoconf works with isatap tunnels and without
quoted text
> > knowledge of the local v4 address.
>
> Real autoconf is not performed, but rather you must configure your
> system with a PRL (potential routers list) and these routers are
> probed periodically in order to keep track of which of them are still
> functioning and also to perform a sort-of unicast-only autoconf.
Well, since ISATAP is just a SIT, it still needs a link local address for=20
autoconf and it needs to have it's v4 Address embedded in the lowest 32 bit=
 of=20
the linklocal address. It will then do normal autoconf with the potential=20
router by sending a proper router solicitation messages, either directed or=
=20
multicast.

I see that the current implementation disables sending of RS when on ISATAP=
,=20
which is not correct because RS are needed to do the autoconf.

At least that's the way the implementation in MS Windows works.

quoted text
> I am pretty sure that the person who added the ISATAP code created the
> current behavior intentionally.
Well, the current implementation does not cover clients at all, because=20
the ip command refuses to create tunnels without the remote parameter, whic=
h=20
is neccessary because it's the potential router.

It then does not derive the linklocal address correctly, making it impossib=
le=20
to do autoconf with the server. Using SIT does work as such as you still ne=
ed=20
to add the correct ISATAP linklocal address to the interface.=20

I think ISATAP Client support in Linux could be more automated.


=2D Sascha