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

Subject: Re: CIPE Linux <-> Win2K
From: Kyle Winters <kyle,AT,ksteam,DOT,com,DOT,au>
Date: Tue, 15 May 2001 01:08:45 +0200
In-reply-to: <5.1.0.14.0.20010515011904.00a5d2f0@cipe-gw.air.net.au>

Jason,
It looks to me as though your PTP addresses are a little mixed up.  From my 
understanding (and this is how I have set up all my connections), you need 
to set the VPN up as a totally different network.  So your PTP IP on one 
end will be 192.168.200.1 and your PTP IP on the other end will be 
192.168.200.2.  Both of these have a netmask of 255.255.255.0
The 192.168 addresses being blocked from the internet won't matter because 
the 192.168 addresses are encapsulated in the "real" IP packet which has an 
address of 203.xxx.xxx.xxx.
Good luck,

Kyle Winters
KS Team Computers

At 01:23 AM 15/05/01 +1000, you wrote:
>Hi,
>
>I am still struggling to get CIPE 1.4.6 on my LRP box talking to a pals 
>Win2K CIPE2beta9.
>
>My internal subnet 192.168.1.x is meant to connect to his subnet of 
>192.168.2.x over the CIPE interface, with PTP links 192.168.1.253 and 
>192.168.2.253 respectively.  The interface seems to come up but in my logs 
>when I ping him I get:
>
>May 14 14:16:20 myrouter kernel: cipcb1: cipe_recvmsg
>May 14 14:16:20 myrouter ciped-cb[1196]: kxchg: send: Connection refused
>May 14 14:16:20 myrouter ciped-cb[1196]: kxchg: recv: Connection refused
>
>And he can't ping me.
>
>Any ideas?  Actually, a thought has occured, the default LRP firewall 
>script sets 192.168.x.x incoming addresses as illegal from the outside 
>world.  I wonder if this is blocking CIPE communications...  Grrrr.
>
>Ta,
>jASON
>
>
>--
>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: 
><URL:http://sites.inka.de/~bigred/devel/cipe.html>





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