RFC mesh join/leave API
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest5 patches 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | mac80211: use configured mesh TTLnet/ net/ net/ | +8 | 0 replies | |
| 2/5 | mac80211: move mesh filter adjustingnet/ net/ | +12 | 0 replies | |
| 3/5 | cfg80211: require add_virtual_intf to return new devinclude/ net/ net/ | +24 | 0 replies | |
| 4/5 | nl80211: refactor mesh parameter parsingnet/ | +28 | 1 reply | |
| 5/5 | cfg80211/mac80211: add mesh join/leave commandsinclude/ include/ net/ +9 more | +273 | 10 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC 0/5] mesh join/leave API
I'm heading to bed ... so the TTL thing will have to be figured out later. I've also not tested this at all, maybe you can :-)
Basically the idea is to decouple the state of mesh from interface UP/DOWN and add new commands to join/leave.
Then the beacon configuration can be part of join -- I suppose things that can change on the fly will be part of the mesh_config, and things that can't will become part of a new mesh_setup struct or so ... This way there's no need for new commands or such, just add new attributes to the join command...
Anyway, just an implementation of the ideas I was toying with.
johannes