From: Sven Eckelmann <sven@narfation.org>
To: Johannes Berg <johannes@sipsolutions.net>
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 12:38:54 +0200 [thread overview]
Message-ID: <1999032.fCPl2VLiSg@bentobox> (raw)
In-Reply-To: <9a1d7a6651d3bf6c4a43c5bc8659df690c009328.camel@sipsolutions.net>
[-- Attachment #1.1: Type: text/plain, Size: 1529 bytes --]
On Friday, 12 July 2019 11:42:51 CEST Johannes Berg wrote:
> 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.
I will prepare a patch now for hostap after lunch.
> And
> I guess newer tshark (which you used) is fixed again, if I understand
> correctly?
Yes and no, the master branch is fixed. But unfortunately, there is no
release with this fix.
And the problems is there since commit 3c427376579a ("802.11: Use
proto_tree_add_bitmask") and release v2.4.0rc0. But unfortunately, the
workaround was added with commit 2cbaf0de223b ("tests: Work around tshark bug
in wpas_mesh_max_peering") instead of bringing a fix upstream.
Kind regards,
Sven
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
WARNING: multiple messages have this Message-ID (diff)
From: Sven Eckelmann <sven@narfation.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
hostap@lists.infradead.org
Subject: Re: [PATCH v3 0/3] mac80211/ath11k: HE mesh support
Date: Fri, 12 Jul 2019 12:38:54 +0200 [thread overview]
Message-ID: <1999032.fCPl2VLiSg@bentobox> (raw)
In-Reply-To: <9a1d7a6651d3bf6c4a43c5bc8659df690c009328.camel@sipsolutions.net>
[-- Attachment #1: Type: text/plain, Size: 1529 bytes --]
On Friday, 12 July 2019 11:42:51 CEST Johannes Berg wrote:
> 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.
I will prepare a patch now for hostap after lunch.
> And
> I guess newer tshark (which you used) is fixed again, if I understand
> correctly?
Yes and no, the master branch is fixed. But unfortunately, there is no
release with this fix.
And the problems is there since commit 3c427376579a ("802.11: Use
proto_tree_add_bitmask") and release v2.4.0rc0. But unfortunately, the
workaround was added with commit 2cbaf0de223b ("tests: Work around tshark bug
in wpas_mesh_max_peering") instead of bringing a fix upstream.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-07-12 10:38 UTC|newest]
Thread overview: 26+ 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 ` 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 ` Sven Eckelmann
2019-06-12 19:35 ` [PATCH v3 2/3] mac80211: implement HE support for mesh Sven Eckelmann
2019-06-12 19:35 ` Sven Eckelmann
2019-06-14 14:11 ` Johannes Berg
2019-06-14 14:11 ` Johannes Berg
2019-06-14 14:13 ` Sven Eckelmann
2019-06-14 14:13 ` Sven Eckelmann
2019-06-14 14:14 ` Johannes Berg
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-12 19:35 ` Sven Eckelmann
2019-06-14 14:10 ` [PATCH v3 0/3] mac80211/ath11k: HE mesh support Johannes Berg
2019-06-14 14:10 ` Johannes Berg
2019-07-03 9:23 ` Sven Eckelmann
2019-07-03 9:23 ` Sven Eckelmann
2019-07-12 7:58 ` Johannes Berg
2019-07-12 7:58 ` Johannes Berg
2019-07-12 9:36 ` Sven Eckelmann
2019-07-12 9:36 ` Sven Eckelmann
2019-07-12 9:42 ` Johannes Berg
2019-07-12 9:42 ` Johannes Berg
2019-07-12 10:38 ` Sven Eckelmann [this message]
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=1999032.fCPl2VLiSg@bentobox \
--to=sven@narfation.org \
--cc=ath11k@lists.infradead.org \
--cc=hostap@lists.infradead.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.