| To: | pekkas@xxxxxxxxxx |
|---|---|
| Subject: | Re: 2.4.21+ - IPv6 over IPv4 tunneling broken |
| From: | YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx> |
| Date: | Fri, 11 Jul 2003 01:18:58 +0900 (JST) |
| Cc: | cat@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, yoshfuji@xxxxxxxxxxxxxx |
| In-reply-to: | <Pine.LNX.4.44.0307101906160.18224-100000@netcore.fi> |
| Organization: | USAGI Project |
| References: | <20030711.005542.04973601.yoshfuji@linux-ipv6.org> <Pine.LNX.4.44.0307101906160.18224-100000@netcore.fi> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
In article <Pine.LNX.4.44.0307101906160.18224-100000@xxxxxxxxxx> (at Thu, 10 Jul 2003 19:08:20 +0300 (EEST)), Pekka Savola <pekkas@xxxxxxxxxx> says: > While technically correct, I'm still not sure if this is (pragmatically) > the correct approach. It's OK to set a default route to go to the > subnet routers anycast address (so, setting a route to prefix:: should > not give you EINVAL). But, on the other side cannot use prefix::, and the setting is rather non-sense. We should educate people not to use /127; use /64 instead. v6ops? :-) -- Hideaki YOSHIFUJI @ USAGI Project <yoshfuji@xxxxxxxxxxxxxx> GPG FP: 9022 65EB 1ECF 3AD1 0BDF 80D8 4807 F894 E062 0EEA |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: 2.4.21+ - IPv6 over IPv4 tunneling b0rked, Pekka Savola |
|---|---|
| Next by Date: | Re: 2.4.21+ - IPv6 over IPv4 tunneling broken, Pekka Savola |
| 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 broken, Pekka Savola |
| Indexes: | [Date] [Thread] [Top] [All Lists] |