> The Beacon frames would probably need to update all <BSSID,*> entries > for the fields that we decide need to be updated based on Beacons, not > just the <BSSID,"">... Alternatively, we could change the BSS table to > have just one entry for each BSSID and a list of SSID entries for each > BSSID (with SSID, WPA/RSN IE, Privacy flag, etc. from ProbeResp). This > would be internal to kernel, though, and the scan result would likely > need to continue showing these as separate "BSSes" even though they have > the same BSSID. Oh. Good point. Any comments on Bill Moss's patch though? At least for the time being that seems like a reasonable thing to do. > Yeah.. Well, the problem is that no one has asked (as far as I know) for > this for a real world use case after multi-BSS support was added. Sure, > this would be nice for testing purposes, but the changes needed for > multi-SSID support are somewhat complex and would not only require quite > a bit of work now, but also make long term maintenance take more > effort.. > > I'm not completely against doing this, but this is not exactly on top of > my to-do list ;-). Right, makes sense :) johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
