18.07.2013 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

RIP processing on<br />

the <strong>Sidewinder</strong> <strong>G2</strong><br />

RIP processing on the <strong>Sidewinder</strong> <strong>G2</strong><br />

The dynamic routing capability <strong>of</strong> RIP can be seen when the link<br />

between Router_a and Router_b is lost. As soon as Router_b notices<br />

that it is no longer receiving RIP updates from Router_a, it updates its<br />

local routing table hop count for that route to 16 (route unreachable)<br />

and broadcasts this to others on its local network (this is to notify<br />

Router_d).<br />

Next, the Telnet client sends another IP frame to Router_a unaware<br />

that the route between Router_a-to-Router_b has been lost. Router_a<br />

looks at its local routing table and discovers there are two routes, one<br />

unreachable, the other through Router_d. Because Router_d is on the<br />

same network as the client, Router_b sends an ‘ICMP Redirect’ back at<br />

the client stating that it can reach the Telnet server network through<br />

Router_d. If the client’s TCP/IP stack is operating correctly, it updates<br />

its local routing table to point that host at Router_d. The client TCP/IP<br />

stack then re-sends its last frame to Router_d. Router_d receives the<br />

frame and forwards it on to Router_c, which forwards it on to<br />

Router_a, etc.<br />

Important: Note that the TCP session continues on through Router_d as if nothing had<br />

happened, and when the link between Router_a and Router_b is re-established, the Telnet<br />

client again should receive an ‘ICMP Redirect’ from Router_d pointing it back at Router_a.<br />

The session should continue as if nothing important happened.<br />

RIP processing is done via a <strong>Sidewinder</strong> <strong>G2</strong> server process called<br />

routed. To implement RIP processing on the <strong>Sidewinder</strong> <strong>G2</strong>, a<br />

routed server process must be configured, enabled, and started in the<br />

burb expecting to handle RIP broadcasts. Only one routed may be<br />

started per burb, but it will handle all network interfaces within that<br />

burb.<br />

The <strong>Sidewinder</strong> <strong>G2</strong> can be configured to support RIP processing via<br />

the following Admin Console options:<br />

Receive routing information from other routers<br />

Setting this option to Yes enables routed to receive UDP RIP<br />

updates from any interface within that burb and update the local<br />

routing table.<br />

Setting this option to No disables the updating <strong>of</strong> local routing<br />

tables with RIPs received from the local network interfaces.<br />

Configuring Dynamic Routing with RIP D-3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!