[Alexis La Goutte <alexis.lagoutte@xxxxxxxxx>]

Hi Pablo,

For me, it is better to add duplicate field and set generated 

Le ven. 13 déc. 2024 à 15:38, Pablo MARTIN-GOMEZ <pmartin-gomez@xxxxxxxxxx> a écrit :

Hello all,

I've started working on the ieee80211-radio dissector. My main need is
to debug Wi-Fi performance problems, so one value I'm interest in is the
MCS index. To my regret, this parameter is split between various fields
depending on the 802.11 standard used by the frame: 
`wlan_radio.11be.mcs`,  `wlan_radio.11ac.mcs` and
`wlan_radio.11n.mcs_index`. I would like to have one field for MCS for
the 11n, 11ac, 11ax & 11be standards, `wlan_radio.mcs_index`. I'm not
sure what is the best course of action here: do I refactor the dissector
to only have the `wlan_radio.mcs_index` field (and so, breaking the
setup of the people using `wlan_radio.11be.mcs` & co) or do I add the
`wlan_radio.mcs_index` field in addition on the current ones and having
the value duplicated in the items?

Thanks,

Pablo MG


_______________________________________________
Wireshark-dev mailing list -- wireshark-dev@xxxxxxxxxxxxx
To unsubscribe send an email to wireshark-dev-leave@xxxxxxxxxxxxx