netdev
[Top] [All Lists]

Re: [ANN] 2nd STABLE release of USAGI Project

To: Jacek Konieczny <jajcus@xxxxxxx>
Subject: Re: [ANN] 2nd STABLE release of USAGI Project
From: Yuji Sekiya <sekiya@xxxxxxxxxxxxxx>
Date: Tue, 06 Feb 2001 17:04:46 +0900
Cc: netdev@xxxxxxxxxxx
In-reply-to: <20010205113236.B3612@xxxxxxxxxxx>
Organization: Keio University
References: <ur91dim0j.wl@xxxxxxxxxxxxxxxxxxxxx> <20010205101710.B2754@xxxxxxxxxxx> <uhf29iivu.wl@xxxxxxxxxxxxxxxxxxxxx> <20010205105822.A3443@xxxxxxxxxxx> <87g0htsa7c.wl@xxxxxxxxxxxxxxxxxxxxxx> <20010205113236.B3612@xxxxxxxxxxx>
Sender: owner-netdev@xxxxxxxxxxx
User-agent: Wanderlust/2.4.1 (Stand By Me) SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.3 Emacs/20.7 (i386-debian-linux-gnu) MULE/4.0 (HANANOEN)
At Mon, 5 Feb 2001 11:32:36 +0100,
Jacek Konieczny <jajcus@xxxxxxx> wrote:

> > Actually it means default route. I can't see why you announce or add
> > statically the route instead of default route.
> 
> This is not the same as default route. Prefix 2000::/3 does not contain 
> multicast nor link-local and site-local addresses. Only global unicast
> addresses. 

Have you ever seen IPv6 routing table ?? 8)
In routing table, default routes for multicast and link-local address
exist. 

fe80::/10                  ::    UA    256    0        0 eth0
ff00::/8                   ::    UA    256    0        0 eth0

So if a default route exist on routing table, multicast and link-local
packets are not affected. In case of site-local, IMO, it is broken
spec and never work 8)8)8).

Anyway, if you want to mention about filtering invalid packets
with purging default route, I think it should be solved as OPERATIONAL
issues not TECHNICAL issues.

Then I think we should be able to choice using a specific route or
a default route for default unicast routing. Even if the linux kernel
accept default route, you can use a specific route for unicast routing
without default route.

Regards.

-- Yuji Sekiya



<Prev in Thread] Current Thread [Next in Thread>