Re: Win2k and CIPE

[Phil Scarratt <fil,AT,draxsen,DOT,com>]

Jake Bullet wrote:

> On Tue, 2 Sep 2003, Phil Scarratt wrote:
>
>
> > Jake Bullet wrote:
> >
> >
> > > > > 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?
> > >
> > >
> > > There is no firewall running on Bob for the CIPE interfaces, and the
> > > routing table is empty.
> > >
> > > Stephen
> >
> > Empty routing table?? That's gotta be why then...Bob has got no idea 
> > where to pass anything. There should at least be interface lo listed 
> > surely......I've forgotten what distro you're running on Bob....
> >
> > Bob needs to have routes to 172.16.0.2 and 172.16.1.2 (or their networks 
> > if other computers are needed to be accessed via the CIPE tunnel).
>
>
> What do I need to add?
>
> I was planning on having a whole big system of Win2k clients, all on
> different subnets.  Will I need a massive routing table to get them all
> talking to each other?
>
> Stephen

I'm a little confused here, as when cipe starts successfully on linux, 
routes are automatically added for the other end of the tunnel. In other 
words, starting cipcb0 (whose ip is 172.16.0.1 and peer is 172.16.0.2) 
should add at least the following to the route table:

172.16.0.2  *  255.255.255.255 U 0 0 0 cipcb0

If these are not appearing then something strange is going on - are you 
sure the tunnel is starting correctly??

Fil