RE: Linux-Bluetoothnext: Ping6 execution for virtual Phy : System freezes

* RE: Linux-Bluetoothnext: Ping6 execution for virtual Phy : System freezes
@ 2015-10-01 10:15 Anoop Kant
  2015-10-01 10:28 ` Alexander Aring
  0 siblings, 1 reply; 6+ messages in thread
From: Anoop Kant @ 2015-10-01 10:15 UTC (permalink / raw)
  To: Alexander Aring; +Cc: linux-wpan, kantanoop

Thanks Alex for the information!!

I executed the steps as provided in previous mail. My system gets freeze after enabling lowpan0 interface.
i.e. after executing command  // ip link set lowpan0 up //

Every time, I have to reboot my system to get it up back.

From Syslog, I see below : Am I missing something ? Any clue on probable reason of this issue ?

Oct  1 14:57:49 yocto-HP-ProBook-4420s AptDaemon: INFO: Quitting due to inactivity Oct  1 14:57:49 yocto-HP-ProBook-4420s AptDaemon: INFO: Quitting was requested Oct  1 15:08:36 yocto-HP-ProBook-4420s kernel: [ 1137.587417] ieee802154fakelb ieee802154fakelb: added ieee802154 hardware
Oct  1 15:08:36 yocto-HP-ProBook-4420s NetworkManager[1373]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/platform/ieee802154fakelb/ieee802154/phy1/net/wpan1, iface: wpan1)
Oct  1 15:08:36 yocto-HP-ProBook-4420s NetworkManager[1373]:    SCPlugin-Ifupdown: device added (path: /sys/devices/platform/ieee802154fakelb/ieee802154/phy1/net/wpan1, iface: wpan1): no ifupdown configuration found.
Oct  1 15:08:36 yocto-HP-ProBook-4420s NetworkManager[1373]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/platform/ieee802154fakelb/ieee802154/phy0/net/wpan0, iface: wpan0)

Oct  1 15:08:36 yocto-HP-ProBook-4420s NetworkManager[1373]:    SCPlugin-Ifupdown: device added (path: /sys/devices/platform/ieee802154fakelb/ieee802154/phy0/net/wpan0, iface: wpan0): no ifupdown configuration found. =====> Erros in logs

Oct  1 15:10:06 yocto-HP-ProBook-4420s NetworkManager[1373]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/lowpan0, iface: lowpan0)
Oct  1 15:10:06 yocto-HP-ProBook-4420s NetworkManager[1373]:    SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/lowpan0, iface: lowpan0): no ifupdown configuration found.
Oct  1 15:12:21 yocto-HP-ProBook-4420s kernel: imklog 5.8.6, log source = /proc/kmsg started.

I appreciate for all your help to enable me to reach till this point. Thanks a lot!!

Rgds
Anoop
-----Original Message-----
From: Alexander Aring [mailto:alex.aring@gmail.com]
Sent: 30 September 2015 23:25
To: Anoop Kant
Cc: linux-wpan@vger.kernel.org; kantanoop@yahoo.com
Subject: Re: Linux-Wpan-Next: Regarding usage of fakelb driver

On Wed, Sep 30, 2015 at 11:25:23AM +0000, Anoop Kant wrote:
> Dear Alex,
>
> Greetings!!
>
> Thanks for detailed information!! I was able to bring up bluetooth_next/ fakelb/iwpan and wpan ping tool in linux machine with the information provided.
>
> Further, I am trying to come up with virtual network (for eample pinging of IPV6 packets between two virtual nodes- packets going thorugh all the layes down to Phy layer and coming back to top layer) using fakelb on LInux machine itself.
>
> I have seen that for earlier zigbee-linux ,we had detailed steps to demonstrate the functionality of the stack without real hardware, as given at below path :
>
> http://linux-zigbee.sourceforge.net/cgi-bin/trac.cgi/wiki/GettingStart
> ed-0.2
>

Don't use this information. It's outdated and it's not easy to delete sourceforge projects. :-)

> Do we have something similar for the latest bluetooth-linux kernel which can help me to simulate WPAN network and verify messaging in LInux machine using fakelb / Or any information available if it has been tried by someone earlier?
>
> Currently, I am analysing same, so just thought to check if some information on this already exist.
>
> Note : So far, I am following the commands http://wpan.cakelab.org/#_how_to_8217_s and reached till this point. Now, further I want to simulate some network activity within Linux machine.
>

If your setup runs fine with bluetooth_next, wpan-tools and fakelb is loaded.

Then iwpan dev should show two interfaces.

On each of them you need to set the pan_id e.g. "0xbeef", but not the default one and create one lowpan interface on it. e.g.:

for pan_id:

iwpan dev wpan0 set pan_id 0xbeef
iwpan dev wpan1 set pan_id 0xbeef

for lowpan interface:

ip link add link wpan0 name lowpan0 type lowpan ip link add link wpan1 name lowpan1 type lowpan

interface up:

ip link set wpan0 up
ip link set wpan1 up

ip link set lowpan0 up
ip link set lowpan1 up

getting default link-local address:

ip a

Then there should something like:

    inet6 fe80::b02f:76cc:1923:df59/64 scope link
           valid_lft forever preferred_lft forever

for the lowpan0 interface, the address differs because it's a random generated one.

run ping6

ping6 -I lowpan1 fe80::b02f:76cc:1923:df59

I suppose here your interfaces are named "wpan0" and "wpan1".
The "fe80::b02f:76cc:1923:df59" is the address of lowpan0 and this is why we use the "lowpan1" interface by calling: "ping6 -I lowpan1".

This should be enough to run some ping between the two virtual phy's.

- Alex
L&T Technology Services Ltd

www.LntTechservices.com<http://www.lnttechservices.com/>

This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.

^ permalink raw reply	[flat|nested] 6+ messages in thread