From: Johannes Berg <johannes@sipsolutions.net>
To: Sven Eckelmann <sven@narfation.org>
Cc: hostap@lists.infradead.org, linux-wireless@vger.kernel.org,
ath11k@lists.infradead.org
Subject: Re: [PATCH v3 0/3] mac80211/ath11k: HE mesh support
Date: Fri, 12 Jul 2019 09:58:50 +0200 [thread overview]
Message-ID: <06c7c1a2c8d0f955cb107475d17587c156fb19de.camel@sipsolutions.net> (raw)
In-Reply-To: <1610842.TRhm9evnVP@bentobox>
On Wed, 2019-07-03 at 11:23 +0200, Sven Eckelmann wrote:
>
> ~/tmp/wireshark/build/run/tshark -r /tmp/hwsim-test-logs/latest/wpas_mesh_max_peering.hwsim0.pcapng -T fields -e wlan.sa -e wlan.mesh.config.cap 'wlan.fc.type_subtype == 8'
> 02:00:00:00:01:00 0x00000009
> 02:00:00:00:00:00 0x00000009
> 02:00:00:00:01:00 0x00000009
> 02:00:00:00:02:00 0x00000009
> 02:00:00:00:00:00 0x00000008
> 02:00:00:00:01:00 0x00000009
> 02:00:00:00:02:00 0x00000009
> 02:00:00:00:00:00 0x00000008
>
> With wireshark 3.0.0:
>
> tshark -r /tmp/hwsim-test-logs/latest/wpas_mesh_max_peering.hwsim0.pcapng -T fields -e wlan.sa -e wlan.mesh.config.cap 'wlan.fc.type_subtype == 8'
> 02:00:00:00:01:00 0x00000001
> 02:00:00:00:00:00 0x00000001
> 02:00:00:00:01:00 0x00000001
> 02:00:00:00:00:00 0x00000001
> 02:00:00:00:02:00 0x00000001
> 02:00:00:00:01:00 0x00000001
> 02:00:00:00:02:00 0x00000001
> 02:00:00:00:00:00 0x00000001
>
> So I had to change the wireshark version (see below) which is used by hostapd.
> (just to document for me what I have forced it to a different version)
What. +hostap list.
This makes no sense, is that a tshark bug in one of the versions?
Maybe we should just use the JSON output, and parse that, but if tshark
now has a different idea of what the "wlan.mesh.config.cap" field is,
that won't help us at all?
Older versions were misparsing the HE element, but that has a length so
should only affect the HE element *itself*?
So ultimately, what do we do here?
Should we take this and sort out the tests?
johannes
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2019-07-12 7:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 19:35 [PATCH v3 0/3] mac80211/ath11k: HE mesh support Sven Eckelmann
2019-06-12 19:35 ` [PATCH v3 1/3] mac80211_hwsim: Register support for HE meshpoint Sven Eckelmann
2019-06-12 19:35 ` [PATCH v3 2/3] mac80211: implement HE support for mesh Sven Eckelmann
2019-06-14 14:11 ` Johannes Berg
2019-06-14 14:13 ` Sven Eckelmann
2019-06-14 14:14 ` Johannes Berg
2019-06-12 19:35 ` [PATCH v3 3/3] ath11k: register HE mesh capabilities Sven Eckelmann
2019-06-14 14:10 ` [PATCH v3 0/3] mac80211/ath11k: HE mesh support Johannes Berg
2019-07-03 9:23 ` Sven Eckelmann
2019-07-12 7:58 ` Johannes Berg [this message]
2019-07-12 9:36 ` Sven Eckelmann
2019-07-12 9:42 ` Johannes Berg
2019-07-12 10:38 ` Sven Eckelmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=06c7c1a2c8d0f955cb107475d17587c156fb19de.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath11k@lists.infradead.org \
--cc=hostap@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sven@narfation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox