Wireshark mailing list archives
Re: network monitor 3.4 traces cannot be read
From: "DePriest, Jason R." <jrdepriest () gmail com>
Date: Thu, 22 Jul 2010 12:23:26 -0500
But the issue doesn't exist with Wireshark 1.2.9? I'm running Netmon 3.4 and Wireshark 1.2.9 on a Windows XP Pro laptop and, much like you, needed to capture some traffic over a VPN connection. I did the capture in Netmon, pulled out the specific application I was concerned with and saved that as a Netmon .cap file. Wireshark opened it as a Netmon 2.x capture file and only had issues with the first frame where Netmon stores text information about the capture. Why does the problem only affect the dev versions of Wireshark? -Jason On Thu, Jul 22, 2010 at 9:59 AM, Graham Bloice <> wrote:
For what its worth, I just installed NM 3.4 to capture traffic over an MS VPN which WinPCap can't handle. Capture is fine, but NM doesn't have the protocol decoder I need (DNP3) so I tried to open the file in Wireshark 1.5.0-SVN-33615 (Win7 x64) and got the error dialog "The capture file has a packet with a network type that Wireshark doesn't support. (netmon: network type 0 unknown or unsupported)". I can make the capture available if folks want, I'm not in a position to look at this myself at the moment. I presume the issue might be to do with the capture being from a VPN adaptor. -- Regards, Graham Bloice
___________________________________________________________________________ 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:
- Re: Wireshark-users Digest, Vol 50, Issue 18 noah davids (Jul 20)
- Re: network monitor 3.3 traces cannot be read Guy Harris (Jul 20)
- network monitor 3.4 traces cannot be read Graham Bloice (Jul 22)
- Re: network monitor 3.4 traces cannot be read DePriest, Jason R. (Jul 22)
- Re: network monitor 3.4 traces cannot be read Guy Harris (Jul 22)
- Re: network monitor 3.4 traces cannot be read Stefaan Pouseele (Jul 22)
- Message not available
- Re: network monitor 3.4 traces cannot be read Guy Harris (Jul 22)
- Re: network monitor 3.4 traces cannot be read Gianluca Varenni (Jul 22)
- Re: network monitor 3.4 traces cannot be read Graham Bloice (Jul 23)
- Re: network monitor 3.4 traces cannot be read Guy Harris (Jul 23)
- Re: network monitor 3.4 traces cannot be read Graham Bloice (Jul 23)
- network monitor 3.4 traces cannot be read Graham Bloice (Jul 22)
- Re: network monitor 3.3 traces cannot be read Guy Harris (Jul 20)
- Re: network monitor 3.4 traces cannot be read Guy Harris (Jul 22)
- Re: network monitor 3.4 traces cannot be read Dave Howe (Jul 23)
- Re: network monitor 3.4 traces cannot be read Graham Bloice (Jul 23)