johnthacker's profile - activity

Also note that all the translations are always installed. I understand a reluctance to change your OS settings.. You can

Also note that all the translations are always installed. You can always go to Preferences and explicitly select English

Windows 11 has support for multiple languages. You almost certainly have English (United Kingdom) as your preferred lang

The previous open files dialog was a custom dialog using a Win32 API that has been deprecated by Microsoft. The current

The previous open files dialog was a custom dialog using a Win32 API that has been deprecated by Microsoft. The current

This was a Qt issue. The automated builds should work, please try one of the 4.6.6rc0 installers here: https://www.wires

In addition to the answer above, Wireshark does not link against OpenSSL so OpenSSL vulnerabilities are not relevant. Gn

https://github.com/morrownr/USB-WiFi is another good place for suggestions.

Is it not possible to configure with the expected server source port? The current version of Wireshark prefers using the

Since 4.2.0, Wireshark has included a built in Matter dissector. Is there a reason you need to use a third party dissect

If I understand correctly, your custom log file does not have the TCP layer at all, and just has the PDUs from each fram

They're on the context menu. Right click to see and change those options. They were relocated because they made it impos

Are you able to use Linux, macOS, or some other operating system other than Windows to do the capture? Higher resolution

Tshark uses the default profile without -C, not the last used profile the way Wireshark does

I am sorry, I misread what you wrote. Yes, the problem is in your preferences.

Try using -d rtp.pt=112,amr_wb instead in that command.

Use Dissector.get("cfdp") Protocol and dissector are not synonymous, as there can be (but is not always) multiple disse

It is also possible to build Qt yourself and set a flag apparently: https://bugreports.qt.io/browse/QTBUG-134075

It does seem like in the Windows documentation that SetThreadDescription is supposed to be available in Windows 2016, bu

It does seem like in the Windows documentation that SetThreadDescription is supposed to be available in Windows 2016, bu

There will be security related updates for Wireshark related issues for the life of 4.4 (which will be at least until 5.

Assuming thar your numbers fit in an appropriate size integer, I would declare a FT_UINT32 or whatever with the BASE_SPE

Windows Server 2016 is not supported on Qt 6.9 (or 6.8), and so the official Wireshark packages will not run on it. You

Windows Server 2016 is not supported on Qt 6.9 (or 6.8), and so the official Wireshark packages will not run on it. You

Qt 6.8 and later run on Windows 1809 or later, which is Server 2019 and Windows 10 with some service pack updates.

Windows Server 2016 is not supported on Qt 6.9 (or 6.8), and so the official Wireshark packages will not run on it. You

Usually the versions track fairly closely in the development version, but for stable releases of Wireshark it depends. S

There's a discussion here, but the only suggested method is using the Conversations dialog as you mention: https://gitla

You can also use -C on the command line with TShark to select particular configuration profiles other than the default,

One would think that the entry point would exist in the Qt6 DLL regardless of the version of Windows. The problem i

Wireshark has "codec" plugins. It is possible to add support for AMR-WB using the open source library. It would be very

Are you sure it's Windows 10? You said fresh install, is it fully updated, and to what update version? That's an error t

Are you sure it's Windows 10? You said fresh install, is it fully updated, and to what update version? That's an error t

https://gitlab.com/wireshark/wireshark/-/merge_requests/21025 will make it so that the actual filter is printed.

It appears that the difference is that show_filter_code in dumpcap is calling open_capture_device which eventually calls

It appears that the difference is that show_filter_code in dumpcap is calling open_capture_device which eventually calls

It appears that the difference is that show_filter_code in dumpcap is calling open_capture_device which eventually calls

Somewhat related is your own issue https://gitlab.com/wireshark/wireshark/-/issues/18190 What difference, if any, does