FWIW --
Another user just complained about the stupidity of requiring using
the "::a.b.c.d" format for creating a tunnel addess as "::/96" is
so-called automatic tunneling using compatible addresses, which is
deprecated -- and this has nothing to do with configured tunneling or
6to4.
So, this is one way of allowing 6to4 addresses as a next-hop.
Hopefully this gets fixed before the third anniversary of this
problem..
---------- Forwarded message ----------
Date: Sat, 23 Jun 2001 23:00:21 +0300 (EEST)
From: Pekka Savola <pekkas@xxxxxxxxxx>
To: netdev@xxxxxxxxxxx
Cc: davem@xxxxxxxxxx, kuznet@xxxxxxxxxxxxx
Subject: patch: ipv6 nexthop can be 6to4 address
Hi,
There's ongoing debate that ipv6 compatible addresses may get deprecated.
Some 6to4 relay routers don't support them anymore. Thus it becomes
necessary to allow nexthop for the default route to native ipv6 to be a
6to4 address.
The current implementation basically assumes the only v6-over-v4 tunneling
method is automatic tunneling with compatible addresses.
Attached patch fixes this.
--
Pekka Savola "Tell me of difficulties surmounted,
Netcore Oy not those you stumble over and fall"
Systems. Networks. Security. -- Robert Jordan: A Crown of Swords
linux-2.4.3-6to4-nexthop.diff
Description: Text document
|