Skip to content

RFC mesh join/leave API

Johannes Berg linux-wireless 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest5 patches 3 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/5mac80211: use configured mesh TTLnet/mac80211/mesh.h net/mac80211/mesh_hwmp.c net/mac80211/mesh_pathtbl.c+8 -40 replies
2/5mac80211: move mesh filter adjustingnet/mac80211/iface.c net/mac80211/mesh.c+12 -170 replies
3/5cfg80211: require add_virtual_intf to return new devinclude/net/cfg80211.h net/mac80211/cfg.c net/wireless/nl80211.c+24 -140 replies
4/5nl80211: refactor mesh parameter parsingnet/wireless/nl80211.c+28 -141 reply
5/5cfg80211/mac80211: add mesh join/leave commandsinclude/linux/nl80211.h include/net/cfg80211.h net/mac80211/cfg.c +9 more+273 -9010 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

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