Re: [Wireshark-dev] 1.10 branch + release schedule

Gerald Combs wrote: > (Which reminds me - we need to set a schedule > for dropping Windows XP support.) Despite M$ enthusiasm for not supporting XP it lives on on many systems which perform their assigned duties and don't have resources to run later versions. How practical would it be to create a

Re: [Wireshark-dev] Bug found

Bill Meier wrote: ... > This issue appears to be similar to (the same ?) as that reported in > https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=553. > > In the comments near the end there's a reference to a GIMP code > workaround (related to a GTK bug) for a similar issue and then a comment > a

Re: [Wireshark-dev] SVN version number in the documentation?

Guy Harris wrote: > I suspect their problem was that they didn't have Subversion installed on the > build machine, so there was no svnversion command available If you are building from a SVN/CVS tree you should be expected to have the tools on the build machine. > The User's Guide says "36497 f

Re: [Wireshark-dev] snmp decoding ...ubuntu smi issue ?... different then on windows XP ...?

Apologies in advance for the tone, but some actions are inexcusable. Jaap Keuter wrote: > > Hi, > > Some history: > > libsmi doesn't provide MIBs any more, due to > Debian bug 498476 [7] The bug belongs to Debian, not libsmi. limsmi provides MIBs. Debian chooses to not include them. > MIB

Re: [Wireshark-dev] snmp decoding ...ubuntu smi issue ?... different then on windows XP ...?

Before we get any deeper I don't run Ubuntu. Slackware rules. Sandor, Todd (Todd) wrote: > What version of libsmi does Ubuntu have? The current one is 0.4.8, but I > tend to use the one in Subversion. > > Todd> According to "About Wireshark", it using SMI 0.4.8 ... Good start. > Are your MIBs

Re: [Wireshark-dev] snmp decoding ...ubuntu smi issue ?... different then on windows XP ...?

Sandor, Todd (Todd) wrote: > Hi: > > I had a couple of Ubuntu newbie problems getting Wireshark installed on > Unbuntu that included SMI to allow snmp decoding and was finally able to get > it to a point where I could configure SMI paths and SMI modules ... > I also have a Wireshark on an XP box

Re: [Wireshark-dev] Wireshark 1.2.13 is now available

Stephen Fisher wrote: > On Sun, Nov 21, 2010 at 04:22:19PM +0100, Joerg Mayer wrote: > > >>On Fri, Nov 19, 2010 at 12:24:08PM -0800, Gerald Combs wrote: >> >>>Known Problems >>> >>> Wireshark may appear offscreen on multi-monitor Windows systems. >>> (Bug 553) >> >>Is it true that this bugfix

Re: [Wireshark-dev] Move from C89 to C99?

Guy Harris wrote: > On Jan 18, 2010, at 8:03 AM, Joerg Mayer wrote: > > >>with Wireshark being more than 10 years old and e.g. requiring glib2/gtk2, >>maybe it would be OK to move the coding requirements from C89 to C99. >>This would give us // comments, inline keywords and the like. >> >>What do

Re: [Wireshark-dev] How does Wireshark do name resolution?

This really belongs in "users", but since it is here ... Richard Brooks wrote: > Wireshark must have got the 'bskyb-pop3-ssl.l.google.com' result somehow. I > can do an nslookup just after Wireshark comes back with > 'bskyb-pop3-ssl.l.google.com' but I still get the same old vanilla flavoured > 'p

Re: [Wireshark-dev] How does Wireshark do name resolution?

Richard Brooks wrote: > Hello Guy > > Your just not getting it. > > The question is given the ip address of '74.125.127.208', how does one query > a DNS server (in this case DNS ip 8.8.8.8 = public Google DNS) to get the > reply 'bskyb-pop3-ssl.l.google.co' (which is the reply Wireshark gets), a

Re: [Wireshark-dev] slow startup caused by splash_update?

Nathan Jennings wrote: > On 4/6/2009 11:24 AM, Jeremy Linton wrote: > >>Jeff Morriss wrote: >> >>>Once Wireshark is up, is it usable [going to Gerald's suggestion]? >> >> Its a little lagy but usable. I wouldn't want to use it all day long, >> but its ok for intermittent use. My feeling is

Re: [Wireshark-dev] wireshark web site

Jaap Keuter wrote: > HI, > > Indeed it's new. Still, no problems on Iceweasel 3.0.5, Firefox 3.0.6 (WinXP) > or > Exploder (WinXP). Cache flush maybe? > Cache flush clears it, but the page still has 44 syntax errors (not just warnings) according to http://validator.w3.org/ -- There's no poi

[Wireshark-dev] wireshark web site

Has there been some significant change made to www.wireshark.org ? It is almost unreadable in Firefox 2, Firefox 3, and an old version of Mozilla. It was OK a few weeks ago. Some Internet Exploder only code maybe? -- There's no point in being grown up if you can't be childish sometimes.

Re: [Wireshark-dev] [Wireshark-commits] rev 26944: /trunk/plugins/profinet/ /trunk/plugins/profinet/: packet-dcerpc-pn-io.c

Ulf Lamping wrote: > [EMAIL PROTECTED] schrieb: > >>http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=26944 >> >>User: stig >>Date: 2008/12/09 05:42 AM >> >>Log: >> From Jim Young (bug 3105): >> Trivial patch to change two C++ style comments to standard C style comments. >> > > >

Re: [Wireshark-dev] G.722 payload export to .wav

Kukosa, Tomas wrote: > Hi, > > as I know, G.722 has just expired patents and is freely available. > > The C source code could be found in ITU-T G.191 > http://www.itu.int/rec/T-REC-G.191/en > > I am not 100% sure about licencing if we can use this source code in > Wireshark, it is why I have

Re: [Wireshark-dev] Error while setting up check-out of code

Peter Johansson wrote: > 2008/9/29 Luis EG Ontanon <[EMAIL PROTECTED] > > > Try to pass the proxy settings manually. > e.g.: > > HTTP_PROXY=1.2.3.4: > > nmake -f Makefile.nmake setup > > \Lego > > On Mon, Sep 29, 2008 a

Re: [Wireshark-dev] performing cpu/time intensive computation in a protocol dissector

l which could be perceived as being able to take advantage of a problem is not acceptable. It stands a fair chance of getting you fired and possibly prosecuted. I'm not going near the network with such a tool without a signed, notarised authority from the head of internal security, wi

Re: [Wireshark-dev] performing cpu/time intensive computation in a protocol dissector

Sake Blok wrote: > May I have your votes please? ;-) > > 1) Don't include the code at all There are enough weak key identifiers out there without burdening Wireshark with a CPU intensive test for a one off problem. The next time someone finds a weakness it is bound to be a different problem need

Re: [Wireshark-dev] wireshark 1.0.1?

Jaap Keuter wrote: > Hi, > > That is a good question. As you may already have seen we're collecting a lot > of bugfixes in the roadmap and eventually roll them into 1.0.1. When that > will > be is a little hard to predict. Currently there are some infrastructure > problems which have to be sor

Re: [Wireshark-dev] [Wireshark-commits] rev 25232: /trunk/ /trunk/: configure.in make-version.pl

Jaap Keuter wrote: > Hi, > > So isn't it time now to 'correct' the development release number from 1.0.99 > to 1.1.0? I've never liked this sort of version numbers since string comparisons don't sort them correctly. Consider GTK's: #define GTK_CHECK_VERSION(major,minor,micro)\ (GTK_MAJ

Re: [Wireshark-dev] [libsmi] Re: Building libsmi from SVN as a .dll

Juergen Schoenwaelder wrote: > On Wed, Apr 16, 2008 at 09:22:38AM +1000, Andrew Hood wrote: > > >>I think I have also tracked down one of the reasons wireshark crashes. > > > [...] > > >>At line 595 oids.c calls smiRenderOID to format the node. The impl

Re: [Wireshark-dev] Building libsmi from SVN as a .dll

Anders Broman wrote: > Hi, > I have experemented with building libsmi.dll from libsmi SVN > _http://www.ibr.cs.tu-bs.de/svn/libsmi_ with the included makefile-dll > and smi.def file > > It builds under MSVC6 I have not tested it but if some one likes to play > with it - here it is... > If you find

Re: [Wireshark-dev] [Wireshark-commits] rev 24770: /trunk/packaging/ /trunk/packaging/nsis/: Makefile.nmake wireshark.nsi /trunk/packaging/portableapps/win32/: makenmake.pl /trunk/packaging/u3/win32/:

Gerald Combs wrote: > [ I'm replying to -dev instead of Stephen directly since this warrants a more > detailed and public explanation. ] > > We have indeed decided to drop GTK1 support*. The main reasons are: > > - GTK1 has been unsupported by the GTK+ team for a long time now. The fact > t

Re: [Wireshark-dev] MIB path not saved with preferences

an add MIBs to it. >> >>What is the "correct" sequence of "Save", "Apply" and "OK" to get >>preferences saved? I would expect "Save" would be enough if that button >>is displayed. Which one of "Apply" and OK" sa

Re: [Wireshark-dev] MIB path not saved with preferences

; or "OK" does that stop the prefs being saved? Do you have to exit the dialog with "Cancel"? The principle of least surprise would suggest "Save" should be committed immediately. > Andrew Hood wrote: > >>Seen in Wireshark HEAD at 24705, but I've

[Wireshark-dev] MIB path not saved with preferences

Seen in Wireshark HEAD at 24705, but I've observed it before and expected it to have been picked up. If you add additional paths for MIBs in the preferences dialog they don't get saved in your prefernces. Or is this only happening because I have a full copy of libsmi and it is expecting to only u

Re: [Wireshark-dev] unnamed structs - epan/dissectors/packet-ieee802154.h

Stephen Fisher wrote: > On Fri, Mar 21, 2008 at 03:01:47PM +1100, Andrew Hood wrote: > > >>Is there any way to make use of unnamd steructs a compilation error? > > > Not with gcc from what I can find so far. > > >>+#define dst_addr16 dst_a

[Wireshark-dev] unnamed structs - epan/dissectors/packet-ieee802154.h

Is there any way to make use of unnamed structs a compilation error? -- There's no point in being grown up if you can't be childish sometimes. -- Dr. Who Index: epan/dissectors/packet-ieee802154.h === --- epan/dissec

Re: [Wireshark-dev] Problems with epan\oids.c

Peter Johansson wrote: > 2008/3/19, Bill Meier <[EMAIL PROTECTED] >: > > Guy Harris wrote: > > > > If it's not already exported, perhaps the libsmi developers weren't > > aware of the wonderful "feature" of the Windows development > > environment where

Re: [Wireshark-dev] Problems with epan\oids.c

Jaap Keuter wrote: > Hi, > > Could you point us to these newer versions? > > Thanx, > Jaap > ftp://ftp.ibr.cs.tu-bs.de/pub/local/libsmi/libsmi-0.4.7.tar.gz -- There's no point in being grown up if you can't be childish sometimes. -- Dr. Who

Re: [Wireshark-dev] Problems with epan\oids.c

Stig Bjørlykke wrote: > On 13. mars. 2008, at 15.51, Peter Johansson wrote: > >> Could this then be of the same type of issue that is with adns, hence >> it is required to recompile libsmi too if using another compiler for >> Wireshark on Windows than MSVC 6. Developer Studio 2005EE for instanc

Re: [Wireshark-dev] Problems with epan\oids.c

Luis EG Ontanon wrote: >>Did you compile it using MSVC 6? Could this then be of the same type of >>issue that is with adns, hence it is required to recompile libsmi too if >>using another compiler for Wireshark on Windows than MSVC 6. Developer >>Studio 2005EE for instance? > > > I cannot swear o

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

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

Guy Harris wrote: > I've checked in a change to do that check only if you're compiling with > warnings treated as errors (the way we do that currently works only with > GCC, and we default to *not* treating warnings as errors when not > compiling with GCC). Is it possible to *not* treat warnin

[Wireshark-dev] ethercat plugin

If you don't have a sufficiently recent C compiler (C99 maybe?), the ethercat plugin will not compile because of the unnamed struct. --- plugins/ethercat/packet-ethercat-datagram.h (revision 24270) +++ plugins/ethercat/packet-ethercat-datagram.h (working copy) @@ -32,10 +32,13 @@ { guin

[Wireshark-dev] SVN 24232 breaks build

epan\dfilter\syntax-tree.n declares deprecated_token "const char *" epan\dfilter\syntax-tree.c uses it deprecated_token "char *" comparing with similar usages, I dropped the "const" -- There's no point in being grown up if you can't be childish sometimes. -- Dr. Who _

Re: [Wireshark-dev] Unhandled exception - uat_gui.c

Luis EG Ontanon wrote: > Sorry, > I thought I wrote that... > > Instead of trying to export the variables that point to the uats we > should get the pointer by other means. The code snipplet was the means > for that. This works: In epan/libwireshark.def make smi_modules_uat and smi_paths_uat "DAT

[Wireshark-dev] Unhandled exception - uat_gui.c

SVN at 24225 Windows XP Pro SP2 M$ Visual Studio 8.0 (MSVC_VARIANT=MSVC2005) Python in c:\Python25 I have done "make -f Makefile.nmake clean" and "make -f Makefile.nmake setup" before "make -f Makefile.nmake" When I try to set either of the SMI parameters from the "Name Resolution" preference I g

Re: [Wireshark-dev] 0.99.7 release?

Ulf Lamping wrote: > Gerald Combs schrieb: > >>It's been a while since 0.99.6 was released (Holy crap! July 5!), so it would >>probably be a good idea to push 0.99.7 out the door. I'd like to make a >>prerelease on the 19th or 20th, with a final release a week later. >> > > I had the same idea

Re: [Wireshark-dev] About transport name resolution with the new services file

Francois-Xavier Le Bail wrote: > --- Andrew Hood <[EMAIL PROTECTED]> wrote: >>It it wasn't for Windows' broken behaviour in >>letting any port be >>ephemeral, that might make some sense. >> >>I have been forced to set registry values to make >

Re: [Wireshark-dev] About transport name resolution with the new services file

Richard van der Hoff wrote: > On Sat, 18 Aug 2007, Francois-Xavier Le Bail wrote: > > >>Hi List, >> >>In version 0.99.6 we have, by example : >>Source Destination Protocol Info >>10.0.0.2 62.210.65.158 TCP 3946 > http [ACK] ... >> >>In version 0.99.7-SVN-22549 we have : >>Source Destin

Re: [Wireshark-dev] Add additional SNMP MIBs to the Wireshark distribution?

Luis EG Ontanon wrote: > libsmi (that is going to be the one) has a rich collection of MIBs. > We could ask them whether or not we can redistribute them. libsmi's MIB collection have been editted to correct syntactic errors. libsmi's parser is MUCH more picky than net-snmp's parser. I ran the com

Re: [Wireshark-dev] libsmi license

Luis EG Ontanon wrote: > there's a win/ directory in the distribution and it looks that it's > been compiled already. I'll look for a binary or we might be able to > buid one ourselves, I have no windows box on weekends (infact they are > supposed to be for relax :-) so I'll try to compile it on mo

Re: [Wireshark-dev] /etc/services file for "port name resolvings"?

Joerg Mayer wrote: > [EMAIL PROTECTED]:~/work/vpn/vpnc/svn/work> lsb_release -a > LSB Version: > core-2.0-noarch:core-3.0-noarch:core-2.0-ia32:core-3.0-ia32:desktop-3.1-ia32:desktop-3.1-noarch:graphics-2.0-ia32:graphics-2.0-noarch:graphics-3.1-ia32:graphics-3.1-noarch > Distributor ID: SUSE LINUX >

Re: [Wireshark-dev] Remote Desktop color palette problem

Gerald Combs wrote: > Maynard, Chris wrote: > >>It seems that when running Wireshark 0.99.6 over a Windows XP Remote >>Desktop connection, there's a problem with the color palette, such that >>the text color is always white, rather than black. While it makes the >>text hard to read on a gray back

Re: [Wireshark-dev] --with-ssl action when gnutls is not found

Guy Harris wrote: > At least one of the reasons why we might need -lcrypto is that we use > NetSNMP to get information about particular SNMP variable bindings. So why not use libsmi instead? It has no reliance on any external libraries. The only disadvantage is that it is more picky than Net

[Wireshark-dev] Windows GTK2 build - colour problem

A little while back there was a discussion of GTK2 stuffing up the colour map on Windows. e.g. all black text is being displayed in white, which is really hard to read on a white background. I thought the GTK libs on the buildbot were updated to fix it. Both 0.99.5 release and SVN as of yesterday

Re: [Wireshark-dev] I've "officially" dropped support for Windows NT 4.0 ...

Ulf Lamping wrote: > Hi List! > > After a long time, I "felt" that it was time to drop support for Windows > NT 4.0! Is there a ** permanent ** link to a version that runs on NT4? I have a requirement for one, but don't have the tools to build for NT. Unless someone can come up with a set of fl

Re: [Wireshark-dev] Build Error in 0.99.4 LNK1181/U1073

Jan Kokott wrote: > Hi, > > I found out that much. > The -i option I got from > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore/html/U1077.asp > maybe that wasn´t a good idea. It depends. -k or -i can get as much as possible compiled in one run. You then run (n)make agai

Re: [Wireshark-dev] Microsoft Visual C Version 6support isa bitoutdated ...

Ulf Lamping wrote: >>I have MSVC 8.0 build 50727. I detest trying to use the M$ compiler >>suite, but sometimes the alternatives are worse. > > > Do you use the Express Edition or the Studio? "Add Remove Programs" lists it as "Microsoft Visual Studio 2005 Professional Edition - ENU" >>nmake Mak

Re: [Wireshark-dev] Microsoft Visual C Version 6support isa bitoutdated ...

Ulf Lamping wrote: > P.S.: In the meantime, I can successfully compile and run Wireshark > versions generated on every MSVC variant mentioned - so there's actually > some real progress in this topic ;-))) This is about as clear as I can make it. I have MSVC 8.0 build 50727. I detest trying to

Re: [Wireshark-dev] Microsoft Visual C Version 6 support isa bitoutdated ...

Ulf Lamping wrote: > Andrew Hood wrote: > >>Reading >>gzipped pcap files does work. >> > > That's the next I will look for - how to do this in a clean.way for all > compiler variants. The simplest solution would probably be to not download zlib123 b

Re: [Wireshark-dev] Microsoft Visual C Version 6 support isa bitoutdated ...

Ulf Lamping wrote: > Andrew Hood wrote: > >>http://groups.google.com/group/mailing.openssl.users/browse_thread/thread/72c89ea76c253905/76f8cbdc64a6efd6?lnk=st&q=MSVC+%22X509_NAME%22&rnum=1#76f8cbdc64a6efd6 >> >>and >> >>http://groups.google.com/grou

Re: [Wireshark-dev] Microsoft Visual C Version 6 support isa bitoutdated ...

Ulf Lamping wrote: > Andrew Hood wrote: > >>http://groups.google.com/group/mailing.openssl.users/browse_thread/thread/72c89ea76c253905/76f8cbdc64a6efd6?lnk=st&q=MSVC+%22X509_NAME%22&rnum=1#76f8cbdc64a6efd6 >> >>and >> >>http://groups.google.com/grou

Re: [Wireshark-dev] Microsoft Visual C Version 6 support isa bitoutdated ...

Ulf Lamping wrote: >>It wouldn't be this one by any chance? Quoting myself from December 05 >><[EMAIL PROTECTED]> >> >>In openssl.h I had to change the typedef for X509_NAME and all the >>places it is used to something else because of some error I suspect (but >>couldn't prove) is a name clash. X50

Re: [Wireshark-dev] Microsoft Visual C Version 6 support isa bitoutdated ...

Ulf Lamping wrote: > RABRET Laurent RD-MAPS-ISS wrote: -snip- >>Caution: if you test, DO NOT FORGET to compile "zlib" to ensure RT lib >>consistency. >> > > I've just disabled ZLIB (avoiding compilation of it - for now) and > GNUTLS (strange compiler error that I don't understand) in the > co

Re: [Wireshark-dev] Compiling under MSVC 8 - was about MSCV 6/7

Brian Vandenberg wrote: > Sleepless, > > The steps provided earlier by another responder work great in vs6. If > you're using vs7 or vs8 to debug you'll likely have trouble. I've tried MSVC8 pretty much following the MSVC7 hints, including recompiling zlib, which I know work because I've used MS

Re: [Wireshark-dev] win32: nmake setup: can't find cl

Graham Bloice wrote: >>A follow-up on issues when building wireshark on win32. >>I found out that if Cygwin "make" package is installed, Wireshark cannot >>be built anymore under win32 (cannot find "cl" and other dependencies). >>It might be a conflict between Cygwin's make and "nmake". >> >>Does s

Re: [Wireshark-dev] Proposal to move "Copy" on packet detail popup menu

Ulf Lamping wrote: > Jaap Keuter wrote: > >>Hi, >> >>I've done it. :) >> > > Hmmm, while looking at it - shouldn't the "Copy" item even be moved > under the "Follow SSL Stream" block? > > I'm using the "Apply As Filter" frequently and the "Copy" never ... Are you suggesting we need a Windows

Re: [Wireshark-dev] A problem of building wireshark under cygwin(libpcap)

Cook, Timothy wrote: > Have you explored the possibility of building using the recommended MSVC > 6/ CYGWIN combination??? A It makes it hard to understand the cause and effect. Q What's wrong with top-posting? I have Visual Studio .Net Professional 2003 and Visual Studio Professional 2005. These

Re: [Wireshark-dev] About /snmp/mibs attached to Wireshark

Akira Hashiguchi wrote: > Hello, > > May I use the file '/snmp/mibs' for our product gratuitously? The MIBs come from net-snmp, so you probably should be looking at their license conditions. It is also possible that net-snmp are using the corrected MIBs from libsmi (net-snmp used to have some MI

Re: [Wireshark-dev] conflict when built with OpenSSL on Mac OS X

Jeff Morriss wrote: > > LEGO wrote: > >>I noticed that when I build --with-ssl wireshark cannot read any file. >> >>If I compile without it works OK. >> >>We had a "similar" report on Solaris where WS crashed when reading the >>DTDs as soon as the reporter build it --without-ssl it worked. >> >>I