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

Subject: Re: ping fails sometimes
From: Wolfgang Ailec <W.Ailec,AT,awe,DOT,at>
Date: Wed, 5 Jun 2002 13:57:09 +0200
In-reply-to: <8F8B9BEB9CFDC24FB5E4DA99EBAA607A011E0CA9@EXBOURGOGNE.corp.khm.be>

Hallo Peter,
this is a very strange behaviour. The only things I can believe
that they are responsible for your problem are:

1. Maybe the small-packets-bug in version 1.4.6 is the problem
    Try pinging with different packet sizes (e.g. 200 bytes)
2. Because you are using the same subnet on the tunnel and on interface
    eth1 there may be a routing problem
3. If you are using the key you write down in your previous e-mails
    (aaaa..) you should generate a real one (ps -auxwww|md5sum) or
    try testing without key by using the nokey option instead of
    key xxxxxxx

>Now and then I log this:
>cipcb0: cipe_recvmesg
>cipcb0: cipe_sendmsg
>cipcb0: setkey

These log-messages appear because you load the kernel module without
cipe_debug=0 as parameter, thats normal.

Hope one of these will help!

Wolfgang

At 01:33 PM 6/5/02 +0200, Berghmans, Peter wrote:
>Wolfgang, all
>
>Here is a more detailled description of my problem: ping works now and
>then.
>
>First my setup:
>
>Cipe 1.4.6 (disabled dyndev) runs on a floppy (both ends, based on
>floppyfw), based on 2.2.20. Module is ok, cipcb0 comes up (thanks you
>Wolfgang).
>
>configurations:
>
>PC1
>ptpaddr 10.0.0.1
>ipaddr 172.16.0.1
>me 0.0.0.0:8016
>peer 12.0.0.44:8017
>key aaaaaaa
>cttl 64
>maxerr -1
>
>PC2
>ptpaddr 172.16.0.1
>ipaddr 10.0.0.1
>me 0.0.0.0:8017
>peer 12.0.0.43:8016
>key aaaaaaa
>cttl 64
>maxerr -1
>
>some routing-information:
>PC1
>Destination      GW    iface
>10.0.0.1/32          *    cipcb0
>172.16.0.0/16     *    eth1
>12.0.0.0               *    eth0
>
>PC2
>Destination      GW    iface
>172.16.0.1/32     *    cipcb0
>10.0.0.0/8            *    eth1
>12.0.0.0               *    eth0
>
>results of ping 172.16.0.1 (PC2) same as 10.0.0.1 (PC1)
>ping works 4 or 5 times, then lots of packets get lost. After a while
>ping restarts for 4 or 5 times, and so on.
>
>Now and then I log this:
>cipcb0: cipe_recvmesg
>cipcb0: cipe_sendmsg
>cipcb0: setkey
>
>There is no firewall and no masquerading (eventhough I first tried with
>my masquerading rules active, same result)
>
>Whats the solution to this (strange) behaviour?
>
>
>Peter





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