[Wireshark-dev] Can't capture traffic on some ports

I setup reverse proxy (Pound) to listen on standard ports 80 and 443 and pipe the data to backend server on the same machine (same IP address), to ports 81 & 83 respectively. Although everything passes OK, I can't capture any traffic on ports 81 or 83 either by using tcpdump or wireshark. Capturing

Re: [Wireshark-dev] warnings as errors ([Wireshark-users] Build problems with Sun's compiler on Solaris 10)

Guy Harris wrote: > Andrew Hood wrote: > > >>Is it possible to *not* treat warnings from system header includes as >>errors? Otherwise --disable-warnings-as-errors will have to stay in my >>config script. > > > I don't know any way to tell GCC to treat warnings from some include > files differ

Re: [Wireshark-dev] [Wireshark-commits] rev 24295: /trunk/ /trunk/epan/dissectors/: packet-dcerpc-nt.c packet-sccp.c packet-sctp.c /trunk/wiretap/: 5views.c iseries.c wtap-int.h

Gerald, What are the chances of getting the Sun C compiler instead of GCC on the Solaris builtbot? We seem to be getting more and more reports of Solaris build errors and warnings. On Sat, Feb 09, 2008 at 11:35:38PM +, [EMAIL PROTECTED] wrote: > http://anonsvn.wireshark.org/viewvc/viewvc.c

Re: [Wireshark-dev] Compilation warnings using Sun's comp ilers on Solaris 10

Dr. David Kirkby <[EMAIL PROTECTED]> writes: > > Hi all, > I thought this might be of use to some of the developers (if not copy to > /dev/null). It shows a number of warnings during compilation of release > 24290, some of which might just significant, such as integer overflows. > Thanks for