[ale] Routing Questions

[Matt Shade]

Basically, yes. To put it another way - what's to prevent me from pointing
MY 192.168.2.0 network at skylab and capturing your traffic?

The 192.168.x.x networks are essentially "non-existant" on the internet.
"You can't get there from here" without some sort of encapsulation, which is
the reason for the VPN.

matt shade
www.threekay.com


----- Original Message -----
From: "Chris Fowler" <cfowler at outpostsentinel.com>
To: ale at ale.org
To: "Byron A Jeff" <byron at cc.gatech.edu>
Cc: <ale at ale.org>
Sent: Friday, November 30, 2001 23:14
Subject: RE: [ale] Routing Questions


> So,  see if I understand this right.
>
> Becasue I have chosen to use private IP's on each eand, those packets by
> definition are not routeable.
> If they were public then it should have worked?
>
> I wanted to get basic routing doen then move to tunnel and encryption.  I
> guess I'll  skip the test of pinging machines on both sides and begin
> working directly on a tunnel.
>
> Technically why can I not tell the kernel to send all pakets for
192.168.2.0
> to skylab and tell sky lab the reverse to send back to Mir?  Is it a
> technical limitation or the fact the IPs are private?
>
> Thanks,
> Chris Fowler
>



---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
sent to listmaster at ale dot org.