Re: Linux-Wpan-Next: Regarding usage of fakelb driver

Re: Linux-Wpan-Next: Regarding usage of fakelb driver

[Alexander Aring]

Hi,

On Tue, Sep 29, 2015 at 09:01:16AM +0000, Anoop Kant wrote:
> Dear Alex,
> 
> Greetings!!
> 
> I am trying to use a simulated network environment using fakelb. I have built image using latest Linux-Wpan-Next files. The image is built and running in x86_64 machine.
> 
> Now, could you guide me where can I get help on how to use this fake drivers.
> 
> I tried to follow the instructions given at https://code.google.com/p/linux-wsn/wiki/Mainline
> But, I am not able to register loopback driver as I am getting issue. I am getting module instering error while trying below command.
> 
> # insmod fakelb.ko
> 
> Could you please guide me where can I refer for steps to follow for this ?
> 

The new website is [0].

Please don't use linux-wpan-next. Our current working repository is
bluetooth-next [1]. If you like to send patches your patches need to
base on bluetooth-next. See [2].

For testing fakelb I would advice you to create some qemu/virtualbox
machine with a recent bluetooth-next kernel.

Then if fakelb driver is built as module you need to call "modprobe
fakelb", if everything is okay then you will see two new wpan phy's by
calling:

iwpan phy

by default a wpan phy will create one node interface, so you will have
two wpan interfaces "wpan0/wpan1" by default. You can check this by calling:

iwpan dev

To setup the interfaces/phy and 6lopwan (if you want that), you can call
"iwpan" for all possible settings and follow the instructions at [3].

- Alex

[0] http://wpan.cakelab.org/
[1] http://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git
[2] http://wpan.cakelab.org/#_developing
[3] http://wpan.cakelab.org/#_how_to_8217_s

RE: Linux-Wpan-Next: Regarding usage of fakelb driver

[Anoop Kant]

Dear Alex,

Thanks for quick response!!

I will build image using bluetooth-next git and try.

I believe iwpan and wpan-ping (wpan tools) will already be present in the bluetooth-next-kernel built. Is that correct understanding ?

Regards,
Anoop
________________________________________
From: Alexander Aring [alex.aring@gmail.com]
Sent: Tuesday, September 29, 2015 4:12 PM
To: Anoop Kant
Cc: linux-wpan@vger.kernel.org
Subject: Re: Linux-Wpan-Next: Regarding usage of fakelb driver

Hi,

On Tue, Sep 29, 2015 at 09:01:16AM +0000, Anoop Kant wrote:
> Dear Alex,
>
> Greetings!!
>
> I am trying to use a simulated network environment using fakelb. I have built image using latest Linux-Wpan-Next files. The image is built and running in x86_64 machine.
>
> Now, could you guide me where can I get help on how to use this fake drivers.
>
> I tried to follow the instructions given at https://code.google.com/p/linux-wsn/wiki/Mainline
> But, I am not able to register loopback driver as I am getting issue. I am getting module instering error while trying below command.
>
> # insmod fakelb.ko
>
> Could you please guide me where can I refer for steps to follow for this ?
>

The new website is [0].

Please don't use linux-wpan-next. Our current working repository is
bluetooth-next [1]. If you like to send patches your patches need to
base on bluetooth-next. See [2].

For testing fakelb I would advice you to create some qemu/virtualbox
machine with a recent bluetooth-next kernel.

Then if fakelb driver is built as module you need to call "modprobe
fakelb", if everything is okay then you will see two new wpan phy's by
calling:

iwpan phy

by default a wpan phy will create one node interface, so you will have
two wpan interfaces "wpan0/wpan1" by default. You can check this by calling:

iwpan dev

To setup the interfaces/phy and 6lopwan (if you want that), you can call
"iwpan" for all possible settings and follow the instructions at [3].

- Alex

[0] http://wpan.cakelab.org/
[1] http://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git
[2] http://wpan.cakelab.org/#_developing
[3] http://wpan.cakelab.org/#_how_to_8217_s
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.

Re: Linux-Wpan-Next: Regarding usage of fakelb driver

[Alexander Aring]

On Tue, Sep 29, 2015 at 10:59:52AM +0000, Anoop Kant wrote:
> Dear Alex,
> 
> Thanks for quick response!!
> 
> I will build image using bluetooth-next git and try.
> 
> I believe iwpan and wpan-ping (wpan tools) will already be present in the bluetooth-next-kernel built. Is that correct understanding ?

No, this is part of userspace you need to build it by yourself.

Newest release is 0.5 [0].

It's using autotools as buildsystem so a normal:

./confgure
make
(as root) make install

See [1].

should be enough, we have one dependency to libnl3. See [2], this should
be provided from your distribution which you install. (It's a common
library for networking utilities).

- Alex

[0] http://wpan.cakelab.org/releases/
[1] http://www.gnu.org/software/automake/manual/html_node/Basic-Installation.html#Basic-Installation
[2] http://www.infradead.org/~tgr/libnl (currently the site is down)

RE: Linux-Wpan-Next: Regarding usage of fakelb driver

[Anoop Kant]

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/GettingStarted-0.2

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.

Regards,
Anoop



________________________________________
From: linux-wpan-owner@vger.kernel.org [linux-wpan-owner@vger.kernel.org] on behalf of Alexander Aring [alex.aring@gmail.com]
Sent: Tuesday, September 29, 2015 4:58 PM
To: Anoop Kant
Cc: Vikas Warad; Madhu Chinthakindi; kantanoop@yahoo.com; linux-wpan@vger.kernel.org
Subject: Re: Linux-Wpan-Next: Regarding usage of fakelb driver

On Tue, Sep 29, 2015 at 10:59:52AM +0000, Anoop Kant wrote:
> Dear Alex,
>
> Thanks for quick response!!
>
> I will build image using bluetooth-next git and try.
>
> I believe iwpan and wpan-ping (wpan tools) will already be present in the bluetooth-next-kernel built. Is that correct understanding ?

No, this is part of userspace you need to build it by yourself.

Newest release is 0.5 [0].

It's using autotools as buildsystem so a normal:

./confgure
make
(as root) make install

See [1].

should be enough, we have one dependency to libnl3. See [2], this should
be provided from your distribution which you install. (It's a common
library for networking utilities).

- Alex

[0] http://wpan.cakelab.org/releases/
[1] http://www.gnu.org/software/automake/manual/html_node/Basic-Installation.html#Basic-Installation
[2] http://www.infradead.org/~tgr/libnl (currently the site is down)
--
To unsubscribe from this list: send the line "unsubscribe linux-wpan" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
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.

Re: Linux-Wpan-Next: Regarding usage of fakelb driver

[Alexander Aring]

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/GettingStarted-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