Hi, I am testing the extended eNodeB ID type in the 3GPP-User-Location-Info avp, and came across something strange, and I am not sure if I am missing something or if this is a wireshark bug.
Take a look at the attached screenshot and the last 3 bytes (81 22 33), then take a look at how wireshark decoded SMeNB, it decoded it as if the first bit is 0, but if you convert 81 to binary you get 10000001.
So shouldn't wireshark decode the SmeNB bit as a 1? I am testing with wireshark and just kinda confused if I made a mistake or looking at a bug. I used wireshark on windows 7 version 3.6.6
Screenshot: