From: Bernd Eckenfels <ecki-news2002-08@lina.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4 and full ipv6 - will it happen?
Date: Wed, 28 Aug 2002 21:14:46 +0200 [thread overview]
Message-ID: <E17k8H8-0003Le-00@sites.inka.de> (raw)
In-Reply-To: <20020827160722.GA13412@alcove.wittsend.com>
In article <20020827160722.GA13412@alcove.wittsend.com> you wrote:
> It's ignoring something because it's assuming the user knows
> what he's doing and not wanting it to do that? Does not compute.
well, it was not my idea, and i dont think I fully understand all that Scope
stuff in IPv6, but I wanted to say:
The kernel is asuming, that a gateway (ie forward=1) is administrated by a
experienced admin, who knows how to set up all those special V6 prefixes,
but wants to defend internet from admins who do not know.
for a single hoomed host a default route does no harm, compared to a gateway
with wrong site or lionk local scope prefix routes.
> Did you mean 2000::/3 (first two bits zero, next bit 1)? That would
> also cover both the 6bone and production allocations under a slightly
> tighter mask. The /2 would cover :: through 3fff: but the /3
> would cover 2000: through 3fff:. Any reaon why we should care about
> the ::/3 band (:: through 1fff:)?
yes, because it does not maks the link and site local prefix starting with
FE and FF (like fe80::/10)
> Does that imply ipv6 only or does that include ipv4 on those
> tcp6 listens?
well, depends on the kernel we are talking about. I plan to have tcp,tcp46
and tcp6 (of course udp and icmp, too) entries, like BSD has.
> I'm not sure I like the tcp6, since it's not tcp that's
> changed, just the ip layer underneath it. I assume you would also
> have udp6 as well?
yes
> Hmmm... Just be careful not to break too many scripts. Freenet6
> has a template script with their tsp package that, I think, tries to do
> some parsing on that stuff. That script is also broken due to the
> default route sillyness, and I'm going to let them know to change their
> route add from ::/0 to a route add for something between ::/1 and 2000::/3
> (season to taste) to get the default routes working properly.
tspc works fine for me, but you are right breaking scripts is a bit ugly.
Well on the other hand, it wil lalso unbreak some bsd scripts :)
Greetings
Bernd
next prev parent reply other threads:[~2002-08-28 19:10 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-19 4:39 Tomasz Torcz, BG
2002-08-19 4:37 ` David S. Miller
2002-08-19 5:16 ` Tomasz Torcz, BG
2002-08-19 5:12 ` David S. Miller
2002-08-19 23:34 ` Thunder from the hill
2002-08-19 23:23 ` David S. Miller
2002-08-19 23:49 ` Daniel Berlin
2002-08-19 23:54 ` Alan Cox
2002-08-20 0:32 ` Rik van Riel
2002-08-20 13:54 ` kuznet
2002-08-20 6:56 ` Thunder from the hill
2002-08-21 20:24 ` Kelsey Hudson
2002-08-21 21:31 ` Bernd Eckenfels
2002-08-21 21:44 ` Thunder from the hill
2002-08-21 22:03 ` Bernd Eckenfels
2002-08-21 23:13 ` Russell King
2002-08-22 0:05 ` Bernd Eckenfels
2002-08-22 6:08 ` Thunder from the hill
2002-08-26 18:55 ` Kelsey Hudson
2002-08-26 19:44 ` Bernd Eckenfels
2002-08-26 21:51 ` Michael H. Warfield
2002-08-26 23:48 ` Bernd Eckenfels
2002-08-27 16:07 ` Michael H. Warfield
2002-08-28 19:14 ` Bernd Eckenfels [this message]
2002-08-29 2:05 ` Michael H. Warfield
2002-08-29 18:47 ` Bernd Eckenfels
2002-08-21 22:08 ` Alan Cox
2002-08-22 6:12 ` Thunder from the hill
2002-08-22 12:27 ` Rik van Riel
2002-08-22 18:22 ` Alan Cox
2002-08-22 18:26 ` Bernd Eckenfels
2002-08-22 19:19 ` Russell King
2002-09-12 15:06 ` Petr Baudis
2002-09-13 1:47 ` David S. Miller
2002-08-19 7:27 ` Chris Wedgwood
2002-08-19 12:25 ` Alan Cox
2002-08-19 22:39 ` Kelsey Hudson
2002-08-20 6:17 ` Val Henson
2002-08-19 23:56 Leif Sawyer
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=E17k8H8-0003Le-00@sites.inka.de \
--to=ecki-news2002-08@lina.inka.de \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®