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

Subject: Re: Error: got short packet from ....
From: ewheeler,AT,kaico,DOT,com
Date: Fri, 8 Mar 2002 09:56:01 +0100
In-reply-to: <20020307220315.A24531@vax.area.com>

> I was running IP tables but I get the same results with those turned
> off.  This is with cipe-snapshot-20020227 - I would try 1.5.2, but I'm
> using the 2.4.18 linux kernel.

I'm using 2.4.18 w/ cipe-1.5.2 -- no problem!  I just commented out the
lines in sock.c which tried to make linux 2.1 function calls
(get_sock_thing or some such function -- there are two instances).  It
compiles fine and works great!   

My question:  Are there *other* more important reasons (besides the short
packet problem) that I should be aware of w/ 1.5.2 on 2.4.18-rml?

--Eric

On Thu, 7 Mar 2002, Jeremy Alves wrote:

> Hi,
> I can't seemt to get any traffic to succesfully flow across cipe.
> I get a bunch of "got short packet from (the other's sides normal IP)" 
> in the log fils, and ifconfig reports errors whenever a side receives
> a packet (i.e. ping).
> 
> The machines are connected together across a wireless network and a 
> wireless access point connected to an ethernet port, and have no 
> problems talking to each other through other channels.
> 
> Any suggestions?
> 
> 
> Here's the output of dmesg:
> 
> on a machine with IP 192.168.169.34:
>     cipdb: CIPE driver vers 1.6.pre-20020227 (c) Olaf Titz 1996-2000, 100 
>channels, debug=1
>     cipdb: rtnl_lock() at ../cipe/device.c:671
>     cipdb: cipe_alloc_dev 0
>     cipdb: rtnl_unlock() at ../cipe/device.c:673
>     cipdb0: alloc
>     cipdb: read_lock(&tasklist_lock) at ../cipe/device.c:258
>     cipdb: read_unlock(&tasklist_lock) at ../cipe/device.c:267
>     cipdb0: setpar
>     lebf_lock: 1
>     cipdb0: setpar 0.0.0.0:0 1000 60000 0200 0
>     cipdb0: setkey
>     cipdb0: attach
>     cipdb0: opened
>     cipdb0: cipe_sendmsg
>     cipdb0: cipe_recvmsg
>     cipdb0: got short packet from 192.168.169.1
> 
> and on a machine with IP 192.168.169.1:
>     ...
>     cipdb0: alloc
>     cipdb: read_lock(&tasklist_lock) at ../cipe/device.c:258
>     cipdb: read_unlock(&tasklist_lock) at ../cipe/device.c:262
>     cipdb0: setpar
>     lebf_lock: 1
>     cipdb0: setpar 0.0.0.0:0 1000 60000 0200 0
>     cipdb0: setkey
>     cipdb0: attach
>     cipdb0: opened
>     cipdb0: cipe_sendmsg
>     cipdb0: cipe_recvmsg
>     cipdb0: got short packet from 192.168.169.34
> 
> The files in /etc/cipe/pk are from the example,
> (ipaddr 10.0.2.1 and ptpaddr 10.0.1.1 for one, and
>  ipaddr 10.0.1.1 and ptpaddr 10.0.2.1 for the other)
> and ip-up and ip-down are identical to the example too.
> 
> Thanks for any help.
> 
> -Jeremy
> 
> --
> 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>
> 

-- 

Eric Wheeler
Network Administrator
KAICO
20417 SW 70th Ave.
Tualatin, OR 97062
www.kaico.com
Voice: 503.692.5268





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