lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 30 Oct 2022 22:20:03 -0400 From: Alexander Aring <aahringo@...hat.com> To: Miquel Raynal <miquel.raynal@...tlin.com> Cc: Alexander Aring <alex.aring@...il.com>, Stefan Schmidt <stefan@...enfreihafen.org>, linux-wpan@...r.kernel.org, "David S. Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, Eric Dumazet <edumazet@...gle.com>, netdev@...r.kernel.org, David Girault <david.girault@...vo.com>, Romuald Despres <romuald.despres@...vo.com>, Frederic Blain <frederic.blain@...vo.com>, Nicolas Schodet <nico@...fr.eu.org>, Guilhem Imberton <guilhem.imberton@...vo.com>, Thomas Petazzoni <thomas.petazzoni@...tlin.com> Subject: Re: [PATCH wpan-next v2 0/3] IEEE 802.15.4: Add coordinator interfaces Hi, On Wed, Oct 26, 2022 at 5:35 AM Miquel Raynal <miquel.raynal@...tlin.com> wrote: > > Hello, > These three patches allow the creation of coordinator interfaces, which > were already defined without being usable. The idea behind is to use > them advertizing PANs through the beaconing feature. > I still don't know how exactly those "leaves" and "non-leaves" are acting here regarding the coordinator interfaces. If this is just a bit here to set in the interface I am fine with it. But yea, "relaying" feature is a project on its own, as we said previously. Another mail I was asking myself what a node interface is then, currently it is a mesh interface with none of those 802.15.4 PAN management functionality? Or can it act also as a "leave" coordinator... I am not sure about that. However I think we can think about something scheduled later as we can still decide later if we really want that "node" can do that. Regarding to 6LoWPAN I think the current type what "node" interface is as a just a node in a mesh is required, it might depends on if you want routing on IP or "relaying" on MAC (mesh-over vs mesh-under), but I never saw mesh-under in 6LoWPAN. Acked-by: Alexander Aring <aahringo@...hat.com> Thanks. - Alex
Powered by blists - more mailing lists