Hi Anatoliy, Xue,
>> ci40 has already some work on it. You could have a look.
Currently we have the lowpan configuration for Creator Ci40 at
https://github.com/CreatorDev/openwrt/blob/ci40/target/linux/pistachio/base-files/etc/uci-defaults/config/network.
And lowpan proto setup is done by
https://github.com/CreatorDev/openwrt/blob/ci40/target/linux/pistachio/base-files/lib/netifd/proto/lowpan.sh
We have received a review comment regarding lowpan.sh in our first upstream
Pull request (https://github.com/openwrt/openwrt/pull/95 which is obsoleted by
a basic Ci40 port https://github.com/openwrt/openwrt/pull/201 superseded by )
> It would be better to put this into an extra package for example into
> the iwpan package, this will probably also work on other devices and
> should be used there.
so we are in the process of making it generic so that is up-streamable.
We are thinking of moving lowpan.sh to
https://github.com/openwrt/openwrt/tree/master/package/network/utils/wpan-tools
and have lowpan mac address generation logic in a platform specific script and
just call that in the lowpan.sh.
However currently we have channel, pan_id, ip address all statically stored
(etc/config/network) in our case, and we pass these information to lowpan.sh to
configure the wpan interface.
Comments/critics are welcome.
Sounds like our mechanism is similar to your option 1. Just that you are
storing the configuration in /etc/config/wpan and we are storing in
/etc/config/network.
So do you have any other mechanism to configure wpan interfaces? Or is it
similar to our
https://github.com/CreatorDev/openwrt/blob/ci40/target/linux/pistachio/base-files/lib/netifd/proto/lowpan.sh
?
Please keep us updated.
Thanks and Regards,
Abhijit A. Mahajani
--
Message: 3
Date: Thu, 12 Jan 2017 02:02:05 +0200
From: Anatoliy Atanasov <anatoliy.atana...@gmail.com>
To: openwrt-devel@lists.openwrt.org
Subject: [OpenWrt-Devel] [RFC][netifd]: Support for 802154 devices
Message-ID:
<CA+9JBv89VcFpbziQfAy=LtOBgWop=lqmked3p275hu2pqd3...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hey Folks,
I saw that netifd isn't able to fully manage 802154 devices. At the moment it
lacks the understanding of wpan settings and definition. If it would be in a
separate file it would look like:
/etc/config/wpan
config wpan-device radio0
option type 'mac80215'
option channel '11'
option disabled '0' / '1'
config wpan-iface
option device 'radio0'
option pan_id '0xbeef'
I figured two ways to implement this.
The approach #1 is to follow the logic in wireless.h/c which wraps calls to the
kernel driver in mac80211.sh & netifd-wireless.sh.
The approach #2 is to replicate the wpan-tools code which would add a
dependency to libnl.
I'm wondering which approach to follow in doing this task?
Regards, Anatoliy
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openwrt.org/pipermail/openwrt-devel/attachments/20170112/bb9633a6/attachment-0001.html>
--
Message: 4
Date: Thu, 12 Jan 2017 10:14:47 +0100
From: Xue Liu <xue@dks-koeln.de>
To: Anatoliy Atanasov <anatoliy.atana...@gmail.com>,
openwrt-devel@lists.openwrt.org
Subject: Re: [OpenWrt-Devel] [RFC][netifd]: Support for 802154 devices
Message-ID: <8e2fcb0d-c3aa-1951-b0e3-2f4ea573b...@dks-koeln.de>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Hi Anatoliy,
Actually I am working on it. Now I am writing a program which is similar with
iwinfo. Later I will make some scripts like mac80211.sh and binding with netifd.
ci40 has already some work on it. You could have a look.
Xue Liu
On 12.01.2017 01:02, Anatoliy Atanasov wrote:
> Hey Folks,
>
> I saw that netifd isn't able to fully manage 802154 devices. At the
> moment it lacks the understanding of wpan settings and definition. If
> it would be in a separate file it would look like:
> /etc/config/wpan
>
> config wpan-device radio0
> option type 'mac80215'
> option channel '11'
> option disabled '0' / '1'
>
> config wpan-iface
> option device 'radio0'
> option pan_id '0xbeef'
>
> I figured two ways to implement this.
> The approach #1 is to follow the logic in wireless.h/c which wraps
> calls to the kernel driver in mac80211.sh & netifd-wireless.sh.
> The approach #2 is to replicate the wpan-tools code which would add a
> dependency to libnl.
>
> I'm wondering which approach to follow in doing this task?
>
> Regards, Anatoliy
>
>
>
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo
