From: Alexander Aring <alex.aring@gmail.com>
To: Baptiste Clenet <bapclenet@gmail.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: ping6 doesn't use at86rf230 driver
Date: Thu, 25 Jun 2015 19:30:32 +0200 [thread overview]
Message-ID: <20150625173032.GC3653@omega> (raw)
In-Reply-To: <20150625171557.GB3653@omega>
On Thu, Jun 25, 2015 at 07:15:57PM +0200, Alexander Aring wrote:
> On Thu, Jun 25, 2015 at 06:52:35PM +0200, Baptiste Clenet wrote:
> > Hi,
> >
> > Following is how I configure the network:
> > modprobe at86rf230
> > iwpan phy wpan-phy0 interface add wpan0 type node
> > iwpan dev wpan0 set pan_id 0xbeef
> > ip link set wpan0 up
> > ip link add link wpan0 name lowpan0 type lowpan
> > ip link set lowpan0 up
> >
> > Then I try to ping6 my second board with:
> > ping6 -I lowpan0 fe80::a8af:ac69:e53e:c7f1
> >
> > I'm observing no changes over the SPI between my board and the
> > at86rf230. But if I change the channel with:
> > iwpan phy wpan-phy0 set channel 0 0
>
> this change should not be possible with the at86rf230.
>
ah, with the at86rf212 it's possible to set page/channel to 0. But I
have still no idea why you having this issues right now.
Everything which you did seems to be correct. Which kernel version do
you use and why you do a:
iwpan phy wpan-phy0 interface add wpan0 type node
there should be a wpan0 node interface by default.
- Alex
next prev parent reply other threads:[~2015-06-25 17:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 16:52 ping6 doesn't use at86rf230 driver Baptiste Clenet
2015-06-25 17:15 ` Alexander Aring
2015-06-25 17:30 ` Alexander Aring [this message]
2015-06-26 7:17 ` Baptiste Clenet
2015-06-26 7:20 ` Baptiste Clenet
2015-06-26 8:03 ` Alexander Aring
2015-06-26 8:24 ` Baptiste Clenet
2015-06-29 7:01 ` Baptiste Clenet
2015-06-29 8:09 ` Alexander Aring
2015-06-29 9:13 ` Varka Bhadram
2015-06-29 9:44 ` Baptiste Clenet
2015-06-29 11:44 ` Baptiste Clenet
2015-06-29 22:09 ` Alexander Aring
2015-06-30 9:12 ` Baptiste Clenet
2015-07-01 8:21 ` Alexander Aring
2015-07-01 9:22 ` Baptiste Clenet
2015-07-01 9:45 ` Baptiste Clenet
2015-07-01 11:59 ` Baptiste Clenet
2015-07-01 15:16 ` Alexander Aring
2015-07-02 15:02 ` Baptiste Clenet
2015-07-02 15:15 ` Baptiste Clenet
2015-07-02 16:12 ` Alexander Aring
2015-07-03 13:24 ` Baptiste Clenet
2015-07-03 13:37 ` Baptiste Clenet
2015-07-03 15:01 ` Baptiste Clenet
2015-07-03 15:47 ` Alexander Aring
2015-07-03 16:33 ` Baptiste Clenet
2015-07-03 17:37 ` Alexander Aring
2015-07-03 22:13 ` Baptiste Clenet
2015-07-04 15:36 ` Alexander Aring
2015-07-05 10:38 ` Baptiste Clenet
2015-07-08 8:35 ` Baptiste Clenet
2015-07-09 11:19 ` Baptiste Clenet
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=20150625173032.GC3653@omega \
--to=alex.aring@gmail.com \
--cc=bapclenet@gmail.com \
--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