The next statement is a protocol statement that enables RIPv2. Except for two differences, it is identical to the statement used in Listing 7.15 to enable RIPv2 for the host. The first difference is that the router will advertise RIPv2 routes, as indicated by the broadcast keyword. The second difference is that the configuration defines the RIP metric used to advertise routes learned from other protocols, which can be any valid RIP metric value. This router learns routes from OSPF that do not have a valid RIP metric. The defaultmetric clause tells gated to use a cost of 5 to advertise those routes in RIP updates. This clause is required to make the routes learned from OSPF available to the RIPv2 system. Without it, the OSPF routes are considered “unreachable” by the RIPv2 systems. The final protocol statement in the sample gated.conf file shown in Listing 7.16 enables OSPF. This router connects to the backbone area, as indicated by the keyword backbone. If the router was not connected to the backbone, the area it was connected to would be defined here (for example: area 1). The number that identifies the area is the number that you define when you design the area hierarchy of your OSPF routing domain. The OSPF protocol is also using simple password authentication, as indicated by the authtype simple clause. The interface clause identifies the interface over which OSPF runs and the protocol characteristics related to that interface. The authkey “UTrustME” clause defines the password used to authenticate OSPF routers in this area. The priority 5 clause defines the priority number this system uses when the area elects a designated router. The purpose of the priority number was described in the discussion of Listing 7.13 as part of the ospfd configuration. As a final example of running gated, let’s configure a Linux system to run an exterior gateway protocol. Running BGP with gated In this section, a router is configured to connect the OSPF backbone area described in the preceding section to an external autonomous system using BGP. The configuration for this router is shown in Listing 7.17. Listing 7.17: A gated OSPF/BGP Exterior Router Configuration # Defines our AS number for BGP autonomoussystem 249; # Defines the OSPF router id routerid 172.16.1.5; # Disable RIP rip no; # Enable BGP bgp yes { group type external peeras 164 { peer 26.6.0.103 ; peer 26.20.0.72 ; }; }; # Enable OSPF; subnet 1 is the backbone area; # use password authentication. ospf yes { 223

Hint: If you are looking for very good and affordable webspace to host and run your tomcat hosting application check Virtualwebstudio tomcat web hosting provider