-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On May 23 2002 15:31 -0400, Aaron Angel wrote:
> > Set up a "pointopoint" interface with an IPv6 remote endpoint, and
> > route all IPv4 traffic through it? (route -A inet add inet dev ${IF})
> >
> > I'm just guessing, but that's how I would most likely try it.
>
> Actually it's not that simple with Linux; Linux has to complicate
> things way beyond the point of sanity. Each tunnel uses two devices,
> sitN (N > 0), and sit0. All I know is that through the various times
> I've tried to configure a tunnel in Linux, it's taken assigning
> addresses to sitN and sit0 in some extremely awkward fashion that by
> the time I figured it out, I have no clue how I figured it out. And
> the HOW-TOs are fairly useless...so you're likely on your own, unless
> someone has done some research using the scientific method and lots
> and lots of documentation. (-: You think I'm joking...
I have fought IPv6 in v4 tunnel setup on Linux myself, and know it's
not very simple. But after a while I was able to get it down this in
order to set the box up as a router to UUNet:
echo 1 > /proc/sys/net/ipv6/conf/all/forwarding
/usr/sbin/radvd
/sbin/ifconfig sit0 tunnel ::158.43.131.66
/sbin/ifconfig sit1 up
/sbin/ifconfig sit1 add 2001:600:4:8d9::2
/sbin/ifconfig sit0 up tunnel ::158.43.131.66
/sbin/ifconfig sit1 up
/sbin/ifconfig eth1 inet6 add 2001:600:101f::1/64
/sbin/ifconfig sit0 up tunnel ::158.43.131.66
/sbin/route -A inet6 add 2000::/3 gw ::158.43.131.66 dev sit0
/sbin/route -A inet6 add 2001:600:4:8d3::1/128 dev sit1
/sbin/route -A inet6 add 2001:600:4:8d9::1/128 dev sit1
In this case:
* 158.43.131.66 is the remote IPv4 endpoint
* Remote IPv6 tunnel endpoint is 2001:600:4:8d9::1/64
* My IPv6 tunnel endpoint is 2001:600:4:8d9::2/64
* My IPv6 allocation is 2001:600:101f::/48
* My router's IPv6 address is 2001:600:101f::1/64
I am sure there is a lot of redundancy in there, but it does bring up
IPv6 networking fine. I thought maybe one could do the reverse (just
use IPv6 addresses for the tunnel endpoint and IPv4 in the routing
table) to set up an IPv4-in-v6 tunnel.
Obviously, besides what I have shown above I also have firewalling in
place.
Michael Kj�rling
- --
Michael Kj�rling -- Programmer/Network administrator ^..^
Internet: [EMAIL PROTECTED] -- FidoNet: 2:204/254.4 \/
PGP: 95f1 074d 336d f8f0 f297 6a5b 2aa3 7bfd 8a70 e33e
``And indeed people sometimes speak of man's "bestial" cruelty, but
this is very unfair and insulting to the beasts: a beast can never be
so cruel as a man, so ingeniously, so artistically cruel.''
(Ivan Karamazov, in Dostoyevsky's 'The Brothers Karamazov')
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Public key is at http://michael.kjorling.com/contact/pgp.html
iD8DBQE875H5KqN7/Ypw4z4RApk4AJ4z4aE/sodgAua/j7hdpvDKW9XF3gCg8rw+
YadkvjcOt0AVsoKVp42V9lA=
=Xstr
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
