netdev - Re: [PATCH 1/2] IPV6: remove addresses and routes when carrier is lost

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080603144056.2c7ec127@extreme>
Date:	Tue, 3 Jun 2008 14:40:56 -0700
From:	Stephen Hemminger <shemminger@...tta.com>
To:	David Miller <davem@...emloft.net>
Cc:	yoshfuji@...ux-ipv6.org, netdev@...r.kernel.org
Subject: Re: [PATCH 1/2] IPV6: remove addresses and routes when carrier is
 lost

On Tue, 03 Jun 2008 12:06:40 -0700 (PDT)
David Miller <davem@...emloft.net> wrote:

> From: Stephen Hemminger <shemminger@...tta.com>
> Date: Tue, 3 Jun 2008 11:34:11 -0700
> 
> > On Tue, 03 Jun 2008 10:53:08 -0700 (PDT)
> > David Miller <davem@...emloft.net> wrote:
> > 
> > > If it's a route behavioral attribute, make it as such and add
> > > a new rtnetlink route attribute.  If it's not there, existing
> > > behavior is maintained.
> > 
> > How would this work for system generated routes which occur
> > when address is added to interface?
> 
> Ok, then this takes us back to making userland take care of it.
> 
> You say this is difficult, by how different is this from any
> other kind of event response and synchronization that these
> routing daemons have to do already?

The problem is more that the zebra code is keeping track of the
RIB and has flags as well. Also, since maintainers are BSD/Solaris
based, it makes life harder. 

Have already fixed a number of bugs in that area, of the route
code where connected and recursive routes aren't getting cleared.
It's not impossible to fix, just a bigger burden.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html