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 with<br />

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

not using<br />

transparent IP<br />

addressing<br />

Figure 250: RIP with the<br />

<strong>Sidewinder</strong> <strong>G2</strong> “spo<strong>of</strong>ing”<br />

the client’s address<br />

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

RIP with <strong>Sidewinder</strong> <strong>G2</strong> not using transparent IP addressing<br />

So what happened to the sessions between <strong>Sidewinder</strong><strong>G2</strong>_b and the client,<br />

and <strong>Sidewinder</strong><strong>G2</strong>_b and the server? These sessions will time-out according<br />

to what has been configured for the Telnet proxy inactivity timer. Currently this<br />

defaults to 2700 seconds, or 45 minutes. Unless the Telnet server also has a<br />

connection time-out, the session will remain between the two systems until the<br />

time-out occurs, at which time the proxy closes both sessions.<br />

What will happen when the route between Router_a and <strong>Sidewinder</strong><strong>G2</strong>_b<br />

becomes available again? The Telnet client sends the frame to Router_d which<br />

will send an ‘ICMP Redirect’ back to the client telling it to communicate through<br />

Router_b. The client will resend the frame to Router_b, which forwards it to the<br />

<strong>Sidewinder</strong> <strong>G2</strong>. Again the <strong>Sidewinder</strong> <strong>G2</strong> has received a frame for which it is<br />

not in session, and it will send a ‘TCP reset’ back to the client, causing the client<br />

to again close the session. As far as the client is concerned the Telnet server has<br />

unexpectedly closed the session. And again, if the client opens a new session<br />

all will be fine. But remember the sessions are timing out between<br />

<strong>Sidewinder</strong><strong>G2</strong>_c and the Telnet server.<br />

Important: The administrator should change this Telnet idle session timer to<br />

something more reasonable such as 10 minutes.<br />

The assumption for this discussion is that the Telnet server must be able to<br />

identify the Telnet clients IP address. The above configuration would not allow<br />

this, the Telnet server will see all sessions from CorpCity network as originating<br />

from the <strong>Sidewinder</strong> <strong>G2</strong>. In Figure 250 as with Figure 249, in order to pass any<br />

traffic through the <strong>Sidewinder</strong> <strong>G2</strong>, some proxy or server must be configured<br />

and enabled.<br />

Bizco<br />

Network<br />

Telnet server<br />

R<br />

router_a<br />

Internet burb trusted burb<br />

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

router_b<br />

CorpCity<br />

Network<br />

To accomplish the ‘spo<strong>of</strong>ing’, you must configure the <strong>Sidewinder</strong> <strong>G2</strong>s generic<br />

TCP proxy to listen on port 23, and enable it to spo<strong>of</strong> the original workstations<br />

IP address (refer to the “use_client_address” feature in the /etc/sidewinder/<br />

conf/tcpgsp.conf file). The administrator must also enable the rule list allowing<br />

internal to external traffic from the Telnet client to the Telnet Server for the<br />

R<br />

Internet burb trusted burb<br />

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

R<br />

router_c<br />

R<br />

Telnet<br />

client<br />

router_d<br />

619

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

Saved successfully!

Ooh no, something went wrong!