Wireshark mailing list archives

Re: question about bug 3303


From: Sake Blok <sake () euronet nl>
Date: Fri, 3 Sep 2010 16:04:49 +0200

On 3 sep 2010, at 15:24, kolos_ws () ural2 hu wrote:

Can someone confirm to me what is happening to bug 3303 
(https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3303) at the moment? 
It hasn't seen much activity lately.

Thank you for pinging, this bug is still on my list to look at. But time is a limited resource :-(  and this issue is 
kind of a tough one to dig into.


Although it is categorised as 'Low Normal' importance at the moment, in my 
case it is a showstopper and would love to see it resolved.

Are you sure you are encountering the same issue? There were some reports of similar issues that actually had a 
different cause. Will you be able to post a capture file showing the issue you have at hand? That way it can be 
determined if you run into the same issue. You can attach the tracefile to the bug-report. If necessary, you can mark 
it as private so that only the core-developers have access to it.

Cheers,


Sake

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request () wireshark org?subject=unsubscribe


Current thread: