Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

Appendix D: Configuring Dynamic Routing with RIP
RIP with Sidewinder G2 using transparent IP addressing
For this example, Router_a will broadcast UDP RIP packets to
SidewinderG2_b but they will be dropped. Because the Sidewinder G2 now
supports RIP, the Sidewinder G2 can be configured to act as a router and
actively participate in the dynamic RIP processing. In order to pass data traffic
through the Sidewinder G2, however, some proxy or server must be configured
and enabled.
The assumption for this discussion is that the administrator has configured the
Sidewinder G2 Telnet proxy. The administrator must also enable the rule
allowing trusted burb-to-Internet burb traffic from the Telnet client to the Telnet
Server. Also, to pass the RIP information through the Sidewinder G2s, both
systems must configure and enable the routed server.
For discussion purposes, the administrator must use the Admin Console to
configure routed on the Internet burb for the following options:
• Advertise routing information: yes
• Advertise as default gateway: no
• Receive routing information from other routers: yes
• Routes from burbs: none
Also, routed on the trusted burb must be configured as follows:
• Advertise routing information: yes
• Advertise as default gateway: no
• Receive routing information from other routers: no
• Routes from burbs: Internet (2)
Given the above configuration, both Sidewinder G2s will do the following:
• broadcast the external routing table information to Router_a (so Router_a
knows when the link is up or down)
• receive routing information from Router_a (all Bizco’s routing information)
and update the external routing table
• broadcast both the internal and external routing information into CorpCity’s
network (which provides CorpCity’s) networks with routing information to
Bizco’s network)
• NOT listen to any RIP broadcasts from the CorpCity network.
Important: The last bullet here is VERY IMPORTANT. This will be discussed in
more detail later in this document.
As in the above discussion, when the Telnet client needs to connect to the
Telnet server, it sends a TCP connection request to Router_b because its
internal default route points to Router_b. Router_b receives the connection
frame and because the route to the Bizco network is shorter via Router_a (3
617