[Wireshark-dev] Are retransmitted packets sometimes labelled as TCP out of order

Hi, I am analyzing a dump file using Wireshark and I found that some of the TCP messages that are sent again (with the same ACK) number are labelled as TCP Out of Rrder by Wireshark. I was expecting to find them labelled as retransmission messages. Is there a reason why the packets are labelled

[Wireshark-dev] Compilation issue on Mac OS

Hi, I am trying to compile wireshark from source that I took from github. I have libgcrypt on my system and the configure script was able to find it. However when I actually run make i get this error CC airpdcap.lo In file included from airpdcap.c:49: *../../wsutil/wsgcrypt.h:36:10:

Re: [Wireshark-dev] Compilation issue on Mac OS

;alexis.lagou...@gmail.com> wrote: > Hi, > > Do you have try with cmake ? > > On Thu, Apr 20, 2017 at 10:33 PM, ajay saxena <ailerona...@gmail.com> > wrote: > >> Hi, >> >> I am trying to compile wireshark from source that I took from github. I >> ha

Re: [Wireshark-dev] Compilation issue on Mac OS

note is compiling with cmake not recommended due to some reason? Thanks, Ajay Thanks, Ajay On Fri, Apr 21, 2017 at 12:54 PM, Guy Harris <g...@alum.mit.edu> wrote: > On Apr 21, 2017, at 5:23 AM, ajay saxena <ailerona...@gmail.com> wrote: > > > Thanks for replying. I use

Re: [Wireshark-dev] Compilation issue on Mac OS

s searched. Whereas when it compiles wireshark, it does not search in /usr/local/include. Thanks, Ajay On Fri, Apr 21, 2017 at 11:17 PM, ajay saxena <ailerona...@gmail.com> wrote: > This was the link that i was trying to send earlier > > http://stackoverflow.com/questions/23905661/on-mac-g

Re: [Wireshark-dev] Compilation issue on Mac OS

]: *** [all-recursive] Error 1 make[4]: *** [all] Error 2 make[3]: *** [all-recursive] Error 1 make[2]: *** [all] Error 2 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 On Sat, Apr 22, 2017 at 3:51 PM, Guy Harris <g...@alum.mit.edu> wrote: > On Apr 21, 2017,

Re: [Wireshark-dev] Compilation issue on Mac OS

k will work too. Thanks, Ajay On Sat, Apr 22, 2017 at 4:47 PM, ajay saxena <ailerona...@gmail.com> wrote: > In the Makefile of epan/dissectors, I modified the AM_CPPFLAGS to add -v > flag and removed the /usr/local/include that I had earlier added as hack to > get the pack-ip.c to com

Re: [Wireshark-dev] Compilation issue on Mac OS

for mylib.h in /Developer/SDKs/MacOSX10.4u.sdk/usr/include/mylib.h. On Sat, Apr 22, 2017 at 8:14 PM, ajay saxena <ailerona...@gmail.com> wrote: > Hi Guy, > > So i was able to find what is causing the issue. It is the -isysroot > option. > > The -sysroot option is also present wh

Re: [Wireshark-dev] Compilation issue on Mac OS

lt;g...@alum.mit.edu> wrote: > On Apr 21, 2017, at 10:07 AM, ajay saxena <ailerona...@gmail.com> wrote: > > > The commits that you've referred to, > > > > 9e4c018e08d5a657f85f0cde0607db0a6d25ddf4 > > 2c52d954d5713be1b809c3b668b0353d2b355c16 > > > &g

Re: [Wireshark-dev] Compilation issue on Mac OS

So i added the include lua directive at the top of the file and now i get the error for lua *packet-ip.c:27:10: **fatal error: **'lua.h' file not found* #include * ^* On Fri, Apr 21, 2017 at 4:29 PM, Guy Harris wrote: > What happens if you add a > >

Re: [Wireshark-dev] Compilation issue on Mac OS

Also cmake on the same source works, I would assume that it reads the header files from same locations unless it uses a fundamentally different resolution mechanism. On Fri, Apr 21, 2017 at 5:28 PM, Guy Harris <g...@alum.mit.edu> wrote: > On Apr 21, 2017, at 2:11 PM, ajay saxena

Re: [Wireshark-dev] Compilation issue on Mac OS

edu> wrote: > On Apr 21, 2017, at 11:22 AM, ajay saxena <ailerona...@gmail.com> wrote: > > > /usr/local/Cellar/geoip/1.6.9 is the location of GeoIP library > > /usr/local/Cellar/geoip/1.6.9/include is the location of GeoIP.h > > > > There is a symbolic link t

Re: [Wireshark-dev] Compilation issue on Mac OS

The compile fails with the same message even after I rename the existing sym link and phyiscally copy the file to my usr/local/include folder. On Apr 21, 2017 14:50, "Guy Harris" <g...@alum.mit.edu> wrote: > On Apr 21, 2017, at 11:37 AM, ajay saxena <ailerona...@gmail.co

Re: [Wireshark-dev] Compilation issue on Mac OS

Dec 31 00:52 wget -> ../Cellar/wget/1.18 lrwxr-xr-x 1 ajasaxen staff 25 Jan 30 13:10 wireshark -> ../Cellar/wireshark/2.2.4 lrwxr-xr-x 1 ajasaxen staff 18 Feb 17 15:38 xz -> ../Cellar/xz/5.2.3 lrwxr-xr-x 1 ajasaxen staff 22 Sep 9 2016 zeromq -> ../Cellar/zeromq/4.1.5

Re: [Wireshark-dev] Compilation issue on Mac OS

) the LIBGEOIP_CFLAGS is in both though. Do files in epan directory import GeoIP too? On Fri, Apr 21, 2017 at 5:06 PM, ajay saxena <ailerona...@gmail.com> wrote: > Please find attached, the Makefile in the epan directory. > > On Fri, Apr 21, 2017 at 5:02 PM, Guy Harris <g...@a

Re: [Wireshark-dev] Compilation issue on Mac OS

QtQuick gdfontg.h openjpeg-2.1 webp QtQuickControls2 gdfontl.h openslide zmq.h QtQuickParticles gdfontmb.h p11-kit-1 zmq_utils.h On Fri, Apr 21, 2017 at 3:23 PM, Guy Harris <g...@alum.mit.edu> wrote: > On Apr 21, 2017, at 12:18 PM, ajay saxena <ailerona...@gmail.com> wrote: > >

Re: [Wireshark-dev] Compilation issue on Mac OS

there be an issue with my script that generates these makefiles? I assumed that script that would generate these make files would add /usr/local/include in the search path by default On Fri, Apr 21, 2017 at 7:15 PM, ajay saxena <ailerona...@gmail.com> wrote: > I think the difference is when

Re: [Wireshark-dev] Compilation issue on Mac OS

I think the difference is when compiling using make, /usr/local/include is not present in the search path. Whereas when compiling with cmake /usr/local/include is present in the search path On Fri, Apr 21, 2017 at 7:12 PM, ajay saxena <ailerona...@gmail.com> wrote: > Us

Re: [Wireshark-dev] Compilation issue on Mac OS

.libs/packet-ip.o *packet-ip.c:63:10: **fatal error: **'GeoIP.h' file not found* #include * ^* On Fri, Apr 21, 2017 at 5:38 PM, Guy Harris <g...@alum.mit.edu> wrote: > On Apr 21, 2017, at 2:33 PM, ajay saxena <ailerona...@gmail.com> wrote: > > > Also cmake on t

Re: [Wireshark-dev] Compilation issue on Mac OS

ld-style-definition -Wstrict-prototypes -Wunused-const-variable -Wshorten-64-to-32 -Werror=implicit -std=gnu99 -Werror -o CMakeFiles/dissectors.dir/packet-ip.c.o -c /Users/ajasaxen/gitHubProjects/wireshark-official/wireshark/epan/dissectors/packet-ip.c On Fri, Apr 21, 2017 at 6:38 PM, ajay saxena &

Re: [Wireshark-dev] Compilation issue on Mac OS

This was the link that i was trying to send earlier http://stackoverflow.com/questions/23905661/on-mac-g-clang-fails-to-search-usr-local-include-and-usr-local-lib-by-def On Fri, Apr 21, 2017 at 11:17 PM, ajay saxena <ailerona...@gmail.com> wrote: > Hi Guy, > > So i found this o

Re: [Wireshark-dev] Compilation issue on Mac OS

Hi Guy, So i found this on stackoverflow On Fri, Apr 21, 2017 at 11:10 PM, Guy Harris <g...@alum.mit.edu> wrote: > On Apr 21, 2017, at 8:04 PM, ajay saxena <ailerona...@gmail.com> wrote: > > > This is what i get for gcc --version > > > > Ajays-MacBook-P

Re: [Wireshark-dev] Compilation issue on Mac OS

model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin On Fri, Apr 21, 2017 at 11:02 PM, Guy Harris <g...@alum.mit.edu> wrote: > On Apr 21, 2017, at 7:33 PM, ajay saxena <ailerona...@gmail.com> wrote: > > > T

[Wireshark-dev] Trying to enable logs for wireshark

Hi, I am running wireshark on a mac and I am trying to enable g_log for wireshark. As stated here, https://wiki.wireshark.org/Development/Tips, I am trying to change the console.log.level to 252, however the console.log.level setting appears to be frozen and I am unable to change it. The

Re: [Wireshark-dev] git doesn't like me anymore

You should be able to add your changes to the existing branch by running the following commands. These commands assume you are already on the branch using which you created the PR. git add updateFileName git commit -m "message" git push When you push the new commits to your fork that should help

Re: [Wireshark-dev] git doesn't like me anymore

mmits from your local branch. A pull/merge request helps to merge commits from a given repo/branch into another repo/branch. It also creates a diff between them that helps people to review the changes. On Sun, Jan 17, 2021 at 4:11 PM Fulko Hew wrote: > > > On Sun, Jan 17, 2021 at