(usagi-users 01175) Re: ISATAP feedback (was: version verification for ISATAP)

[Peter Bieringer <pb@xxxxxxxxxxxx>]

Hi,

--On Thursday, January 17, 2002 03:50:39 PM -0500 Nathan Lutchansky
<lutchann@xxxxxxxxxx> wrote:

>> docs/ease of use:
>> -Peter Bieringers work seems to be the authoritative reference for
>> configuration of ipv6,
Looks like so ;-)

>> I had a little trouble locating
>> http://v6web.litech.org/isatap/. Merging the instructions with the
>> (new) LDP site http://linuxdoc.org/HOWTO/Linux+IPv6-HOWTO/ would
>> make it more accessible and increase awareness.
> 
> This is a good idea.  I wouldn't mind contributing the ISATAP HOWTO
> to the Linux IPv6 HOWTO, and this seems like an appropriate place
> for it.
> 
> Peter?  How does this sound?
Ok, no problem for me, if GPL copyright makes no problem at all for
you.

Contribution best practice would be currently a LyX file using
DocBook template and writing one chapter. For reviews later, I got
already an user CVS space on LDP for the LyX file. 


>> -Extending the scripts (in Redhat) such that isatap can be
>> controlled just by .conf files would be nice, but I realize this
>> is very early and most people working with it so far won't care
>> about this kind of thing.
> 
> I thought about distributing an init script to do this, but decided
> not to, due to your next point.
For RHL they should base on my script set, if you need extensions,
tell me.

>> functionality:
>> -If the ISATAP clients use dynamic addresses then the dependency
>> on the local address when setting up the client is awkward for
>> real deployments.
> 
> Yes, that is a bit of a problem.  I envision that ISATAP will be
> primarily used in dynamic-IP environments, likely with DHCP clients
> on a corporate network.
> 
> I think it is clear that the IPv4 address the client should use
> would be the one assigned to the interface through which rtsol
> messages are routed. There are two places this could be determined
> and set:
> 
>  a) the ISATAP kernel code
>  b) init scripts that set up the is0 interface
> 
> Either way, the is0 interface can't be brought up until all IPv4
> configuration is done.  Thus, since special care will be needed to
> configure ISATAP anyway, I would say (b) is more appropriate.
We have also mechanism to run setup things after network starts, see
"init.ipv6-global" parameter "start post". Perhaps a better hook. Or
using something similar like current 6to4 setup.


>     RADDR=192.168.1.1     (or whatever the ISATAP router is)
>     LADDR=`ip route get $RADDR | head -1 | awk '{ print $(NF) }'`
>     ip tunnel add is0 mode isatap local $LADDR v4any $RADDR ttl 64
>     ip link set is0 up
> 
> Does anybody have any other suggestions?  -Nathan
Sounds similar to 6to4 setup in "ifup-ipv6", have a look there. I can
add some isatap functions also in "network-functions-ipv6" - or you
contribute them.

        Peter