Re: [Wireshark-dev] Warning message when starting wireshark "color_filters.c:658 -- read_filters_file(): Could not compile "Checksum Errors" in colorfilters "

I will check. Sorry I missed this. On 08/10/21 11:56, Anders Broman via Wireshark-dev wrote: Hi, Top of trunk I get ** (wireshark:13228) 12:52:43.789284 [Epan WARNING] C:\Development\wireshark\epan\color_filters.c:658 -- read_filters_file(): Could not compile "Checksum Errors" in colorfilter

Re: [Wireshark-dev] Display filter field variables

Thanks a lot. :-) Seems like I was wrong and it's a macro after all. On 08/10/21 16:31, chuck c wrote: Display Filter Macros of currently selected packet fields https://gitlab.com/wireshark/wireshark/-/wikis/DFilterMacro https://g

Re: [Wireshark-dev] Display filter field variables

Display Filter Macros of currently selected packet fields https://gitlab.com/wireshark/wireshark/-/wikis/DFilterMacro https://gitlab.com/wireshark/wireshark/-/commit/9865b6346f6442bc8326cde55e5f012250748131 On Fri, Oct 8, 2021 at 10:10 AM João Valverde via Wireshark-dev < wireshark-dev@wireshark.

[Wireshark-dev] Display filter field variables

Hi, The GUI display filter has an interesting but little-known (?) feature to replace field values for the selected frame with the syntax ${}, which I only learned about in bug #15504, and confused me at first. This all happens before the expression is compiled and is different from display f

[Wireshark-dev] Warning message when starting wireshark "color_filters.c:658 -- read_filters_file(): Could not compile "Checksum Errors" in colorfilters "

Hi, Top of trunk I get ** (wireshark:13228) 12:52:43.789284 [Epan WARNING] C:\Development\wireshark\epan\color_filters.c:658 -- read_filters_file(): Could not compile "Checksum Errors" in colorfilters file "C:\Development\wsbuild-gpl\run\RelWithDebInfo\colorfilters". "Bad" cannot be converted to

Re: [Wireshark-dev] Sample of IAX2 with RTP

Hi, first: I didn't received this response from mailing system even I'm receiving other wireshark-dev communication as expected. I noticed it in archive... > Be very careful to not change any calculation made in accordance to > RFC 3550. > People depend on these algorithms as well as the naming