Thomas Graf wrote: > Whatever is used, there is a link state detection implemented as a > heartbeat protocol. Even on DC the probing can be done periodically > while the link is up. My point is that there are such things and it's > basically the same as the kernel reporting !IFF_RUNNING. I cannot > imagine that you want the kernel to disable the relevant connected > routes to handle this case.
OSPF doesn't care if there is connected route or not if !IFF_RUNNING. And it doesn't matter if it's demand circuit or usual one. If kernel reports link down (!IFF_RUNNING), no any packets are sent over this link - hellos, LS updates etc. Hellos and other heartbeat mechanisms are used to discover neighbours, not whether link works or not. If link is down, yes, it means that neighbour is down as well. But if neighbour is down, it doesn't mean that link is down. It just means that neighbour isn't considered for routing calculations, but forming adjacencies are still attempted via sending periodical hellos (or whatever keepalive packets). Note, that it really doesn't matter if routes are removed or marked as unusable. Just argument about routing protocols keepalives is completely irrelevant. And in fact Quagga (and probably other routing protocol implementations as well) ignores any connected route add/delete messages at all from kernel. It manages his own connected routes in his own RIB and connected routes are removed from there if !IFF_RUNNING. So, from point of view of routing calculations all works already. The only problem is kernel itself - routing daemon may add really usable route to the network behind directly connected interface, but it will not be used by kernel, because there is connected route in the kernel. -- Hasso Tepper Elion Enterprises Ltd. WAN administrator - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
