For NT routing, set 192.168.X.100 as
default gw. no weird routes other than that for the NT side.
On 192.168.0.100, add:
route add -net 192.168.1.0 netmask 255.255.255.0 gw 10.10.10.1
On 192.168.1.100, add:
route add -net 192.168.0.0 netmask 255.255.255.0 gw 10.10.10.10
Also tailor your firewall rules to allow the routing if necessicary (might
start w/ flushed rules for testing: ipchains -F ; iptables -F ; iptables
-t nat -F)
Then NT1 & NT2 should ping!
On Mon, 27 Aug 2001 Gert.Vandelaer,AT,medisearch-int,DOT,com wrote:
> Hy all,
> i've given up on cipe on win32,
> couldn't explain the "CRC checksum failed" ... "nokey" wouldn't even
> initiate connection ... and so much more.
> CIPE between 2 Linux boxes runs great,
> now I need to get routing going.
> The Linux boxes are in front of a MS Network,
> all Mickeysoft data should go over the CIPE link ...
> Should I try to build a bridge consisiting of LAN-IP and CIPE-IP (protocol
> 4, btw).
> Or is there some simple routing trick I could use ...
> I read some info about CIPE + Bridge failing when the network load would
> get really high,
> I also read about someone giving up on CIPE + Bridge, and got a VTUN +
> Bridge going.
> I'd like to keep on using CIPE if possible,
> WinNT 1(192.168.0.1)
> Linux 1 (192.168.0.100) --- 10.10.10.10
> CIPE (OK)
> Linux 2 (192.168.1.100) ---- 10.10.10.1
> Win NT 2 (192.168.1.1)
> I'd like to ping the "Win NT1" from "Win NT2", and vice versa ...
> right now I can ping only between the 2 linuxes.
> Message sent by the cipe-l,AT,inka,DOT,de mailing list.
> Unsubscribe: mail majordomo,AT,inka,DOT,de, "unsubscribe cipe-l" in body
> Other commands available with "help" in body to the same address.
> CIPE info and list archive: