<< | Thread Index | >> ]    [ << | Date Index | >> ]

To: Jake Bullet <jbullet,AT,cats,DOT,meow,DOT,at>
Subject: Re: Win2k and CIPE
From: Phil Scarratt <fil,AT,draxsen,DOT,com>
Date: Tue, 02 Sep 2003 12:49:11 +1000
Cc: cipe-l,AT,inka,DOT,de
In-reply-to: <Pine.LNX.4.21.0309020314590.24282-100000@cats.meow.at>
Organization: Draxsen Technologies
References: <Pine.LNX.4.21.0309020314590.24282-100000@cats.meow.at>

Jake Bullet wrote:

On Tue, 2 Sep 2003, Phil Scarratt wrote:
<SNIP>

Win2k(Alice) Linux(Bob) Win2k(Chris) 172.16.0.2 172.16.0.1 - 172.16.1.1 172.16.1.2

I'd like the two client machines (alice & chris) to share a private
network through the server (Bob) over CIPE.  The only way I could think of
was to give each machine its own subnet and have Bob route between them.

I tried this for ages, but I could never get the Win2k clients to route
the 172.16.0.0 network down the interface.  If I added specific routes
then it sent the packets (from Alice to Bob) but then Bob failed to
forward them.

Stephen

With the following assumptions:
- CIPE tunnel between Alice and Bob with CIPE IP addresses 172.16.0.1/2
- Bob and Chris are on the same LAN with LAN IP addresses 172.16.1.1/2
- Bob is Chris' default gateway
Adding a route to Alice for the Bob-Chris LAN (route add 172.16.1.0 mask 255.255.255.0 172.16.0.1) should allow packets to get from Alice to Chris and back.


If however, the following scenario presents itself:
- CIPE tunnel between Alice and Bob with IP addresses as marked above
- CIPE tunnel between Bob and Chris with IP addresses as marked above
then the following should work (never done this so totally untested):
- add route to Alice that points to 172.16.1.0 (route add 172.16.1.0 mask 255.255.255.0 172.16.0.1)
- add route to Chris that points to 172.16.0.0 (route add 172.16.0.0 mask 255.255.255.0 172.16.1.1)


Fil

--
Phil Scarratt
Draxsen Technologies
IT Contractor


<< | Thread Index | >> ]    [ << | Date Index | >> ]