Tunnel between two IPv6 islands in an IPv4 ocean?

What would be the "Debian way" to set up a tunnel
between two routers  
running Debian to connect two IPv6 islands in an otherwise
IPv4 ocean?

To be a bit more specific:

There are two groups of us in my University who are
experimenting  
with IPv6.  The rest of the University is entirely IPv4.

Each of these groups has gotten themselves a tunneled router
 
connection to the IPv6 backbone outside the University, and
we can  
communicate using IPv6 by going out to the backbone and back
into the  
University via these two tunnels.

But that seems overly cumbersome.  It would be great if we
could  
connect the two groups directly with an IPv6 on IPv4 tunnel
that  
never leaves the University.  If possible, I'd like to use
two Debian  
machines to do this.  Does anybody know how/if it can be
done?

Thanks!

Rick


-- 
To UNSUBSCRIBE, email to debian-ipv6-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmasterlists.debian.org

Rick Thomas wrote:
>
> What would be the "Debian way" to set up a
tunnel between two routers 
> running Debian to connect two IPv6 islands in an
otherwise IPv4 ocean?
>
> To be a bit more specific:
>
> There are two groups of us in my University who are
experimenting with 
> IPv6.  The rest of the University is entirely IPv4.
>
> Each of these groups has gotten themselves a tunneled
router 
> connection to the IPv6 backbone outside the University,
and we can 
> communicate using IPv6 by going out to the backbone and
back into the 
> University via these two tunnels.
>
> But that seems overly cumbersome.  It would be great if
we could 
> connect the two groups directly with an IPv6 on IPv4
tunnel that never 
> leaves the University.  If possible, I'd like to use
two Debian 
> machines to do this.  Does anybody know how/if it can
be done?
>

It's very easy.

Here an example /etc/network/interfaces extract:

auto ipv6tun
iface ipv6tun inet6 v4tunnel
  address  2001:770:119:1::2
  netmask  64
  endpoint 10.15.30.2
  ttl      64
  up       ip link set mtu 1280 dev ipv6tun
  up       ip route add ::/0 via 2001:770:119:1::1 dev
ipv6tun


The other side obviously would be the opposite:

auto ipv6tun
iface ipv6tun inet6 v4tunnel
  address  2001:770:119:1::1
  netmask  64
  endpoint 10.15.172.10
  ttl      64
  up       ip link set mtu 1280 dev ipv6tun
  up       ip route add ::/0 via 2001:770:119:1::2 dev
ipv6tun



Kind regards,
Martin List-Petersen

-- 
Communication is the beginning of understanding
   -- AT&T


-- 
To UNSUBSCRIBE, email to debian-ipv6-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmasterlists.debian.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


>>>>> "Martin" == Martin
List-Petersen <martinlist-petersen.dk>
writes:
    >> What would be the "Debian way" to set
up a tunnel between two
    >> routers running Debian to connect two IPv6
islands in an
    >> otherwise IPv4 ocean?
    >> 
    >> To be a bit more specific:
    >> 
    >> There are two groups of us in my University who
are experimenting
    >> with IPv6.  The rest of the University is
entirely IPv4.

    Martin> Here an example /etc/network/interfaces
extract:

    Martin> auto ipv6tun iface ipv6tun inet6 v4tunnel
address

  What is described will work, and will work well.
  There is another way to do this, if you are planning to
have more than
two end-points, is you set up the 6to4 addresses on the
routers, and
then just add routes to each other.  (It just scales better,
but if you
have only two sites, Martin's suggestion is as good or
better)
  This has the advantage that it also gives you connectivity
to the
2002: addresses directly, which are somewhat popular among
IPv4-only
home users. 

- -- 
]           Bear: "Me, I'm just the shape of a
bear."          |  firewalls  [
]  Michael Richardson,    Xelerance Corporation, Ottawa, ON 
  |net architect[
]mcrxelerance.com      http://www.san
delman.ottawa.on.ca/mcr/ |device driver[
]panic("Just another Debian GNU/Linux using, kernel
hacking, security guy"); [



  
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Finger me for keys

iQEVAwUBR3O/94CLcPvd0N1lAQLE+QgAkKK7H/7qWiQCwNSuE2AM5yR0vqFE
wwI/
H3kMfBEr0PrUX5KC2ha9A7Bw1pyi/82amg9ACyQq9DDvD7k9eC9aMFxtu+RG
Z+AH
GxwfxW3QiSGgdJn+jwTgQkKxMJ/I1RVdyJZPwsjSANZTf+NIr48/1u7xPI9i
7pGz
DvV9Ckj7yrWaEuFfhMV48WFR/HgFMph73d73H3UYKMY7kAfYSBMrzFcWre9N
CSEO
lomgikf/oDBaPBOO9iOpj15uXiN7eX93WbPWjcqmYEQUPWYy5scGceAOtTQq
UZyr
nCqQvnu4cSFpNiVwray+FYVPeeAB87zUumiwYFUwSmOmCvS/lmbv/Q==
=qRuZ
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to debian-ipv6-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmasterlists.debian.org

Thanks, Michael...  And "Thanks!" very much for
all the good answers  
I've gotten so far on this list.

Substantive reply is continued as a bottom post per Debian
mailing- 
list etiquette requirement...

On Dec 27, 2007, at 10:08 AM, Michael Richardson wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>>>>>> "Martin" == Martin
List-Petersen <martinlist-petersen.dk>  
>>>>>> writes:
>>> What would be the "Debian way" to set
up a tunnel between two
>>> routers running Debian to connect two IPv6
islands in an
>>> otherwise IPv4 ocean?
>>>
>>> To be a bit more specific:
>>>
>>> There are two groups of us in my University who
are experimenting
>>> with IPv6.  The rest of the University is
entirely IPv4.
>
>     Martin> Here an example /etc/network/interfaces
extract:
>
>     Martin> auto ipv6tun iface ipv6tun inet6
v4tunnel address
>
>   What is described will work, and will work well.
>   There is another way to do this, if you are planning
to have more  
> than
> two end-points, is you set up the 6to4 addresses on the
routers, and
> then just add routes to each other.  (It just scales
better, but if  
> you
> have only two sites, Martin's suggestion is as good or
better)
>   This has the advantage that it also gives you
connectivity to the
> 2002: addresses directly, which are somewhat popular
among IPv4-only
> home users.


Can you be a bit more specific?  I'm kinda new at this, and
there are  
a number of things that I imagine might be what you're
referring to  
as "the 6to4 addresses on the routers".

In particular, Martin gave a very detailed example of what
to put in / 
etc/network/interfaces.  I'm still working on understanding
the  
details of how that works (Any pointers to good
documentation on /etc/ 
network/interfaces and the programs that use it would be
greatly  
appreciated!)  If you could give a similar example for three
(or  
more) islands/tunnel-endpoints, it might make things a bit
clearer to  
me.

Thanks very much for all the good answers I've gotten so
far!

Rick


-- 
To UNSUBSCRIBE, email to debian-ipv6-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmasterlists.debian.org

>>>>> "Rick" == Rick Thomas
<rbthomas55pobox.com> writes:
    Rick> Can you be a bit more specific?  I'm kinda new
at this, and
    Rick> there are a number of things that I imagine
might be what
    Rick> you're referring to as "the 6to4 addresses
on the routers".

    Rick> In particular, Martin gave a very detailed
example of what to
    Rick> put in / etc/network/interfaces.  I'm still
working on

h
ttp://people.debian.org/~csmall/ipv6/setup624.html
http://wiki.debian.
org/DebianIPv6

-- 
]           Bear: "Me, I'm just the shape of a
bear."          |  firewalls  [
]  Michael Richardson,    Xelerance Corporation, Ottawa, ON 
  |net architect[
]mcrxelerance.com      http://www.san
delman.ottawa.on.ca/mcr/ |device driver[
]panic("Just another Debian GNU/Linux using, kernel
hacking, security guy"); [



-- 
To UNSUBSCRIBE, email to debian-ipv6-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmasterlists.debian.org