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.

D<br />

RIP with standard IP routers<br />

Figure D-1. Dynamic<br />

routing a with standard<br />

IP route<br />

D-2 Configuring Dynamic Routing with RIP<br />

Bizco<br />

Network<br />

Telnet server<br />

R<br />

router_a<br />

router_b<br />

CorpCity<br />

Network<br />

Note: This figure assumes that all routers (a, b, c, and d) are exchanging RIP packets<br />

between each other every 30 seconds.<br />

In this example, it is unnecessary for the Telnet server and the client<br />

to be accepting RIP packets. The server can statically configure its<br />

gateway to be Router_a. The client can statically configure its gateway<br />

to Router_b.<br />

The Telnet client has two different possible paths <strong>of</strong> reaching the<br />

server: (1) via Router_b-to-Router_a, and (2) via Router_d-to-Router_cto-Router_a.<br />

Examining the routing table on Router_b, you would find<br />

that there are two possible routes to the Bizco network, one with a<br />

hop count equal to two (through Router_a), the other with a hop<br />

count to three (through Router_d).<br />

When the Telnet client needs to connect to the Telnet server, it sends<br />

a TCP connection request to Router_b because its internal default<br />

route points to Router_b. Router_b receives the connection frame and<br />

because the route to the Bizco network is shorter via Router_a (two<br />

hops verses three hops), it forwards the connection frame on to<br />

Router_a. Router_a forwards the frame into the Bizco network and it<br />

eventually gets received by the Telnet server. The Telnet server builds<br />

and sends a reply frame back, this frame typically follows the same<br />

route back to the client. The two systems have established a<br />

connection.<br />

R<br />

R<br />

router_c<br />

R<br />

Telnet<br />

client<br />

router_d

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

Saved successfully!

Ooh no, something went wrong!