On Fri, 2019-07-12 at 11:36 +0200, Sven Eckelmann wrote: > > There is already a workaround for that in the hostap testcases: > > if all_cap_one: > # It looks like tshark parser was broken at some point for > # wlan.mesh.config.cap which is now (tshark 2.6.3) pointing to incorrect > # field (same as wlan.mesh.config.ps_protocol). This used to work with > # tshark 2.2.6. > # > # For now, assume the capability field ends up being the last octet of > # the frame. > But maybe you already spotted the problem - it requires that mesh > configuration element is the last element. Which is not the case here - > similar to 5GHz tests (where you have most likely a VHT cap/oper element > after the meshconf_ie). > > I hope that this makes more sense now. Ah, yes, it does. So I guess we need to update/fix that workaround. And I guess newer tshark (which you used) is fixed again, if I understand correctly? johannes _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
