Re: [Wireshark-dev] What's the difference between NdisMediumBare80211 (DLT_IEEE802_11) and NdisMediumRadio80211 (DLT_IEEE802_11_RADIO)

On Mar 30, 2016, at 5:09 PM, Yang Luo wrote: > I'm adding Native 802.11 capture support to Npcap and demonstrate it on > Wireshark. (See: > https://github.com/nmap/npcap/releases/download/v0.06-r13/npcap-nmap-0.06-r13-wifi.exe). > I found that the there are two 802.11 related values to show th

[Wireshark-dev] What's the difference between NdisMediumBare80211 (DLT_IEEE802_11) and NdisMediumRadio80211 (DLT_IEEE802_11_RADIO)

Hi list, I'm adding Native 802.11 capture support to Npcap and demonstrate it on Wireshark. (See: https://github.com/nmap/npcap/releases/download/v0.06-r13/npcap-nmap-0.06-r13-wifi.exe). I found that the there are two 802.11 related values to show the adapter type: NdisMediumBare80211 and NdisMedi

Re: [Wireshark-dev] Can't build GTK only using CMake on Windows7

I got nmake working again - it was the clashing link.exe, which IIRC was mentioned in the old developer guide (which is why I wanted to see it again). I think I am in as good a place as I can get for now - thanks for the help. Robert On 30 March 2016 at 20:53, Graham Bloice wrote: > returning

Re: [Wireshark-dev] Warn Dissector bug, protocol RADIUS

On Wed, Mar 30, 2016 at 2:05 PM, Jeff Morriss wrote: > > > On Wed, Mar 30, 2016 at 11:51 AM, Anders Broman < > anders.bro...@ericsson.com> wrote: > >> Hi, >> >> After the recent radius changes I get these console printouts for radius >> packets…. >> >> > Hey, you blamin' me? ;-) ;-) > Well you s

Re: [Wireshark-dev] Building with CMake on Win10 and VS2013 (win64)

On 30 March 2016 at 18:10, João Valverde wrote: > > > On 30-03-2016 16:46, Graham Bloice wrote: > >> >> >> On 30 March 2016 at 16:02, João Valverde >> > > wrote: >> >> >> >> On 30-03-2016 14:57, Graham Bloice wrote: >> >> >> >> On 30 March 2016

Re: [Wireshark-dev] Can't build GTK only using CMake on Windows7

returning this to -dev On 30 March 2016 at 17:00, Robert Cragie wrote: > Also, can you put back in the build instructions for nmake back into the > online docs somewhere even if it is deprecated? > > This is causing me a lot of headaches at the moment and I will probably > have to go back to a v

Re: [Wireshark-dev] Can't build GTK only using CMake on Windows7

returning this to -dev On 30 March 2016 at 16:53, Robert Cragie wrote: > It seems to be picking up the Windows installation of Python (which is in > the path). Removing this from the path will mess up a lot of things for me > as most of the time I do not want to use the cygwin python installatio

Re: [Wireshark-dev] Warn Dissector bug, protocol RADIUS

On Wed, Mar 30, 2016 at 11:51 AM, Anders Broman wrote: > Hi, > > After the recent radius changes I get these console printouts for radius > packets…. > > Hey, you blamin' me? ;-) ;-) > C:\Development\wireshark>17:30:27 Warn Dissector bug, protocol > RADIUS, > > in packet 65: proto.c:24

Re: [Wireshark-dev] Building with CMake on Win10 and VS2013 (win64)

On 30-03-2016 16:46, Graham Bloice wrote: On 30 March 2016 at 16:02, João Valverde mailto:joao.valve...@tecnico.ulisboa.pt>> wrote: On 30-03-2016 14:57, Graham Bloice wrote: On 30 March 2016 at 14:39, João Valverde mailto:joao.valve...@tecnico.ulisboa.pt>

Re: [Wireshark-dev] Obfuscating a capture

Juan Jose Martin Carrascosa writes: > Hi everybody, > is there an existing way to obfuscate a capture? For instance, select a few fields and make them zero or random. You might want to take a look at https://www.tracewrangler.com/, or if that doesn't meet your needs, try some of the other anonym

Re: [Wireshark-dev] Obfuscating a capture

Hi Juan, 2016-03-30 18:13 GMT+02:00 Juan Jose Martin Carrascosa : > Hi everybody, > > is there an existing way to obfuscate a capture? For instance, select a > few fields and make them zero or random. > > I want to find a way to obfuscate captures so we can provide them to other > people, or othe

[Wireshark-dev] Obfuscating a capture

Hi everybody, is there an existing way to obfuscate a capture? For instance, select a few fields and make them zero or random. I want to find a way to obfuscate captures so we can provide them to other people, or other people to us (security reasons). Any ideas? I don't feel like writing it myse

Re: [Wireshark-dev] Can't build GTK only using CMake on Windows7

On 3/30/16 8:44 AM, Graham Bloice wrote: > > There seems to be something wrong with the python installation in Cygwin. > To build the docbook stuff we use the Cygwin a2x utility that depends on > the Cywin python. There's quite a bit of juggling that goes on here to > keep things straight. I'm

[Wireshark-dev] Warn Dissector bug, protocol RADIUS

Hi, After the recent radius changes I get these console printouts for radius packets C:\Development\wireshark>17:30:27 Warn Dissector bug, protocol RADIUS, in packet 65: proto.c:2494: failed assertion "(guint)hfindex < gpa_hfinfo.len" ( Unregistered hf!) Regards Anders __

Re: [Wireshark-dev] Building with CMake on Win10 and VS2013 (win64)

On 30 March 2016 at 16:02, João Valverde wrote: > > > On 30-03-2016 14:57, Graham Bloice wrote: > >> >> >> On 30 March 2016 at 14:39, João Valverde >> > > wrote: >> >> >> >> No problems building the installer with NSIS 3.0b3. >> >> >> OK, now install o

Re: [Wireshark-dev] Can't build GTK only using CMake on Windows7

On 30 March 2016 at 16:12, Robert Cragie wrote: > I installed the latest Git (x64 version) and cleaned up my path, removing > all GNU/Linux like paths on there. This now seems to build OK with one > error on building: > > CustomBuild: > Building Custom Rule > C:/Users/robcra01/Documents/Wiresha

Re: [Wireshark-dev] Building with CMake on Win10 and VS2013 (win64)

On 30-03-2016 14:57, Graham Bloice wrote: On 30 March 2016 at 14:39, João Valverde mailto:joao.valve...@tecnico.ulisboa.pt>> wrote: No problems building the installer with NSIS 3.0b3. OK, now install on a non Windows 10 machine that doesn't have the VC2015 redist already installed.

Re: [Wireshark-dev] Can't build GTK only using CMake on Windows7

I installed the latest Git (x64 version) and cleaned up my path, removing all GNU/Linux like paths on there. This now seems to build OK with one error on building: CustomBuild: Building Custom Rule C:/Users/robcra01/Documents/WiresharkBitbucket/wireshark/docbook/CMakeLists.txt CMake does not n

Re: [Wireshark-dev] Building with CMake on Win10 and VS2013 (win64)

On 30 March 2016 at 14:39, João Valverde wrote: > > > On 30-03-2016 14:25, João Valverde wrote: > >> >> >> On 30-03-2016 14:20, João Valverde wrote: >> >>> >>> >>> On 30-03-2016 08:48, Graham Bloice wrote: >>> On 30 March 2016 at 03:10, João Valverde >>>

Re: [Wireshark-dev] Can't build GTK only using CMake on Windows7

On 30 March 2016 at 14:01, Robert Cragie wrote: > I have always had issues with trying to have both cygwin and git (or any > other pseudo-GNU/Linux environments) coexist on Windows. It is normally a > case of juggling paths until it just works. This is probably why (I can't > remember exactly why

Re: [Wireshark-dev] Building with CMake on Win10 and VS2013 (win64)

On 30-03-2016 14:25, João Valverde wrote: On 30-03-2016 14:20, João Valverde wrote: On 30-03-2016 08:48, Graham Bloice wrote: On 30 March 2016 at 03:10, João Valverde mailto:joao.valve...@tecnico.ulisboa.pt>> wrote: On 29-03-2016 21:46, Roland Knall wrote: Sorry, late ov

Re: [Wireshark-dev] Building with CMake on Win10 and VS2013 (win64)

On 30-03-2016 08:48, Graham Bloice wrote: On 30 March 2016 at 03:10, João Valverde mailto:joao.valve...@tecnico.ulisboa.pt>> wrote: On 29-03-2016 21:46, Roland Knall wrote: Sorry, late over here. You could try with cmake 3.5rc2. But beside that, I did not get W

Re: [Wireshark-dev] Building with CMake on Win10 and VS2013 (win64)

On 30-03-2016 14:20, João Valverde wrote: On 30-03-2016 08:48, Graham Bloice wrote: On 30 March 2016 at 03:10, João Valverde mailto:joao.valve...@tecnico.ulisboa.pt>> wrote: On 29-03-2016 21:46, Roland Knall wrote: Sorry, late over here. You could try with cmake 3.5rc2. But

Re: [Wireshark-dev] ./configure fails

Nice! And obvious... thanks! On Wed, Mar 30, 2016 at 2:59 PM, João Valverde < joao.valve...@tecnico.ulisboa.pt> wrote: > > > On 30-03-2016 11:46, Juan Jose Martin Carrascosa wrote: > >> Hi all, >> >> ./configure was working for me two weeks ago. >> >> Now it fails with: >> >> ./configure: line 19

Re: [Wireshark-dev] ./configure fails

On 30-03-2016 11:46, Juan Jose Martin Carrascosa wrote: Hi all, ./configure was working for me two weeks ago. Now it fails with: ./configure: line 19638: AX_COMPILER_VENDOR: command not found ./configure: line 19646: AX_COMPILER_VENDOR: command not found checking whether the compiler fails w

Re: [Wireshark-dev] Can't build GTK only using CMake on Windows7

I have always had issues with trying to have both cygwin and git (or any other pseudo-GNU/Linux environments) coexist on Windows. It is normally a case of juggling paths until it just works. This is probably why (I can't remember exactly why) I had to put the cygwin path ahead of the git path for n

Re: [Wireshark-dev] Can't build GTK only using CMake on Windows7

On 30 March 2016 at 12:05, Robert Cragie wrote: > I do have cygwin on the path. I needed this for nmake build and it hasn't > caused problems before. I have removed cygwin from the path and now I get > errors with CMake: > > The errors now are because you have the native git bin directory on the

[Wireshark-dev] Build error with Visual studio 2015 and nmake

Hi, I just tried to compile with Visual studio 2015 and Qt 5.6 and got the following error: wireshark_dialog.cpp .\wireshark_application.cpp(547): error C2664: 'void *ws_load_library(gchar *)': cannot convert argument 1 from 'const char [13]' to 'gchar *' .\wireshark_application.cpp(547): note: C

Re: [Wireshark-dev] Can't build GTK only using CMake on Windows7

I do have cygwin on the path. I needed this for nmake build and it hasn't caused problems before. I have removed cygwin from the path and now I get errors with CMake: -- Generating build using CMake 3.5.1 -- Building for win64 using Visual Studio 12 2013 Win64 Working in C:\Users\robcra01\Document

Re: [Wireshark-dev] Building with CMake on Win10 and VS2013 (win64)

On 30 March 2016 at 11:18, Robert Cragie wrote: > I needed to add the PLATFORM environment variable as well. I am using > VS2013 community edition. > I also use VS2013 CE and have never needed to set the platform variable. It's only required for x64 builds and is set by the appropriate Visual St

[Wireshark-dev] ./configure fails

Hi all, ./configure was working for me two weeks ago. Now it fails with: ./configure: line 19638: AX_COMPILER_VENDOR: command not found ./configure: line 19646: AX_COMPILER_VENDOR: command not found checking whether the compiler fails when given an unknown warning option... yes checking whether

Re: [Wireshark-dev] Building with CMake on Win10 and VS2013 (win64)

I needed to add the PLATFORM environment variable as well. I am using VS2013 community edition. Robert On 30 March 2016 at 08:56, Graham Bloice wrote: > > > On 29 March 2016 at 20:14, Michael Mann wrote: > >> I had gotten CMake to build on my setup a few months back, but it was a >> bit "quirk

Re: [Wireshark-dev] Can't build GTK only using CMake on Windows7

Comments in-line: On 30 March 2016 at 10:08, Robert Cragie wrote: > I updated cygwin and included asciidoc and the CMake output now doesn't > show asciidoc as missing optional. Here is the output from CMake (I removed > : > > cmake -G "Visual Studio 12 Win64" ..\wireshark > > -- The C compiler i

Re: [Wireshark-dev] Can't build GTK only using CMake on Windows7

I updated cygwin and included asciidoc and the CMake output now doesn't show asciidoc as missing optional. Here is the output from CMake (I removed : cmake -G "Visual Studio 12 Win64" ..\wireshark -- The C compiler identification is MSVC 18.0.40629.0 -- The CXX compiler identification is MSVC 18.

Re: [Wireshark-dev] Building with CMake on Win10 and VS2013 (win64)

On 29 March 2016 at 20:14, Michael Mann wrote: > I had gotten CMake to build on my setup a few months back, but it was a > bit "quirky" (I had to keep deleting and regenerating the build directory > because consecutive rebuilds would fail). > I tried again with a more recent version of master (ma

Re: [Wireshark-dev] Building with CMake on Win10 and VS2013 (win64)

On 30 March 2016 at 03:10, João Valverde wrote: > > > On 29-03-2016 21:46, Roland Knall wrote: > >> Sorry, late over here. You could try with cmake 3.5rc2. But beside that, >> I did not get WS compile correctly with VS2013 for some time now, need >> to use VS2015 myself. >> > > > Just another dat