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: Fri, 3 Apr 2015 20:38:06 +0200 [thread overview]
Message-ID: <20150403183804.GB773@omega> (raw)
In-Reply-To: <20150403182744.GA8360@bogon.m.sigxcpu.org>
On Fri, Apr 03, 2015 at 08:27:44PM +0200, Guido Günther wrote:
> On Fri, Apr 03, 2015 at 04:45:02PM +0200, Alexander Aring wrote:
> > On Fri, Apr 03, 2015 at 04:36:47PM +0200, Guido Günther wrote:
> > > Hi,
> > > I'm trying to get 6lowpan to work using bluetooth-next on the above
> > > hardware[1]. I'm currently using bluetooth-next as of
> > > baf880a96859cca79208122e555e7efeabd16e4d . When I do a:
> > >
> > > iwpan dev wpan0 set pan_id 0xbeef
> > >
> > > I get:
> > >
> > > command failed: Device or resource busy (-16)
> > >
> >
> > you can set the pan_id when you interface is down only.
>
> There was an ifplugd on the pi which continued to up the device -
> damnit. Sorry for the noise. I can now ping the two devices but am
> seeing massive packet loss:
This "ifplugd" thing is a common issue, most people which using raspbian
reported similar issues.
>
> # ping6 -s 20 -I lowpan0 fe80::f836:9287:905c:a684
> PING fe80::f836:9287:905c:a684(fe80::f836:9287:905c:a684) from fe80::cb23:b779:742d:4fd2 lowpan0: 20 data bytes
> 28 bytes from fe80::f836:9287:905c:a684: icmp_seq=3 ttl=64 time=27.7 ms
> 28 bytes from fe80::f836:9287:905c:a684: icmp_seq=4 ttl=64 time=12.7 ms
> 28 bytes from fe80::f836:9287:905c:a684: icmp_seq=5 ttl=64 time=12.7 ms
> ^C
> --- fe80::f836:9287:905c:a684 ping statistics ---
> 16 packets transmitted, 3 received, 81% packet loss, time 15017ms
>
> Will need to dig into this again.
>
mhh, is this a linux to linux connection? Maybe try to activate ARET
mode, you can do that with:
iwpan dev wpan0 set max_frame_retries 3
or something differs with 3, -1 will turn off the ARET mode. Value 0
will do csma handling only. All above 0 will do retransmission tries.
You should do that on both nodes and all nodes in your network need to
support AACK handling. (Automatck ACK).
Or maybe switch channel, I am running out of ideas now. :-)
- Alex
next prev parent reply other threads:[~2015-04-03 18:38 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 [this message]
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
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=20150403183804.GB773@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 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.