On 04/24/2016 01:30 AM, Jouni Malinen wrote:
On Tue, Apr 19, 2016 at 07:06:49AM -0700, Ben Greear wrote:
The "vendor_elem" array is in the wpa_s struct, but the config logic
deals with "struct wpa_config", which has no way to reference wpa_s as
far as I can tell.
Correct.
Any opinion on moving wpa_s->vendor_elem to the wpa_config struct?
Or, maybe add a back-pointer from wpa_config to the wpa_s?
Why would either of those be needed? The new configuration parameters
would be completely independent of wpa_s->vendor_elem, i.e., they are
used only as a default value to set wpa_s->vendor_elem when bringing up
an interface. No further changes to the configuration parameter during
the lifetime of the interface would change wpa_s->vendor_elem and
similarly, no VENDOR_ELEM* command would change the value of the
configuration parameter.
My usage often involves writing out a new config file and then telling
supplicant to (re)load it. I would want any changes to the custom probe/assoc
ies to take affect at that time.
From your comment above, it seems you are suggesting a reload would not
effect the vendor elems?
Thanks,
Ben
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap
