>> I may have misunderstood -- but are you saying that you have the >> technology to perform bidirectional redistribution between two very >> different routing protocols in an unadministered network, and >> guarantee the absence of persistent routing loops without making >> any assumptions about the topology?
> Have you run, say, RIPng, on one network interface facing the > interior of a network while running IS-IS on another interface on > the same router? Yes, I have. On one router this is easy. You obviously need two routers in order to create a loop. > Once each routing is configured and redistributing routes between, > what is the issue? First Google hit for "redistribution persistent loop cisco" [1]: "If you misconfigured Route Redistribution, this will lead to sub-optimal routing and even severe instabilities such as route oscillations and persistent routing loops. [...] To avoid routing loops, a route received from a routing instance must not be re-injected back into the same instance." In short, you must configure your redistribution filters to ensure that there isn't a redistribution loop. While that's in principle possible in a managed network (but error-prone and fragile), it's suicide in an unmanaged network. Hemant, the fact that general redistribution is impossible in unmanaged networks is the very reason for the existence of Babel, a single protocol that is reasonably efficient on both on your favourite gigabit technology and on the unstable, non-transitive, lossy bits that people will include in their networks, whether Mikael likes it or not. If redistribution were as easy as you make it, you'd just run IS-IS on the wired bits and OLSRv2 on the meshy bits, both of which are fine protocols in their particular area of application. [1] https://supportforums.cisco.com/document/12015996/route-redistribution-explained -- Juliusz _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
