> On Mar 5, 2015, at 2:27 PM, Brian E Carpenter <brian.e.carpen...@gmail.com> > wrote: > > Hi, > >> 8. Support for Stub Networks and Stub Routers > ... >> IS-IS supports stub-networks as defined above >> simply by advertising the prefix associated with a link, but not the >> link itself. This is sometimes referred to as a "passive link". >> >> Further an IS-IS router has the ability to set a bit (the overload >> bit) to indicate that it should not be used for any transit traffic, >> and that it will only be considered a destination for the prefixes it >> has advertised, i.e., it is a stub router as defined above. > ... >> As all distance vector protocols, Babel supports fairly arbitrary >> route filtering. Designating a stub network is done with two >> statements in the current implementation's filtering language. > > In a homenet, there must be no manual config. In both cases, how does > this work automatically? How does IS-IS know not to advertise the link > and set the overload bit, and how does Babel know to include those > filtering rules? Or more generally, how does a stub router know that > it's a stub router, when there is no human to tell it so?
For IS-IS, the stub router would know so b/c it can’t be anything else. It is running the stub version of the software. The reason it would be doing this is b/c it’s a very small device not designed to do anything else. BTW, is it true that there must be no manual config, or simply that one cannot rely on manual config? Thanks, Chris. > > Regards > Brian > > _______________________________________________ > homenet mailing list > homenet@ietf.org > https://www.ietf.org/mailman/listinfo/homenet _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
