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

Subject: cipe 1.52free9 and kernel 2.4.18
From: "Mark Smith" <mark.smith,AT,avcosystems,DOT,co,DOT,uk>
Date: Wed, 14 Aug 2002 11:21:46 +0200

I've got an interesting problem...  I can establish a tunnel using pkcipe
between two linux hosts, both running the exact same kernel and cipe module
without problem.

However, if I attempt to establish the very same tunnel using cipe alone, it
doesn't connect.

One machine has static real IP and is directly connected (through a cable
modem) and is serving as host with the following config:

--- snip ---
# the peer's IP address
ptpaddr         0.0.0.0
# our CIPE device's IP address
ipaddr          192.168.0.1
# my UDP address. Note: if you set port 0 here, the system will pick
# one and tell it to you via the ip-up script. Same holds for IP 0.0.0.0.
me              <ip1>:11111
# ...and the UDP address we connect to. Of course no wildcards here.
peer            0.0.0.0
# The static key. Keep this file secret!
# The key is 128 bits in hexadecimal notation.
key             <secret>
--- end ---

The other machine has a static private address whose outbound traffic is
rewritten to a real IP using a NAT firewall.  It's config:

--- snip ---
# the peer's IP address
ptpaddr         192.168.0.1
# our CIPE device's IP address
ipaddr          10.253.0.12
# my UDP address. Note: if you set port 0 here, the system will pick
# one and tell it to you via the ip-up script. Same holds for IP 0.0.0.0.
me              <ip2>:11111
# ...and the UDP address we connect to. Of course no wildcards here.
peer            <ip1>:11111
# The static key. Keep this file secret!
# The key is 128 bits in hexadecimal notation.
key             <secret>
# keepalive (and wakeup)
ping            10
dynip
--- end ---

Starting the server end just waits, but logs the following in
/var/log/messages:

Aug 14 10:59:44 rigel ciped-2.4.18-686[2679]: CIPE daemon vers 1.5.2 (c)
Olaf Titz 1996-2000
Aug 14 10:59:44 rigel ciped-2.4.18-686[2679]: sendctl: Invalid argument

and in /var/log/debug:

Aug 14 10:59:42 rigel kernel: cipcb: read_lock(&tasklist_lock) at
../cipe/device.c:216
Aug 14 10:59:42 rigel kernel: cipcb: read_unlock(&tasklist_lock) at
../cipe/device.c:221
Aug 14 10:59:44 rigel kernel: cipcb: read_lock(&tasklist_lock) at
../cipe/device.c:216
Aug 14 10:59:44 rigel kernel: cipcb: read_unlock(&tasklist_lock) at
../cipe/device.c:221

The client logs:

Aug 14 10:00:33 starbug ciped-2.4.18-686[5783]: CIPE daemon vers 1.5.2 (c)
Olaf Titz 1996-2000
Aug 14 10:00:33 starbug ciped-2.4.18-686[5783]: opendev: bind

The server is still running at this point, and hasn't logged anything new.
The module is inserted correctly on both, and on the server, cipcb0 reports:

cipcb0    Link encap:IPIP Tunnel  HWaddr
          inet addr:192.168.0.1  P-t-P:0.0.0.0  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP  MTU:1442  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

The interface doesn't exist on the client.  Anyone got any clues on this?

--
Mark Smith - Avco Systems Ltd
email: mark.smith,AT,avcosystems,DOT,co,DOT,uk
Tel: +44 (0)1784 430996 Fax: +44 (0)1784 431078





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