Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 1201] No VPN after tracing

Date: Sat, 4 Nov 2006 15:34:58 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1201


vadimrapp@xxxxxxxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |




------- Comment #2 from vadimrapp@xxxxxxxxxxxxx  2006-11-04 15:34 GMT -------
Dear Ulf,

I'm not familiar with the internals of the product, and don't even know what
WinCap is. I'm using Wireshark, I see this effect in Wireshark, and accordingly
I report it to Wireshark team. If you in turn determine that this is caused by
a component that you are using, then I think it's your turn to report it to the
3rd party, along with the reasons why you think it's their area (which I don't
know). Having not worked with wincap directly, being not even aware of what it
is, I don't think I can report it to them effectively.

Vadim Rapp


-- 
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.