
Configuring the Remote Annex
115623B Rev. 00
BayStream Multiservice Software Version 7.2
4-9
Although the routes required for passive RIP need not be defined after you enable
active RIP, you may want to define a default route and one or more static routes
for other purposes. For example, a default router can act as a bottleneck through
which all traffic to and from a network must pass. You can also use static routes to
reach routers that are not running active RIP.
To define default and static routes that remain across Annex boots, enter them in
the config.annex file. You can define routes anywhere in the configuration file, but
routes not defined in an “annex...end” or “subnet...end” block are discarded and
not cached if their interfaces are not operational when the Annex is booted.
Typically, the Ethernet interface is operational immediately, but SLIP and PPP
interfaces may take longer to come up.
Configuring the Annex to Advertise RIP 1 and/or RIP 2 Updates
By default, active RIP sends RIP version 2 updates to the IP broadcast address, so
that both RIP 1 and RIP 2 systems can receive them. This assumes that
rip_send_version
is set to compatibility, which is the default. It also assumes the
routers on your network accept both RIP 1 and RIP 2 updates. Although
discarding RIP 2 updates violates the RIP 1 RFC (1058), some RIP
implementations written before the RFC still do so. If you have both RIP 1 and
RIP 2 nodes on your network, make sure that there are no RIP 1 implementations
that discard RIP 2 packets. If there are, use the
na
or
admin
mode to set the
rip_send_version
parameter to 1, as shown in the following example:
annex:
su
password:
annex#
admin
Annex administration Remote Annex R13.3, 72 ports
admin:
set interface=all rip_send_version 1
You may need to reset the appropriate port or Annex subsystem, or reboot the
Annex for changes to take effect:
admin:
quit
annex#
boot
The
boot
command is required in the preceding example because you are setting
en0. If en0 were not among the interfaces, you could substitute the
admin
command
reset interface
for the
boot
command.
Summary of Contents for Bay Dial VPN
Page 10: ...x BayStream Multiservice Software Version 7 2 115623B Rev 00 ...
Page 12: ......
Page 14: ......
Page 32: ......
Page 52: ......
Page 68: ......
Page 92: ......
Page 106: ......
Page 146: ......
Page 161: ...Syslog Messages 115623B Rev 00 BayStream Multiservice Software Version 7 2 B 9 ...