Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: "Guido Günther" <agx@sigxcpu.org>
Cc: linux-wpan@vger.kernel.org
Subject: Re: 6lowpan on a RPi using at86rf233
Date: Thu, 9 Apr 2015 12:21:29 +0200	[thread overview]
Message-ID: <20150409102126.GE1261@omega> (raw)
In-Reply-To: <20150409090652.GA5018@bogon.m.sigxcpu.org>

Hi,

On Thu, Apr 09, 2015 at 11:06:52AM +0200, Guido Günther wrote:
> 
> SSHing between the machines is ok. Nice.

For tune-up tcp connection I set also set tcp window size;

#reduce tcp receive buf, will improve tcp connections
echo "127 512 1024" > /proc/sys/net/ipv4/tcp_rmem
echo "127 512 1024" > /proc/sys/net/ipv4/tcp_wmem

This will do this for all tcp connection. You can also try to set MSS
with ip6tables.

to have much fragments isn't good on a 6LoWPAN connection. Upper layers
like CoAP, etc. will handle this. Also a general TCP connection isn't
good, because the ACK handling stuff. Maybe want to try out "mosh with
ipv6 support [1]" - currently only available on dev branch.


High fragments and fq_codel qdisc will also occur trouble, because the
skb's are too long inside the queue and fq_codel will drop them then.
This occurs on my setup at payload of ~2000 bytes, but we should never
reach such payload, also 1024 is too high. If you use with contiki I
don't think that contiki implement ipv6 fragmentation, so you can set
the highest payload to 1280. Does somebody knows if contiki supports
ipv6 fragmentation?

- Alex

[1] https://github.com/keithw/mosh

  reply	other threads:[~2015-04-09 10:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150403143647.GA6266@bogon.m.sigxcpu.org>
2015-04-03 14:45 ` 6lowpan on a RPi using at86rf233 Alexander Aring
2015-04-03 18:27   ` Guido Günther
2015-04-03 18:38     ` Alexander Aring
2015-04-07 11:49       ` Guido Günther
2015-04-07 19:07         ` Alexander Aring
2015-04-09  9:06           ` Guido Günther
2015-04-09 10:21             ` Alexander Aring [this message]
2015-04-03 18:49     ` Alexander Aring

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=20150409102126.GE1261@omega \
    --to=alex.aring@gmail.com \
    --cc=agx@sigxcpu.org \
    --cc=linux-wpan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox