I don't know how it got solved, but read the mailing list archives for "short
packet". There was something about that around cipe v1.5.x, but I'm not
terribly aware of the details or the cause/s.
It might be the static key (make sure that the keys match and are 32
hexadecimal digits in length). Also, you don't say whether the tunnel works
at all or not. You might also attempt to use a different version of CIPE (say
v1.4.5) to see if anything changed in the protocol between versions that I
On Monday 17 June 2002 07:37 am, Bart Boelaert wrote:
> Does anyone know how to solve the problem as described below?
> I'm running CIPE 1.5.3 on a RH system with kernel 2.2.19-6.2.12. I compiled
> CIPE and removed the cipcb.o kernel module from
> /lib/modules/2.2.19-6.2.12/net, so that the correct kernel module which
> CIPE installed in /lib/modules/2.2.19-6.2.12/misc is used. On the other end
> I'm using CIPE for Win32 2.0-pre14 on a W2K Server system. The W2K system
> has a dynamic IP address. The CIPE config file on the Linux system is as
> follows :
> ipaddr 192.168.192.254
> ptpaddr 192.168.192.2
> me 100.100.100.100:16000
> peer 0.0.0.0:16000
> maxerr -1
> key 270bda82c3a4447d776f976c41a2ba50
> When the W2K system wants to establish a CIPE tunnel with the Linux system,
> I get the following syslog message many times on the Linux system :
> got short packet from <remote peer ip>
> I also get a lot of RX error packets when I check the CIPE interface
> statistics via ifconfig.
> Could somebody help me out with this nasty problem?
> Thanks in advance,
> Bart Boelaert.
> This e-mail has been scanned when leaving our systems and is certified
> Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.371 / Virus Database: 206 - Release Date: 13/06/2002