multicasting protocol, such as RIPv2, on this interface. The second interface command is much like the first, except that it does not set the multicast flag. The log file command defines the file into which zebra should write its logging information. In Listing 7.5, the log is written to /var/log/zebra.log. Alternatives to logging to a specific file are to use the log stdout command to log to standard output or the log syslog command to log through syslogd. The last command in Listing 7.5 defines a static route. Although static routes may be distributed by protocols configured in other files, such as ripd.conf, the static routes are defined in the zebra.conf file. The keywords ip route are followed by the destination of the route and then the router used to reach that destination. In Listing 7.5, the destination is network number 172.16.50.0. A 24-bit address mask is being used to match addresses to the destination. The gateway for the route is 172.16.1.50. Of course, this is just an example. You probably won’t use static routes when you run routing protocols. Two lines in the zebra.conf file shown in Listing 7.5 define passwords for the vtysh interface. This file should therefore be readable only by administrators. Before going on to the configuration of individual routing protocols, let’s look at how these passwords are put to use for the vtysh interface. Using vtysh The vtysh tool provides an interactive interface into the zebra routing manager and each routing daemon. vtysh allows you to examine and modify the configuration of each program in the Zebra suite. Listing 7.6 shows a vtysh session in which the current zebra configuration is examined. In a later example, this configuration will be modified with vtysh. Listing 7.6: Examining zebra.conf through the vtysh Interface [root]# cat /etc/zebra/zebra.conf password Wats?Watt? enable password CHLLlns [root]# service zebra start Starting zebra: [ OK ] [root]# telnet localhost zebra Trying 127.0.0.1… Connected to localhost. Escape character is ‘^]’. Hello, this is zebra (version 0.91a). Copyright 1996-2001 Kunihiro Ishiguro. User Access Verification Password: Wats?Watt? junko.foobirds.org> enable Password: CHLLlns junko.foobirds.org# write terminal Current configuration: ! password Wats?Watt? enable password CHLLlns ! interface lo ! interface eth0 ! line vty 210
Note: If you are looking for cheap and reliable provider to host and run your servlet application check Vision servlet hosting services