[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20131017.161909.251791393805386332.davem@davemloft.net>
Date: Thu, 17 Oct 2013 16:19:09 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: ja@....bg
Cc: kristian.evensen@...il.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next] fib_trie: Send RTM_DELROUTE when link goes
down
From: Julian Anastasov <ja@....bg>
Date: Thu, 17 Oct 2013 22:52:43 +0300 (EEST)
>
> Hello,
>
> On Thu, 17 Oct 2013, Kristian Evensen wrote:
>
>> From: Kristian Evensen <kristian.evensen@...il.com>
>>
>> When a link is set as down using for example "ip link set dev X down", routes
>> are deleted, but RTM_DELROUTE messages are not sent to RTNLGRP_IPV4_ROUTE. This
>> patch makes trie_flush_list() send a RTM_DELROUTE for each route that is
>> removed, and makes rtnelink route deletion behavior consistent across commands.
>> The parameter lists for trie_flush_list() and trie_flush_leaf() are expanded to
>> include required information otherwise unavailable in trie_flush_list().
>>
>> One use case that is simplified by this patch is IPv4 WAN connection monitoring.
>> Instead of listening for and handling both RTM_*ROUTE and RTM_*LINK-messages, it
>> is sufficient to handle RTM_*ROUTE.
>
> IIRC, such notifications were not implemented
> to avoid storms to routing daemons. Not sure if this is
> still true.
I'm definitely not applying this patch.
Routing daemons maintain the routing table internally, and they
therefore can purge their internal data structures when the link
down event occurs.
This is how it has worked forever and for real BGP tables the
RTM_DELROUTE traffic would be enormous and at nearly DoS levels
for anyone listening for them.
--
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
Powered by blists - more mailing lists