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

Subject: RE: Mixed Linux and Windows
From: Frank De Meulenaere <fdm,AT,cadservice,DOT,be>
Date: Wed, 21 Nov 2001 23:27:46 +0100

A dummy subnet? Hmmm... where does that fit in?

Say my Windows box has a LAN-side ip of 192.168.158.1, and a dynamically
assigned Internet-side ip.
The Linux box is 1.2.3.4 on the Internet side (port 23456/udp), and
192.168.0.1 on the LAN side.

These routes are added by CIPE on the Linux-side:

Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
192.168.158.1   *               255.255.255.255 UH    0      0        0
cipcb1
192.168.158.0   192.168.158.1   255.255.255.0   UG    0      0        0
cipcb1

Do I need to add routes on the Windows side?

TIA,

Frank

-----Original Message-----
From: Tony Langdon [mailto:tlangdon,AT,atctraining,DOT,com,DOT,au
Sent: woensdag 21 november 2001 22:51
To: 'Frank De Meulenaere'
Subject: RE: Mixed Linux and Windows

> Is it possible to mix Linux and Windows CIPE-clients?
> 
> I want to have a central Linux-server running CIPE, and 
> connect to it from
> multiple clients, some running Linux, others Windows 2000.
> 
> I did not find a clear answer in the archives, but if I understood
> correctly, the 2 CIPE-implementations use different network connection
> types. Linux uses point-to-point, while Windows is an 
> ethernet connection.
> Are they mutually exclusive?
> 
> Has anyone succeeded in this kind of setup?

I have a WIndows CIPE machine talking to a Linux one.  They will
interoperate, as long as you use a dummy subnet for the tunneled link
itself.  I see no reason why your arrangement won't work.  However, each
"client" will need to talk to a different server port, and you'll need a
separate CIPE interface for each connection.

Only problems I've have had have been related to bugs in Windows 2000
and/or
the Windows CIPE implementation.

Attachment: bin00002.bin
Description: "smime.p7s"


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