New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

"base.HEX" or "base.NONE" in proto_fields.lua? #9

Open

amomorning opened this issue Jun 18, 2018 · 1 comment

amomorning commented Jun 18, 2018

I found that this plugin didn't decode my proto, if I changed "base.HEX" into "base.NONE" as noted.

wasphin commented Jan 19, 2019

According to this answer

FT_BYTES fields are always displayed as hex, you just get to choose what separates the hex digit pairs for the bytes, if anything. Choose one of base.NONE, base.DOT, base.DASH, base.COLON or base.SPACE

wasphin added a commit to wasphin/protobuf_dissector that referenced this issue


          FT_BYTES fields are always displayed as hex

b41a703

fix 128technology#9, see answer [here](https://osqa-ask.wireshark.org/questions/63411/multiple-lua-error-during-loading-issues-reported-after-install-of-win64-version-240/63414)

wasphin mentioned this issue

FT_BYTES fields are always displayed as hex #10

Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment