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

To: Phil Scarratt <fil,AT,draxsen,DOT,com>
Subject: Re: Win2k and CIPE
From: Jake Bullet <jbullet,AT,cats,DOT,meow,DOT,at>
Date: Tue, 2 Sep 2003 03:22:05 +0100 (BST)
Cc: cipe-l,AT,inka,DOT,de
In-reply-to: <3F53FBAA.4010402@draxsen.com>

On Tue, 2 Sep 2003, Phil Scarratt wrote:

> Jake Bullet wrote:
> 
> > On Mon, 1 Sep 2003, David A. Osborn wrote:
> > 
> <SNIP>
> > 
> > p.p.s. I've been trying to get the Linux box at the other end of mine to
> > route packets, and to get the Windows2k box to route packets for the
> > subnet down the link in the first place.  If you find the solution, please
> > post it :-)
> > 
> What exactly do you mean by this. If the Linux box or WinBox are default 
> gateways for their respective networks then it should happen 
> automatically. You will need a route to the remote NETWORK (not just the 
>   remote machine) which needs adding manually, in either the Linux or 
> Win case.
> 

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


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