Vladislav, If you use the 'iproute2' package under recent releases of the Linux kernel (e.g. recent releases of 2.4.*), you will see that the command:
# ip tunnel add allows you to add as many auto-tunnel pseudo interfaces as you'd like. For example, try: # ip add tun1 mode sit remote R1 local L1 # ip add tun2 mode sit remote R2 local L2 ... # ip add tunn mode sit remote Rn local Ln and you should see n-many 'tun' pseudo-interfaces pop up when you issue the command: 'ifconfig -a'. (Above, Ri and Li represent the remote and local IPv4 addresses assigned to pseudo-interfaces 'tuni' for 1 <= i <= n). The 'sit0' is simply there as a "base" upon which multiple pseudo-interfaces may be layered. If you get the 'iproute2' package from: http://v6web.litech.org/isatap/ you will see the following when you issue the command: 'ip tunnel help': > Usage: ip tunnel { add | change | del | show } [ NAME ] > [ mode { ipip | gre | sit | isatap } ] > [ remote ADDR ] [ local ADDR ] [ v4any ADDR ] So, to create an ISATAP tunnel, simply use the "mode isatap" directive. Fred [EMAIL PROTECTED] Vladislav Yasevich wrote: > > Fred > > I believe Pekka is comming from the linux implementation point of view > which has only one pseudo-interface (sit0) to act as tunnel endpoint > (at least that's what I see on my linux box). This is really the problem > that leads to not being able to distinguish between tunneling mechanisms. > > -vlad -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [EMAIL PROTECTED] --------------------------------------------------------------------
