Re: Win2k and CIPE

Jake Bullet wrote:
>>
>>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)
>>
> 
> 
> That's not quiet it, as Chris is also running CIPE to Bob.  I did try this
> but the Server (Bob) didn't seem to be routing the packets.
> I did turn on IP forwarding.  Running TCP dump on both CIPE interfaces
> showed Alice sending the ECHO REQUEST to Bob, and that's where it stopped.
> 
> As mentioned lots of these were showing up in the syslog:
> 
> May  6 01:21:37 bob kernel: cipcb2: got bogus length=9
> May  6 01:21:37 bob kernel: cipcb1: got bogus length=9
> 
> Stephen
> 

Is there a firewall running on Bob? What's the routing table for Bob 
look like?

Fil


--
Message sent by the [email protected] mailing list.
Unsubscribe: mail [email protected], "unsubscribe cipe-l" in body
Other commands available with "help" in body to the same address.
CIPE info and list archive: <URL:http://sites.inka.de/~bigred/devel/cipe.html>