From: "\"Thomas B. Rücker\"" <thomas@ruecker.fi>
To: "Michael C. Cambria" <mcc@fid4.com>,
Alexander Aring <alex.aring@gmail.com>
Cc: Varka Bhadram <varkabhadram@gmail.com>, linux-wpan@vger.kernel.org
Subject: Re: at86rf233 on BeagleBone Black
Date: Wed, 22 Apr 2015 09:57:10 +0300 [thread overview]
Message-ID: <55374646.90509@ruecker.fi> (raw)
In-Reply-To: <5535FAE4.60302@ruecker.fi>
On 21/04/15 10:23, "Thomas B. Rücker" wrote:
> On 04/20/2015 06:04 PM, Michael C. Cambria wrote:
>> I'll test e..g ping6 to another BBB and Pi ASAP.
> Yeah, still have to test mine too. Started working on wiring another
> openlabs module into a Minnowboard Max, but that needs writing a board
> file...
> I think I'll first just flash one of my CC2530 nodes for some simple tests.
I've tried two things:
- Receiving packets from cc2530 nodes running contiki in monitor mode.
For some reason Wireshark complains about the FCS on some packets.
- Beaglebone White and a BB Black (same image, both DTBs patched)
works just fine, #exactsteps below
Boards run a Debian Jessie image with a 4.0 Linux kernel built using
RCN's tools. From what I can tell it's pretty low on patches, so
~vanilla. DT for both am335x-bone and am335x-boneblack modified to
include a DTSI, similar to what Alex posted e.g. in
<20150414150656.GB2179@omega>. DT for BBB disabled HDMI. wpan-tools from
git.
Board1:
# iwpan dev wpan0 set pan_id 0xcafe
# ip link add link wpan0 name lowpan0 type lowpan
# ip -6 addr add 2001:db8::1/64 dev lowpan0
# ip link set wpan0 up
# ip link set lowpan0 up
Board2:
# iwpan dev wpan0 set pan_id 0xcafe
# ip link add link wpan0 name lowpan0 type lowpan
# ip -6 addr add 2001:db8::2/64 dev lowpan0
# ip link set wpan0 up
# ip link set lowpan0 up
# ping6 2001:db8::1 -c3
PING 2001:db8::1(2001:db8::1) 56 data bytes
64 bytes from 2001:db8::1: icmp_seq=1 ttl=64 time=10.8 ms
64 bytes from 2001:db8::1: icmp_seq=2 ttl=64 time=10.5 ms
64 bytes from 2001:db8::1: icmp_seq=3 ttl=64 time=10.5 ms
--- 2001:db8::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 10.526/10.633/10.814/0.175 ms
Tried SSH, works fine too.
If you are concerned with TCP performance you can modify parameters
according to Alex:
#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
Note that this will affect the whole TCP stack. There might be a way to
do it per interface.
Next: try to talk to the Contiki nodes properly
Cheers
Thomas
next prev parent reply other threads:[~2015-04-22 6:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <551EDFCA.3070905@fid4.com>
2015-04-03 19:13 ` at86rf233 on BeagleBone Black Alexander Aring
2015-04-03 19:36 ` Alexander Aring
2015-04-14 15:06 ` Alexander Aring
2015-04-16 21:08 ` Michael C. Cambria
2015-04-17 3:26 ` Varka Bhadram
2015-04-17 13:28 ` Michael C. Cambria
2015-04-17 22:19 ` Alexander Aring
2015-04-20 18:04 ` Michael C. Cambria
2015-04-20 18:24 ` Alexander Aring
2015-04-21 7:23 ` "Thomas B. Rücker"
2015-04-22 6:57 ` "Thomas B. Rücker" [this message]
2015-04-23 9:37 ` Alexander Aring
2015-04-23 13:47 ` Michael C. Cambria
2015-04-23 14:59 ` 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=55374646.90509@ruecker.fi \
--to=thomas@ruecker.fi \
--cc=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=mcc@fid4.com \
--cc=varkabhadram@gmail.com \
/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