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

To: James Knott <james.knott,AT,rogers,DOT,com>
Subject: Re: Setting up CIPE on XP
From: Phil Scarratt <fil,AT,draxsen,DOT,com>
Date: Tue, 12 Aug 2003 13:31:43 +1000
Cc: CIPE <cipe-l,AT,inka,DOT,de>
Organization: Draxsen Technologies
References: <3F2E9BCA.9010402@rogers.com> <3F2F0B0F.8010309@draxsen.com> <3F317F12.2060102@rogers.com> <3F31B4EB.6080003@draxsen.com> <3F344E68.1030505@rogers.com> <3F34AFDE.4030009@draxsen.com> <3F384192.3080200@rogers.com>

Also, on the firewall end, you've got appropriate rules:

-allow packets in on udp port 6969 (obviously this is the case as there are cipe msgs in the logs as you included in the other email - I included this purely for completeness sake)
-allow packets IN AND OUT on the cipcbx interface. It is important to allow packets IN and OUT on the cipcb0 interface or it won't work.


Fil

James Knott wrote:
Atfer getting nowhere fast, I reinstalled the CIPE drivers.

I've configured the VPN as follows.

Local IP address 0.0.0.0 Port 6969
Peer IP Address <real host name> Port 6969
Local PTP Address 192.168.2.20
Peer PTP Address 192.168.2.10
Status Enabled
Cipher NONE
Startup Script route add 192.168.2.10 192.168.2.20

route print shows

C:\Documents and Settings\jknott>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 00 e2 8a 26 aa ...... Intel(R) PRO/100 VE Network Connection - Packe
Scheduler Miniport
0x3 ...00 20 e0 8a a6 ce ...... IBM High Rate Wireless LAN MiniPCI Combo Card
Packet Scheduler Miniport
0x4 ...08 00 58 00 00 01 ...... CIPE VPN Adapter - Packet Scheduler Miniport
0x20006 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.40 192.168.1.31 21
0.0.0.0 0.0.0.0 209.188.83.238 209.188.83.238 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.31 192.168.1.31 20
192.168.1.31 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.31 192.168.1.31 20
192.168.2.0 255.255.255.0 192.168.2.20 192.168.2.20 30
192.168.2.10 255.255.255.255 192.168.2.20 192.168.2.20 1
192.168.2.20 255.255.255.255 127.0.0.1 127.0.0.1 30
192.168.2.255 255.255.255.255 192.168.2.20 192.168.2.20 30
209.188.80.79 255.255.255.255 209.188.83.238 209.188.83.238 1
209.188.83.238 255.255.255.255 127.0.0.1 127.0.0.1 50
209.188.83.255 255.255.255.255 209.188.83.238 209.188.83.238 50
224.0.0.0 240.0.0.0 192.168.1.31 192.168.1.31 20
224.0.0.0 240.0.0.0 192.168.2.20 192.168.2.20 30
224.0.0.0 240.0.0.0 209.188.83.238 209.188.83.238 1
255.255.255.255 255.255.255.255 192.168.1.31 192.168.1.31 1
255.255.255.255 255.255.255.255 192.168.1.31 3 1
255.255.255.255 255.255.255.255 192.168.2.20 192.168.2.20 1
Default Gateway: 209.188.83.238
===========================================================================
Persistent Routes:
None



After all this, I can ping the notebook end, but not the firewall end. Also, I don't see any indication of data going through the VPN.





-- Phil Scarratt Draxsen Technologies IT Contractor/Consultant 0403 53 12 71


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