18.07.2013 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

RIP processing<br />

on the<br />

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

Appendix D: Configuring Dynamic Routing with RIP<br />

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

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

route between Router_a-to-Router_b has been lost. Router_a looks at its local<br />

routing table and discovers there are two routes, one unreachable, the other<br />

through Router_d. Because Router_d is on the same network as the client,<br />

Router_b sends an ‘ICMP Redirect’ back at the client stating that it can reach<br />

the Telnet server network through Router_d. If the client’s TCP/IP stack is<br />

operating correctly, it updates its local routing table to point that host at<br />

Router_d. The client TCP/IP stack then re-sends its last frame to Router_d.<br />

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

on to Router_a, etc.<br />

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

had happened, and when the link between Router_a and Router_b is reestablished,<br />

the Telnet client again should receive an ‘ICMP Redirect’ from<br />

Router_d pointing it back at Router_a. The session should continue as if nothing<br />

important happened.<br />

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

implement RIP processing on the <strong>Sidewinder</strong> <strong>G2</strong>, a routed server process<br />

must be configured, enabled, and started in the burb expecting to handle RIP<br />

broadcasts. Only one routed may be started per burb, but it will handle all<br />

network interfaces within that burb.<br />

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

following Admin Console options:<br />

• Receive routing information from other routers<br />

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

any interface within that burb and update the local routing table.<br />

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

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

• Advertise routing information<br />

Setting this option to Yes enables routed to broadcast UDP RIP updates,<br />

advertising local routing information available within this burb.<br />

Setting this option to No disables broadcasting <strong>of</strong> any UDP RIP updates.<br />

• Advertise as default gateway<br />

Setting this option to Yes enables routed to send the default route.<br />

Setting this option to No disables sending the default route.<br />

• Advertise burb/routes from burbs<br />

This option specifies which burbs (other than the current burb) should have<br />

their routing information included in RIP updates sent by THIS burb. If no<br />

burbs are listed under this option, routed will only send routing information<br />

about the current burb.<br />

615

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

Saved successfully!

Ooh no, something went wrong!