From: Mika Liljeberg <mika.liljeberg@welho.com>
To: "Mika Penttilä" <mika.penttila@kolumbus.fi>
Cc: Pekka Savola <pekkas@netcore.fi>, Andre Tomt <andre@tomt.net>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: 2.4.21+ - IPv6 over IPv4 tunneling b0rked
Date: 11 Jul 2003 17:32:34 +0300 [thread overview]
Message-ID: <1057933954.695.6.camel@hades> (raw)
In-Reply-To: <3F0EC96D.6080102@kolumbus.fi>
[-- Attachment #1: Type: text/plain, Size: 2030 bytes --]
On Fri, 2003-07-11 at 17:27, Mika Penttilä wrote:
> afaics, ipv6_addr_type() checks just for some rfc-specified reserved
> anycast addresses, not the ones in device list. Anyway, it will surely
> also bail out from the loopback test (anycast subnet router address is
> ours).
Nope, since the tunnel interface will have 2002::/16. It seems to work
with the attached patch (against 2.4.21-ac4). A small fix to sit was
required as well. Look:
hades:~# ifconfig 6to4
6to4 Link encap:IPv6-in-IPv4
inet6 addr: ::213.243.180.94/128 Scope:Compat
inet6 addr: 2002:d5f3:b45e::1/16 Scope:Global
UP RUNNING NOARP MTU:1480 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:416 (416.0 b) TX bytes:496 (496.0 b)
hades:~# ip -6 route list
::/96 via :: dev 6to4 metric 256 mtu 1480 advmss 1420
2002::/16 dev 6to4 proto kernel metric 256 mtu 1480 advmss 1420
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440
fe80::/64 dev 6to4 proto kernel metric 256 mtu 1480 advmss 1420
ff00::/8 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440
ff00::/8 dev 6to4 proto kernel metric 256 mtu 1480 advmss 1420
default via 2002:c058:6301:: dev 6to4 metric 1024 mtu 1480 advmss 1420
hades:~# ping6 -c4 -n www.ipv6.org
PING www.ipv6.org(2001:6b0:1:ea:a00:20ff:fe8f:708f) 56 data bytes
64 bytes from 2001:6b0:1:ea:a00:20ff:fe8f:708f: icmp_seq=1 ttl=250 time=207 ms
64 bytes from 2001:6b0:1:ea:a00:20ff:fe8f:708f: icmp_seq=2 ttl=250 time=206 ms
64 bytes from 2001:6b0:1:ea:a00:20ff:fe8f:708f: icmp_seq=3 ttl=250 time=177 ms
64 bytes from 2001:6b0:1:ea:a00:20ff:fe8f:708f: icmp_seq=4 ttl=250 time=78.5 ms
--- www.ipv6.org ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3030ms
rtt min/avg/max/mdev = 78.547/167.637/207.698/52.821 ms
Anyone see any problems with this?
MikaL
[-- Attachment #2: 6to4.udiff --]
[-- Type: text/plain, Size: 881 bytes --]
--- route.c.org 2003-07-11 16:41:55.000000000 +0300
+++ route.c 2003-07-11 16:42:16.000000000 +0300
@@ -743,7 +743,7 @@
some exceptions. --ANK
*/
err = -EINVAL;
- if (!(gwa_type&IPV6_ADDR_UNICAST))
+ if (!(gwa_type&(IPV6_ADDR_UNICAST|IPV6_ADDR_ANYCAST)))
goto out;
grt = rt6_lookup(gw_addr, NULL, rtmsg->rtmsg_ifindex, 1);
--- sit.c.org 2003-07-11 16:57:53.000000000 +0300
+++ sit.c 2003-07-11 17:17:42.000000000 +0300
@@ -495,10 +495,13 @@
addr_type = ipv6_addr_type(addr6);
}
- if ((addr_type & IPV6_ADDR_COMPATv4) == 0)
- goto tx_error_icmp;
+ if ((addr_type & IPV6_ADDR_COMPATv4))
+ dst = addr6->s6_addr32[3];
+ else
+ dst = try_6to4(addr6);
- dst = addr6->s6_addr32[3];
+ if (!dst)
+ goto tx_error_icmp;
}
if (ip_route_output(&rt, dst, tiph->saddr, RT_TOS(tos), tunnel->parms.link)) {
next prev parent reply other threads:[~2003-07-11 14:32 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 15:43 2.4.21+ - IPv6 over IPv4 tunneling b0rked CaT
2003-07-10 15:55 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-10 15:58 ` CaT
2003-07-10 16:08 ` Pekka Savola
2003-07-10 16:18 ` 2.4.21+ - IPv6 over IPv4 tunneling broken YOSHIFUJI Hideaki / 吉藤英明
2003-07-10 16:19 ` Pekka Savola
2003-07-13 14:49 ` 2.4.21+ - IPv6 over IPv4 tunneling b0rked Anand Kumria
2003-07-13 16:23 ` Pekka Savola
2003-07-10 19:57 ` Mika Penttilä
2003-07-10 16:27 ` Mika Liljeberg
2003-07-10 23:39 ` CaT
2003-07-11 0:04 ` Mika Liljeberg
2003-07-11 1:49 ` Andre Tomt
2003-07-11 2:03 ` Mika Liljeberg
2003-07-11 2:03 ` 2.4.21+ - IPv6 over IPv4 tunneling broken YOSHIFUJI Hideaki / 吉藤英明
2003-07-11 4:51 ` 2.4.21+ - IPv6 over IPv4 tunneling b0rked Pekka Savola
2003-07-11 5:20 ` Mika Liljeberg
2003-07-11 5:22 ` Pekka Savola
2003-07-11 5:39 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-11 8:46 ` Pekka Savola
2003-07-11 9:04 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-11 9:39 ` Mika Penttilä
2003-07-11 10:03 ` Pekka Savola
2003-07-11 10:47 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-11 10:47 ` Pekka Savola
2003-07-11 10:59 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-11 10:59 ` Pekka Savola
2003-07-11 11:03 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-11 11:04 ` Pekka Savola
2003-07-11 11:36 ` Mika Liljeberg
2003-07-11 11:48 ` Pekka Savola
2003-07-11 12:09 ` Mika Liljeberg
2003-07-11 12:48 ` Mika Penttilä
2003-07-11 13:38 ` Mika Liljeberg
2003-07-11 14:27 ` Mika Penttilä
2003-07-11 14:32 ` Mika Liljeberg [this message]
2003-07-11 15:16 ` Mika Penttilä
[not found] <20030710.214551.08349572.davem@redhat.com>
2003-07-14 23:49 ` kuznet
2003-07-15 6:14 ` Pekka Savola
2003-07-15 14:46 ` kuznet
2003-07-15 17:29 ` Pekka Savola
2003-07-15 23:19 ` kuznet
2003-07-16 6:03 ` Pekka Savola
2003-07-17 0:03 ` kuznet
2003-07-17 6:50 ` Pekka Savola
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1057933954.695.6.camel@hades \
--to=mika.liljeberg@welho.com \
--cc=andre@tomt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.penttila@kolumbus.fi \
--cc=netdev@oss.sgi.com \
--cc=pekkas@netcore.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).