| To: | YOSHIFUJI Hideaki / ???? <yoshfuji@xxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: 2.4.21+ - IPv6 over IPv4 tunneling b0rked |
| From: | Mika Penttilä <mika.penttila@xxxxxxxxxxx> |
| Date: | Thu, 10 Jul 2003 22:57:12 +0300 |
| Cc: | cat@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, pekkas@xxxxxxxxxx |
| References: | <20030710154302.GE1722@xxxxxxxxxx> <20030711.005542.04973601.yoshfuji@xxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 |
But 3ffe:8001:000c:ffff::36 is _not_ subnet routers anycast address. Anyway, looks like a bug to me... --Mika YOSHIFUJI Hideaki / ???? wrote: In article <20030710154302.GE1722@xxxxxxxxxx> (at Fri, 11 Jul 2003 01:43:03 +1000), CaT <cat@xxxxxxxxxx> says:With 2.4.21-pre2 I can get a nice tunnel going over my ppp connection and as such get ipv6 connectivity. I think went to 2.4.21 and then to 2.4.22-pre4 and bringing up the tunnel fails as follows::ip addr add 3ffe:8001:000c:ffff::37/127 dev sit1ip route add ::/0 via 3ffe:8001:000c:ffff::36 RTNETLINK answers: Invalid argumentThis is not bug, but rather misconfiguration;you cannot use prefix::, which is mandatory subnet routers anycast address, as unicast address.Thank you. |
| Previous by Date: | Re: [PATCH - RFC] [1/2] 2.6 must-fix list - kernel error reporting, Jim Keniston |
|---|---|
| Next by Date: | [PATCH][2.4] more atm changes backported to 2.4, chas williams |
| Previous by Thread: | Re: 2.4.21+ - IPv6 over IPv4 tunneling b0rked, Pekka Savola |
| Next by Thread: | Re: 2.4.21+ - IPv6 over IPv4 tunneling b0rked, Mika Liljeberg |
| Indexes: | [Date] [Thread] [Top] [All Lists] |