Technical information

Watson SHDSL Router
Web-based Management Manual
Watson-SHDSL-Router-GUI-Manual.doc
Version 2.3-03
9-102
Revision: 2012-02-29
To activate the routing engine, you need to create a configuration file for the proto-
col daemon, and also for Zebra. Zebra is Quagga's IP routing management dae-
mon, which provides kernel routing table updates, interface lookups, and redistribu-
tion of routes between the routing protocols.
Note: To view examples of the configuration files, browse to
http://www.quagga.net/docs/quagga.pdf .
3. Enter the configuration files into their respective code fields. Alternatively, click
the 'Set Default Values' button to the right of each code field. The default values,
displayed in a field are the following:
 BGP :
!router bgp <AS number> The exclamation mark is Quagga's comment charac-
ter. The router bgp string is a command that activates the BGP daemon. The
exclamation mark emphasizes that the command must be followed by an exact
Autonomous System's ID number.
log syslog A command that instructs the daemon to send its log messages to
the system log.
 OSPF :
router ospf A command that activates the OSPF daemon.
log syslog See the explanation under BGP.
 Zebra
interface ixp1 Instructs the daemon to query and update routing information via
a specific WAN device. It is important that you change the default ixp1 value to
your WAN device name.
log syslog See the explanation under BGP.
4. Click 'OK' to save the settings.
If the OSPF daemon is activated, Watson starts sending the 'Hello' packets to other
routers to create adjacencies. After determining the shortest path to each of the
neighboring routers, Zebra updates the routing table according to the network
changes. If the BGP deamon is activated, Watson starts to advertise routes it uses
to other BGP-enabled network devices located in the neighboring Autonomous
System(s). The BGP protocol uses TCP as its transport protocol. Therefore, Wat-
son first establishes a TCP connection to routers with which it will communicate.
KeepAlive messages are sent periodically to ensure the liveness of the connection.
When a change in the routing table occurs, Watson advertises an Update message
to its peers. This update message adds a new route or removes the unfeasible one
from their routing table.