Hi, On Mon, Jul 13, 2015 at 06:18:47PM +0200, Baptiste Clenet wrote: > 2015-07-13 16:59 GMT+02:00 Baptiste Clenet <bapclenet@xxxxxxxxx>: > > Hi, > > > > Here is how I set the network: > > modprobe at86rf230 > > 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 do: > > ping6 -I lowpan0 fe80::a8af:ac69:e53e:c7f1 > > > > Nothing is sent. (I checked by sniffing the SPI pins). No errors from > > ping6 or other layers in the network stack. > > > > root@OpenWrt:/# ifconfig > > lowpan0 Link encap:UNSPEC HWaddr > > 05-38-09-06-90-E0-5E-3E-00-00-00-00-00-00-00-00 > > inet6 addr: fe80::738:906:90e0:5e3e/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1280 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > > > wpan0 Link encap:UNSPEC HWaddr > > 05-38-09-06-90-E0-5E-3E-00-00-00-00-00-00-00-00 > > UP BROADCAST RUNNING NOARP MTU:127 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:1 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:300 > > RX bytes:0 (0.0 B) TX bytes:75 (75.0 B) > > > > (TX bytes:75 (75.0 B), seems to be sent when you up lowpan0 ?) > > Yes, this is because the IPv6 neighbor discovery protocol. (We don't increment the lowpan interface stats currently), but this should be some patch later which increments the "uncompressed" part of 6LoWPAN -> simple IPv6 view, this is also what wireshark offers you on this interface. > > > > Is my settings right? What should I check to make sure the data goes > > from each layer of the network stack? > > Yes, the setting is right. I have no idea why it doesn't work on your side. That the "tx stats" of wpan interface are incremented shows me it runs the code at [0]. Before we call "drv_xmit_async" which calls the function at [1]. Maybe you can do some 'printk(KERN_INFO "foobar\n")' at [1] to see if you really call that function in driver layer, but it should. Do you see SPI traffic while probing? Because at [2] we have some id registers reads. If you don't see spi traffic and it probes successful then your sniffing setup seems wrong. If you see spi traffic then it seems to be correct and something is different in openwrt when calling ?spi_async?. Do you use now the software spi bit banging driver over gpio's? - Alex [0] http://lxr.free-electrons.com/source/net/mac802154/tx.c#L106 [1] http://lxr.free-electrons.com/source/drivers/net/ieee802154/at86rf230.c#L1027 [2] http://lxr.free-electrons.com/source/drivers/net/ieee802154/at86rf230.c#L1648 -- 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
