On Mon, 2008-06-16 at 10:22 +0200, Hannes Gredler wrote:
> Bernd Petrovitsch wrote:
> > Then I don't understand the bug.
> 
> there is a couple of things:
> 
> 1. a tc entry may timeout, gets not refreshed.
> 
> 2. a tc_entry is the attachment point for rt_paths
>     --> i.e. if a tc_entry goes away then all the
>     rt_paths are flushed too.
> 
> 3. the hna_entry and hna_nets are independent of the
>     tc_entry. the rt_path is only created when a HNA
>     net is fresh created.
> 
> now consider the following series of events.
> 
> 1. tc goes away (note that the HNA is still valid)
>     the route shas been removed from the kernel since the
>     tc is not reachable anymore.
> 
> 2. the tc is updated. now the rt_path is not resinserted,
>     since the hna_net was not changed, did get properly refreshed.
>
> you only get back the hna net if it times out (is removed) and later on
> gets refreshed and thehna_net is re-created.

Hmm, I have a communication problem. I understand it then before.

IMHO if a node vanishes, the HNAs from that node should also vanish. It
doesn't make much sense to keep the default route if the "gateway node"
announcing it is not reachable anymore.

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services




