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:
# 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.
Thaks a lot for the hint!
Cheers,
-- Guido
--
To unsubscribe from this list: send the line "unsubscribe linux-wpan" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
