On Thu, 2010-12-09 at 11:48 +0100, Sven Neumann wrote: > When a cached BSS struct is updated because a new beacon was received, > the code replaces the cached information elements by the IEs from the > new beacon. However it did not update the pub.information_elements > and pub.len_information_elements fields leaving them either pointing > to the old beacon IEs or in an inconsistent state where the data is > replaced by the new beacon IEs but len_information_elements still has > its value from the first beacon. > > Fix this by updating the information elements fields if they are > pointing to beacon IEs. Err, no, this is intentional -- we want data from probe responses to "win" and be displayed preferentially. If you look at the code that dumps them out, that's what will happen. If you need the most up-to-date beacon IEs, use (the equivalent of) "iw wlan0 scan dump -b". johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
