Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why does routed not work for long periods of time under SR10.2? Are there any known TCP/IP problems with routing?

0
Posted

Why does routed not work for long periods of time under SR10.2? Are there any known TCP/IP problems with routing?

0

The SR10.2 version of routed would stop broadcasting and listening to RIP routes after about 20 minutes. This is due to a feature in DomainOS which keeps applications from receiving their own broadcast packets. BSD routed depends on this feature in stand-alone networks to determine if there is a problem with the physical interface. From the SR10.3 release notes: 4.2.4 TCP/IP Bug in routed The routed command does not detect an inactive physical interface unless the interface is specifically configured “down” with the ifcon- fig command. SR10.2 routed aged active routes (APR 000DDC72) The routed command was timing out active physical interfaces. We’ve modified routed to prevent it from timing out, and therefore marking “down”, interfaces that are configured “up” with the ifconfig command. The routed command does, however, time out interfaces that are configured “down” with the ifconfig command. ( 2/15/94, Eric Bratton ) If you are finding that anything depend

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123