All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ranch <linux-hams@trinnet.net>
To: folkert <folkert@vanheusden.com>, linux-hams@vger.kernel.org
Subject: Re: icmp
Date: Fri, 1 Apr 2016 12:41:59 -0700	[thread overview]
Message-ID: <56FECF07.8020306@trinnet.net> (raw)
In-Reply-To: <20160401190724.GD25136@belle.intranet.vanheusden.com>


This is because you have your window setting per the /etc/ax25/axports 
file set to 1.   Change it to say 4 and things should work better.

Btw.. what speed are you running your LoRa network at?  A round trip 
time of 1.6 seconds is quite slow but maybe that's due to the 
serialization delays of running your network at say 300bps!

--David


On 04/01/2016 12:07 PM, folkert wrote:
> An other strange thing: I can't have 2 packets in that 2 second
> interval. E.g. a traceroute only works if I add -N 1 -w 2.
>
> On Fri, Apr 01, 2016 at 08:42:26PM +0200, folkert wrote:
>> Hi,
>>
>> This evening I succeeded in doing ICMP over AX.25 over LoRa(!)!
>>
>> root@savannah:~/data/mkiss_moteino# ping -i 5 192.168.5.1
>> PING 192.168.5.1 (192.168.5.1) 56(84) bytes of data.
>> 64 bytes from 192.168.5.1: icmp_seq=4 ttl=64 time=4524 ms
>> 64 bytes from 192.168.5.1: icmp_seq=7 ttl=64 time=1601 ms
>> 64 bytes from 192.168.5.1: icmp_seq=8 ttl=64 time=1601 ms
>> 64 bytes from 192.168.5.1: icmp_seq=9 ttl=64 time=1601 ms
>> ^C
>> --- 192.168.5.1 ping statistics ---
>> 9 packets transmitted, 4 received, 55% packet loss, time 40005ms
>> rtt min/avg/max/mdev = 1601.358/2332.248/4524.246/1265.550 ms


  reply	other threads:[~2016-04-01 19:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-01 18:42 icmp folkert
2016-04-01 19:07 ` icmp folkert
2016-04-01 19:41   ` David Ranch [this message]
2016-04-01 20:14     ` icmp folkert
2016-04-01 21:46       ` icmp David Ranch
2016-04-08 11:40         ` icmp folkert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56FECF07.8020306@trinnet.net \
    --to=linux-hams@trinnet.net \
    --cc=folkert@vanheusden.com \
    --cc=linux-hams@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.