The first line in our example creates an active default route. This default route is used during the RIP startup period, but after RIP is up and running, this default router is expected to be an active participant in the routing protocol. If you use a default route when running a routing protocol, use an active default route. A static default route can defeat the purpose of a dynamic routing protocol by not allowing the protocol to update the route when network conditions change. The second line creates a static route to subnet 172.16.50.0 through router 172.16.55.36. Because this is a passive route, 172.16.55.36 does not need to run RIP. The only reason to create such a route would be that 17216.55.36 does not run RIP. routed is adequate for some small networks. It requires no installation and very little configuration. However, it is antiquated software that is not suitable for many networks. In particular, it does not support classless IP addresses. If you use classless IP addresses, run a modern routing protocol that supports address masks. Some Linux distributions no longer provide routed, preferring to rely on more modern routing software. Linux offers two different software packages that provide modern routing protocols. The gateway daemon (gated) is a routing software package found on many Unix systems. Zebra is a routing software package from GNU. These packages provide Linux systems with access to interior and exterior routing protocols that normally run only on dedicated routing hardware, such as Cisco routers. Routing with Zebra Zebra is a routing software package that provides support for RIP, RIPv2, OSPF, and BGP. In addition, Zebra provides support for IPv6 routing with both the RIPng protocol and the OSPFv6 protocol. There are internal and external aspects to routing software. On the external side, routing software runs a protocol to exchange routing information with external routers. On the internal side, routing software processes the information learned from the protocol, selects the best routes, and updates the kernel routing table. This internal process increases in complexity when running multiple protocols because it is possible for a router to receive routes to the same destination from different routing protocols. Each protocol uses its own metric for selecting the best route. If each protocol independently updated the routing table, chaos could ensue. To support multiple protocols, and in particular exterior routing protocols, Zebra provides a way to compare incompatible metrics and select the best route. It does this using a value it calls distance, which is an arbitrary number from 1 to 255. The higher the distance number of the protocol that provides the route, the less preferred the route. Each protocol has a default distance value assigned to it, which you can override in the configuration. Zebra uses a modular architecture, with separate programs handling different routing tasks. At this writing, the Zebra suite includes the following key programs: zebra zebra is the routing manager. It updates the kernel routing table with the routes received from the various routing protocols. All protocols update the table through the zebra routing manager. ripd ripd provides the RIP and RIPv2 routing protocols. ospfd ospfd provides the OSPF routing protocol. 206
Note: If you are looking for good and quality webspace to host and run your java application check Actions java hosting services