dottedmag's profile - activity

overview network karma followed questions activity

2023-11-01 17:47:00 +0000	received badge	● Popular Question (source)
2023-02-08 22:24:10 +0000	received badge	● Popular Question (source)
2020-10-23 17:27:55 +0000	commented question	Lua: populate a field from DissectorTable In any case, I just tried it in my own Lua dissectors and it seems to work just fine Perfect, thank you.
2020-10-23 17:27:05 +0000	commented question	Lua: populate a field from DissectorTable Wait, all scripts have a shared global namespace? Then I'll figure it out. I thought every script is loaded in a separa
2020-10-23 11:33:36 +0000	commented question	Lua: populate a field from DissectorTable I'm trying to do what Wireshark does in dissecting, say, decoding Protocol field in IP. IP dissector delegates to a ip.p
2020-10-18 16:32:51 +0000	received badge	● Notable Question (source)
2020-10-18 16:32:51 +0000	received badge	● Popular Question (source)
2020-10-18 14:29:19 +0000	edited question	Lua: populate a field from DissectorTable Lua: populate a field from DissectorTable I'm dissecting a protocol where one of fields specifies the request kind. Diss
2020-10-18 14:28:55 +0000	asked a question	Lua: populate a field from DissectorTable Lua: populate a field from DissectorTable I'm dissecting a protocol where one of fields specifies the request kind. Diss
2020-08-27 12:05:17 +0000	marked best answer	Dissecting a field with a mixed content I'm writing a dissector for a protocol, and have stumbled upon the following field: rxRSSIVal IN RSSI measurement of the received frame. This is a signed 8-bit value. Values from RSSI_RESERVED_START to 124 are reserved. All values below RSSI_RESERVED_START are received power in dBms. RSSI_NOT_AVAILABLE - RSSI measurement not available RSSI_MAX_POWER_SATURATED - Receiver saturated. RSSI too high to measure precisely RSSI_BELOW_SENSITIVITY - No signal detected. The RSSI is too low to measure precisely. I understand how to mark reserved values as invalid via expert field. How can I format other values in the packet tree node? I looked at various field types and none of them seem to fit. Is there a custom field type where dissector code can control the displayed value? Ideally I'd also like to be able to support filtering `myproto.rxrssi=max_power_saturated` and `myproto.rxrssi=10`, but I'm not sure it is feasible.
2020-08-27 12:05:17 +0000	received badge	● Scholar (source)
2020-08-27 08:46:51 +0000	asked a question	Dissecting a field with a mixed content Dissecting a field with a mixed content I'm writing a dissector for a protocol, and have stumbled upon the following fie
2019-05-16 18:37:52 +0000	commented answer	Linking packets in a dissector I see that tracking requests/responses is based on addresses/ports. Should I do the manual tracking if I need things lik
2019-05-16 15:22:02 +0000	edited question	Linking packets in a dissector Linking packets in dissector I am writing a dissector for ZWave serial port protocol, and I would like to link request/r
2019-05-16 15:13:10 +0000	edited question	Linking packets in a dissector Linking packets in dissector I am writing a dissector for ZWave serial port protocol, and I would like to link request/r
2019-05-16 15:11:10 +0000	received badge	● Editor (source)
2019-05-16 15:11:10 +0000	edited question	Linking packets in a dissector Linking packets in dissector I am writing a dissector for ZWave serial port protocol, and I would like to link request/r
2019-05-16 15:10:19 +0000	asked a question	Linking packets in a dissector Linking packets in dissector I am writing a dissector for ZWave serial port protocol, and I would like to link request/r