Hi, On Wed, Nov 2, 2022 at 10:52 AM Miquel Raynal <miquel.raynal@xxxxxxxxxxx> wrote: > > Hi Alexander, > > aahringo@xxxxxxxxxx wrote on Sun, 30 Oct 2022 22:20:03 -0400: > > > Hi, > > > > On Wed, Oct 26, 2022 at 5:35 AM Miquel Raynal <miquel.raynal@xxxxxxxxxxx> 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? > > Not "none", because I would expect a NODE to be able to perform minimal > management operations, such as: > - scanning > - requesting an association > But in no case it is supposed to: > - send beacons > - manage associations > - be the PAN coordinator > - act as a relay > perfect, thanks. But still there is something which I don't get. The split you mentioned about the functionality is for me being a coordinator (IEEE spec) or pan coordinator (IEEE spec) which has the additional functionality of "send beacons, manage assocs, act as relay". So a coordinator (iftype) is a pan coordinator (IEEE spec) and a node (iftype) is a coordinator (IEEE spec), but _only_ when it's associated, before it is just a manually setup mesh node? I hope it's clear when meaning iftype and when meaning IEEE spec, but for the manual setup thing (node iftype) there is no IEEE spec, although it is legal to do it in my opinion. Thanks. - Alex
