Comment # 19
on bug 12412
from [email protected]
(In reply to Pascal Quantin from comment #18)
> To see whether it helps or not, I just built a Wireshark 2.1 development
> release using c-ares 1.11.0 instead of 1.9.1.
>
> Could you give it a try and see if you still face the issue?
It fixes the problem where the IPv6 resolver address is interpreted as an IPv4
address. BUT, it fails to make use of the IPv6 path and uses only the IPv4
resolver address. Nicely load balances across them. I ran a CYGWIN 'dig'
@v6addr to verify the v6 path works and my DNS resolver Wireshark sees them.
Observed that the filling-in of the rDNS names is slow and glitchy in Wireshark
v2. Had to force a refresh of the packet view before all the names that were
cached by libcares replaced the addresses.
Also observed that v2 steps all over the window positions of v1 (which I am
definitely not uninstalling yet.) They ought to be separate and not conflict.
BEST of all. The new libcares works with v1 Wireshark and the rDNS fill-in is
now blindly fast. Thanks!
> In case you are unhappy with the Qt based GUI, you can still find the GTK
> based UI under the name "Wireshark Legacy".
I'll try that. Thanks.
You are receiving this mail because:
- You are watching all bug changes.