2015-06-29 11:13 GMT+02:00 Varka Bhadram <varkabhadram@xxxxxxxxx>:
> On 06/29/2015 01:39 PM, Alexander Aring wrote:
>>>
>>> Alexander, which version of Linux bluetooth-next tree is based on?
>>
>> 4.1.0-rc4-01278-gfbb12f9-dirty
>>
>> this is currently in my development branch. Alternative you can check
>> the Makefile of linux-kernel [0].
>>
>> VERSION = 4
>> PATCHLEVEL = 1
>> SUBLEVEL = 0
>> EXTRAVERSION = -rc4
>> NAME = Hurr durr I'ma sheep
>>
>>
>>
>> I really have no idea why you don't have a wpan interface by default.
>
>
> May be the wpan interface is down :-).
>
> can you please check with: *ifconfig -a*
Varka, you were right:
root@OpenWrt:/# ifconfig -a
br-lan Link encap:Ethernet HWaddr A6:3E:F6:19:6C:F7
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fd35:d27a:3a36::1/60 Scope:Global
inet6 addr: fe80::a43e:f6ff:fe19:6cf7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:598 (598.0 B) TX bytes:1230 (1.2 KiB)
eth0 Link encap:Ethernet HWaddr 2E:81:C8:13:EF:44
inet6 addr: fe80::2c81:c8ff:fe13:ef44/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:19 errors:0 dropped:0 overruns:0 frame:0
TX packets:46 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1216 (1.1 KiB) TX bytes:7418 (7.2 KiB)
Interrupt:5
eth0.1 Link encap:Ethernet HWaddr 2E:81:C8:13:EF:44
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:19 errors:0 dropped:0 overruns:0 frame:0
TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:874 (874.0 B) TX bytes:2319 (2.2 KiB)
eth0.2 Link encap:Ethernet HWaddr A6:3E:F6:19:6C:F8
inet6 addr: fe80::a43e:f6ff:fe19:6cf8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:3257 (3.1 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:48 errors:0 dropped:0 overruns:0 frame:0
TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3936 (3.8 KiB) TX bytes:3936 (3.8 KiB)
wpan0 Link encap:UNSPEC HWaddr
0E-49-D3-CD-5E-7D-3E-8C-00-00-00-00-00-00-00-00
BROADCAST NOARP MTU:127 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:300
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
'ip link set wpan0 up' sets it up.
>
>> You can delete interfaces from nl802154, but then openwrt need to speak
>> to this netlink interface and I don't believe that it does that. :-)
>
>
> Speaking to the netlink interface in OpenWRT is same as in case of bare
> Linux kernel compiled for specific target. There is no difference.
> So we can use the wpan-tools [1] to speak to the netlink interface.
>
> [1]:
> http://git.openwrt.org/?p=openwrt.git;a=blob;f=package/network/utils/wpan-tools/Makefile;h=87a5fb1461121407f685e960b64315661aacc9bf;hb=HEAD
>
> --
> Varka Bhadram.
>
I'm going to search deeper why ping6 doesn't want to communicate with SPI.
--
Baptiste
--
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
