Search Linux Wireless

Re: [PATCH 2/4] o80211s: (nl80211) support for mesh interfaces and set_mesh_cfg command

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> @@ -36,6 +36,7 @@
>   *	%NL80211_ATTR_IFINDEX and %NL80211_ATTR_WIPHY. Can also be sent from
>   *	userspace to request deletion of a virtual interface, then requires
>   *	attribute %NL80211_ATTR_IFINDEX.
> + * @NL80211_CMD_SET_MESH_CFG: start mesh operation

So if I bring up a mesh interface and don't use SET_MESH_CFG, it won't
operate at all?

I think I'd prefer if the MESH_ID attribute would be given as part of
SET_INTERFACE/NEW_INTERFACE instead of a new command. I'm attempting to
keep nl80211 as object oriented as possible and this single command
doesn't really fit the picture.

In fact, you could deny creating a MESH type interface when no mesh ID
is given, that would be more obvious to the user imho than to deny
bringing it up later.

johannes

Attachment: signature.asc
Description: This is a digitally signed message part


[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux