First time here? Check out the FAQ!
THIS IS A TEST INSTANCE. Feel free to ask and answer questions, but take care to avoid triggering too many notifications.
Ask Your Question
0

Is this a Wireshark bug?

  • retag add tags

I set mobility domain identifier in my device to 1234. I capture beacon frame with wireshark. In HEX window I see it is 1234. In tree i see: Mobility Domain Identifier: 0x3412.

Is this a Wireshark bug? or my device doesnt work properly?

wisniam's avatar
1
wisniam
asked 2021-05-19 10:32:30 +0000, updated 2021-05-19 10:33:19 +0000
edit flag offensive 0 remove flag close merge delete

Comments

Wireshark version?

grahamb's avatar grahamb (2021-05-19 10:34:24 +0000) edit
more
  • delete

Version 3.2.3 (Git v3.2.3 packaged as 3.2.3-1) My Wireshark is installed from repositories on Ubuntu 20.04 LTS

wisniam's avatar wisniam (2021-05-19 10:59:45 +0000) edit
more
  • delete

Unfortunately, as per usual with distro-provided versions, that is quite old. Can you either try with a new version, current stable is 3.4.5, or share the capture at a public place so others can check?

grahamb's avatar grahamb (2021-05-19 11:12:25 +0000) edit
more
  • delete

Maybe the whole little-endian big-endian war has stirred up again ;-)

hugo.vanderkooij's avatar hugo.vanderkooij (2021-05-19 12:08:05 +0000) edit
more
  • delete

I downloaded and compiled version 3.4.5 (Git commit 7db1feb42ce9) The result is the same. Also version 3.5.0 (v3.5.0rc0-1874-ge10f761362ba) give the same result.

I think this is a bug in the wireshark. It looks like the numbers are just swapped. Looks fine in HEX view. The topic of mobility domain is new to me and I'm not sure if it's a bug or not :) Maybe I don't know something :)

wisniam's avatar wisniam (2021-05-19 13:05:46 +0000) edit
more
  • delete
add a comment see more comments

1 Answer

0

Possibly a bug. Raise an issue at the Wireshark Gitlab site.

grahamb's avatar
23.8k
grahamb
answered 2021-05-19 13:25:30 +0000
edit flag offensive 0 remove flag delete link
more

Comments

Done. Thank You for help :) https://gitlab.com/wireshark/wireshar...

wisniam's avatar wisniam (2021-05-19 14:41:53 +0000) edit
more
  • delete

Not all of the devs frequent hereabouts, so the Issue should get the correct eyes on it.

grahamb's avatar grahamb (2021-05-19 14:56:39 +0000) edit
more
  • delete
add a comment see more comments

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss.

Add Answer