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

2013-04-20 Thread Ulf Lamping
Am 19.04.2013 21:45, schrieb Gerald Combs: On 4/18/13 5:17 PM, Dirk Jagdmann wrote: Note that we would still be committed to supporting OS X PPC and U3 users until Wireshark 1.10 reaches end of life in 2015. I suggest remove OsX PPC and U3 even for the 1.10 release. After a bit of research i

Re: [Wireshark-dev] Ready to remove all non-ui-manager code?

2011-09-21 Thread Ulf Lamping
Am 14.09.2011 23:59, schrieb Joerg Mayer: Hello, would it be OK to remove the non-UI-MANAGER code in gtk/? I haven't seen any ongoing work in that area, so what (if anything) is missing from the UI-MANAGER codebase? The only things that come to my mind are the proto_help stuff and the gtkvumeter

Re: [Wireshark-dev] plugins to builtins

2011-06-21 Thread Ulf Lamping
Am 21.06.2011 10:23, schrieb Roland Knall: Now, the problems I had with the SercosIII plugin came from the fact, that it was a plugin, and therefore its proto_register method was called after(!) the proto_register method for the built-in dissectors. This lead to some confusion, where the dissecto

Re: [Wireshark-dev] plugins to builtins

2011-06-20 Thread Ulf Lamping
Am 21.06.2011 00:27, schrieb Roland Knall: Hi There is nothing technically wrong with dissectors being developed as plugins. There might be some technical questions that arise from that fact, if another dissector is using them, but for now, those issues seemed to be dealt with correctly (for ref

Re: [Wireshark-dev] plugins to builtins

2011-06-20 Thread Ulf Lamping
Am 20.06.2011 16:29, schrieb mman...@netscape.net: (just added myself to the mailing list so I can include reply history to the topic. This message touches on both Jaap's and Roland's comments) As the (main) author of the PROFINET plugin I may add a few cents ... Excuse me if I'm slightly wron

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

2010-02-24 Thread Ulf Lamping
Am 24.02.2010 09:22, schrieb s...@wireshark.org: > http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=31978 > > User: stig > Date: 2010/02/24 12:22 AM > > Log: > From Hannes Diethelm via bug 4525: > Corrected values for IdentInfo (which was obviously wrong) I've checked against t

Re: [Wireshark-dev] how to submit code to wireshark..??

2010-01-19 Thread Ulf Lamping
Am 20.01.2010 02:36, schrieb Brian Oleksa: > Japp and Chris > > Thank you for the reply. > > I really understand that you must follow the code standards or you will > have problems down the road. > I also understand that the core developers don't have much free time. > > My next question is: If the

Re: [Wireshark-dev] How about moving from svn to git?

2009-11-07 Thread Ulf Lamping
Joerg Mayer schrieb: > Hello, > > this is just something that went through my mind yesterday while working > on the third patch on the same files and without a chance to commit > between the patches. If there is one thing that I don't like (although > I do it sometimes) is to do a commit that does

Re: [Wireshark-dev] [Wireshark-commits] rev 30825: /trunk/ /trunk/gtk/: Makefile.common gui_utils.c gui_utils.h main_proto_draw.c main_statusbar.c /trunk/image/: expert_chat.h expert_chat.png expert_c

2009-11-04 Thread Ulf Lamping
Gerald Combs schrieb: > Stig Bjørlykke wrote: >> I really like the new icons! This may be very personal, but I think >> the blue "chat" and the gray "none" are a bit too dark. I think the >> chat icon should be more like the blue used in the background, and the >> gray more "anonymous". Th

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

2009-10-27 Thread Ulf Lamping
Gerald Combs schrieb: > Getting Wireshark > >Wireshark source code and installation packages are available from >the download page on the main web site. Hi! Why not simply say: Wireshark source code and installation packages are available from: http://www.wireshark.org/download.html

Re: [Wireshark-dev] Permission to Print.

2009-09-17 Thread Ulf Lamping
Long Lee schrieb: > Hello everyone, > > I bring a soft copy of the Wireshark user's guide: 29944 to the print > shop to print a hard copy for personal use. > > I was told that the can not print this document because of it's copyright. > > According to page 2 of the WireShark document, it stated

Re: [Wireshark-dev] New packet list is now the default.

2009-09-17 Thread Ulf Lamping
Anders Broman schrieb: > Hi, > I've made the new packet list the default build choice. I think it's in > a reasonable state and making it the default will help in fixing any > remaining issues. Hi! I guess I've started the first coding experiments on this topic some years ago, so I'm very plea

Re: [Wireshark-dev] Time for a new development release?

2009-07-28 Thread Ulf Lamping
Gerald Combs schrieb: > Ulf Lamping wrote: >> Hi! >> >> My colleagues would like to use the latest PROFINET dissector >> enhancements, that are not part of the stable release. >> >> The latest development release 1.1.3 at >> http://www.wireshark.org/do

Re: [Wireshark-dev] Time for a new development release?

2009-07-24 Thread Ulf Lamping
Jaap Keuter schrieb: > Hi, > > What's wrong with 1.2.1? Hi! AFAIK, e.g. the following PROFINET stuff that is not part of it: http://anonsvn.wireshark.org/viewvc?view=rev&revision=29150 http://anonsvn.wireshark.org/viewvc?view=rev&revision=28932 And as they are not bugfixes but extensions, they

[Wireshark-dev] Time for a new development release?

2009-07-23 Thread Ulf Lamping
Hi! My colleagues would like to use the latest PROFINET dissector enhancements, that are not part of the stable release. The latest development release 1.1.3 at http://www.wireshark.org/download.html is a bit, well, outdated. I don't like to advise my colleagues to use the daily builds, as they

Re: [Wireshark-dev] build wireshark on Windows xp with VC 6.0 failed

2009-06-28 Thread Ulf Lamping
Fenggen Jia schrieb: > When building the latest wireshark source from SVN(28879), the following > problem occurs: > " > mt: unknown option -- n > usage: mt [-V] [-f device] operation [count] > NMAKE : fatal error U1077: 'mt.exe' : return code '0x1' > Stop. > " > The mt version i'm using is below:

Re: [Wireshark-dev] Compile problems of capture_if_details_dlg_win32.c on MSVC2008EE and MSVC2005

2009-06-28 Thread Ulf Lamping
Kovarththanan Rajaratnam schrieb: >> >> I've seen the same problem on a MSVC2005 installation. >> >> Any ideas what changed in the last few weeks/months and what to do? > > This problem has existed for a while. See: > > https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3439 > Thanks for point

[Wireshark-dev] Compile problems of capture_if_details_dlg_win32.c on MSVC2008EE and MSVC2005

2009-06-28 Thread Ulf Lamping
Hi! After updating to the latest SVN, I get: capture_if_details_dlg_win32.c capture_if_details_dlg_win32.c(512) : error C2065: 'Ndis802_11AuthModeWPA2' : un declared identifier capture_if_details_dlg_win32.c(512) : error C2099: initializer is not a constant capture_if_details_dlg_win32.c(512)

Re: [Wireshark-dev] [Wireshark-commits] rev 28794: /trunk/gtk/ /trunk/gtk/: Makefile.common capture_dlg.c capture_file_dlg.c drag_and_drop.c file_dlg_win32.c fileset_dlg.c main.c main.h main_filter_to

2009-06-22 Thread Ulf Lamping
Guy Harris schrieb: > On Jun 22, 2009, at 1:41 AM, Ulf Lamping wrote: > >> Now you're telling me that file name in question is not 100% correct >> so >> you're changing it back into the chaos we once had - ignoring the >> benefits we could get from the n

Re: [Wireshark-dev] [Wireshark-commits] rev 28794: /trunk/gtk/ /trunk/gtk/: Makefile.common capture_dlg.c capture_file_dlg.c drag_and_drop.c file_dlg_win32.c fileset_dlg.c main.c main.h main_filter_to

2009-06-22 Thread Ulf Lamping
Guy Harris schrieb: > On Jun 21, 2009, at 11:53 PM, Ulf Lamping wrote: > >> But what are you trying to achieve? > > Being able to find files that implement more than "main" things, > whether it's the main menu or the main window. What I've tried

Re: [Wireshark-dev] [Wireshark-commits] rev 28794: /trunk/gtk/ /trunk/gtk/: Makefile.common capture_dlg.c capture_file_dlg.c drag_and_drop.c file_dlg_win32.c fileset_dlg.c main.c main.h main_filter_to

2009-06-21 Thread Ulf Lamping
Guy Harris schrieb: > On Jun 21, 2009, at 1:03 PM, Ulf Lamping wrote: > >> g...@wireshark.org schrieb: >>> http://anonsvn.wireshark.org/viewvc/viewvc.cgi? >>> view=rev&revision=28794 >>> >>> User: guy >>> Date: 2009/06/21 12:16 PM >

Re: [Wireshark-dev] [Wireshark-commits] rev 28794: /trunk/gtk/ /trunk/gtk/: Makefile.common capture_dlg.c capture_file_dlg.c drag_and_drop.c file_dlg_win32.c fileset_dlg.c main.c main.h main_filter_to

2009-06-21 Thread Ulf Lamping
g...@wireshark.org schrieb: > http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=28794 > > User: guy > Date: 2009/06/21 12:16 PM > > Log: > "main_menu.[ch]" -> "menus.[ch]"; it handles not only the main menu, but > context menus. Which menus that are not part of the main window d

Re: [Wireshark-dev] writing non-Ethernet pcapng files

2009-05-21 Thread Ulf Lamping
Aaron Turner schrieb: > On Thu, May 21, 2009 at 12:20 PM, Michael Tüxen > wrote: >> On May 21, 2009, at 9:15 PM, Aaron Turner wrote: >> >>> On Thu, May 21, 2009 at 11:55 AM, Michael Tüxen >>> wrote: Hi Aaron, can you check also with the latest svn version? >>> This was trunk-1.0 r2

Re: [Wireshark-dev] [Wireshark-commits] rev 27790: /trunk/ /trunk/epan/crc/: Makefile.am Makefile.common Makefile.nmake crc-16-plain.c crc-16-plain.h /trunk/epan/: Makefile.am Makefile.nmake crc16.c c

2009-03-20 Thread Ulf Lamping
ger...@wireshark.org schrieb: > http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=27790 > > User: gerald > Date: 2009/03/18 02:59 PM > > Log: > Create an "epan/crc" directory for CRC code. Add crc-16-plain.[ch], > generated from pycrc. The command line used to generate the file i

Re: [Wireshark-dev] New CRC code (Was: Re: WS 1.1.3 release?)

2009-03-18 Thread Ulf Lamping
Gerald Combs schrieb: > Richard van der Hoff wrote: >>> Also, it might be useful to have all of the CRC code in one place, such as >>> epan/crc/. It would be _really_ useful if each of our CRC modules listed >>> their >>> corresponding parameters. >> As the original author of epan/crc16.c, I could

Re: [Wireshark-dev] [Wireshark-commits] rev 27748: /trunk/plugins/profinet/ /trunk/plugins/profinet/: Makefile.common crc16.c crc16.h moduleinfo.h moduleinfo.nmake packet-dcerpc-pn-io.c packet-pn-rt.c

2009-03-16 Thread Ulf Lamping
Guy Harris schrieb: > On Mar 16, 2009, at 3:45 PM, Joerg Mayer wrote: > >> On Mon, Mar 16, 2009 at 09:40:03PM +, u...@wireshark.org wrote: >>> http://anonsvn.wireshark.org/viewvc/viewvc.cgi? >>> view=rev&revision=27748 >>> crc16 algorithm copied from Linux sources (GPL V2 only!) >> So far the

Re: [Wireshark-dev] [Wireshark-commits] rev 27748:/trunk/plugins/profinet/ /trunk/plugins/profinet/:Makefile.common crc16.c crc16.h moduleinfo.h moduleinfo.nmakepacket-dcerpc-pn-io.c packet-pn-rt.c

2009-03-16 Thread Ulf Lamping
Anders Broman schrieb: > Hi, > Isn't there a couple of crc versions in epan? Yes, and I tried the existing stuff. Unfortunately, there seems to be a multitude of possible implementations - none of the existing ones are compatible. I'm not an expert on this stuff, so it might be easy to rewrite

Re: [Wireshark-dev] [Wireshark-commits] rev 27748: /trunk/plugins/profinet/ /trunk/plugins/profinet/: Makefile.common crc16.c crc16.h moduleinfo.h moduleinfo.nmake packet-dcerpc-pn-io.c packet-pn-rt.c

2009-03-16 Thread Ulf Lamping
Joerg Mayer schrieb: > On Mon, Mar 16, 2009 at 09:40:03PM +, u...@wireshark.org wrote: >> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=27748 >> crc16 algorithm copied from Linux sources (GPL V2 only!) > > So far the wireshark sources are v2 or later - so adding a gplv2 onl

Re: [Wireshark-dev] GeoIP information presentation

2009-03-08 Thread Ulf Lamping
Jaap Keuter schrieb: > Hi list, > > Currently the GeoIP information is an alternating list of source and > destination > paramters, like so: > > [Source GeoIP Country: China] > [Destination GeoIP Country: Japan] > [Source GeoIP City: Tokyo, 40] > [Destination GeoIP City: Tok

Re: [Wireshark-dev] [Wireshark-commits] rev 27500: /trunk/ /trunk/epan/dissectors/: Makefile.common packet-opsi.c packet-opsi.h /trunk/packaging/nsis/: Makefile.nmake wireshark.nsi /trunk/plugins/: Ma

2009-02-22 Thread Ulf Lamping
j...@wireshark.org schrieb: > http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=27500 > > User: jake > Date: 2009/02/22 02:05 AM > > Log: > Incorporate plugin dissector into build in collection. > > Directory: /trunk/epan/dissectors/ > ChangesPath Action > +

[Wireshark-dev] News from the msvcr dll hell ... and a possible solution!

2009-02-15 Thread Ulf Lamping
Hi! On a computer without any Visual Studio version installed I tested my private Wireshark build compiled with Visual Studio 2005 Express Edition and with it's own installer. As usual, this installer will call the vcredist_x86.exe, so it installs the msvcr80.dll for the 2005 studio. However,

Re: [Wireshark-dev] [GeoIP] New map of IP locations

2009-02-15 Thread Ulf Lamping
Guy Harris schrieb: > On Feb 15, 2009, at 2:26 AM, Ulf Lamping wrote: > >> 2) The file ipmap.html will be copied from the program(data?) to the >> temp folder. > > Why make the copy? The ipmap.txt file is generated, so it can't be put into the (read-only) pro

Re: [Wireshark-dev] [Wireshark-commits] rev 27437: /trunk/gtk/ /trunk/gtk/: capture_if_dlg.c

2009-02-11 Thread Ulf Lamping
g...@wireshark.org schrieb: > http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=27437 > > User: guy > Date: 2009/02/11 05:48 PM > > Log: > Use network_virtual_16.xpm for VMware interfaces on OS X (well, use them > if VMware Fusion ever lets you capture on them, which it currently

Re: [Wireshark-dev] [Wireshark-commits] rev 27411: /trunk/gtk/ /trunk/gtk/: main_menu.c

2009-02-10 Thread Ulf Lamping
Sake Blok schrieb: > On Tue, Feb 10, 2009 at 09:22:27PM +, u...@wireshark.org wrote: >> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=27411 >> >> User: ulfl >> Date: 2009/02/10 01:22 PM >> > [...] >> >> add/change accelerator keys: >> "Time Display Format" 1 - 6 > > Hmmm

[Wireshark-dev] buildbot problem with asn1/charging_ase

2009-02-09 Thread Ulf Lamping
Hi! Recent changes in asn1 causes the buildbot some trouble with the automake stuff. Could someone with more knowledge than me have a look? Regards, ULFL ___ Sent via:Wireshark-dev mailing list Archives:http://www.

Re: [Wireshark-dev] wireshark web site

2009-02-08 Thread Ulf Lamping
Andrew Hood schrieb: > 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. FF3 on XP seems ok. Although the display of the menu if really too slow now. > > Some Interne

Re: [Wireshark-dev] Help

2009-02-06 Thread Ulf Lamping
Maizza Falah schrieb: > I'm using Fedora 8, on a i386. > I downloaded the rpm of wireshark. > Then, as root, put, in a terminal, the command: > > rpm -ivh wireshark-jgroups-1.0.3-1.fc8.i386.rpm > > It didn't show any error. > But when I put the command: > > wireshark > > It says: > > bash: wi

Re: [Wireshark-dev] After latitude/longitude - construct a URL that takes you to a map?

2009-02-03 Thread Ulf Lamping
Guy Harris schrieb: > On Feb 3, 2009, at 5:03 PM, u...@wireshark.org wrote: > >> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=27365 >> >> User: ulfl >> Date: 2009/02/03 05:03 PM >> >> Log: >> add display of GeoIP latitude/longitude > > And now for our next trick? > > ht

Re: [Wireshark-dev] text output from command line

2009-02-03 Thread Ulf Lamping
atdev.quer...@wipro.com schrieb: > Hi all, > > You all know after loading a packet we could have the information of the > loaded packets in text format (menu->export->as plain text file->xxx). > Can we do the same from the command line? > > Is that possible? > Is it possible to use the user M

Re: [Wireshark-dev] Issue loading a new plugin

2009-02-02 Thread Ulf Lamping
Jaap Keuter schrieb: > Hi, > > Since this comes up more and more often is someone able to: > 1. Write a patch for the plugin makefiles, or > 2. Write a chapter in the developer manual, or > 3. Write something on an apropriate Wiki page. > This in order of preference. > Is: 0. Fix it in the subv

Re: [Wireshark-dev] Open Watcom C compiler ?

2009-02-02 Thread Ulf Lamping
Gerald Combs schrieb: > Kukosa, Tomas wrote: >> Hi, >> >> does it make sence to have Wireshark compileable for Windows platform >> with Watcom C? (http://openwatcom.org) >> What is your opinion? >> >> Is there here any active user of this compiler? > > Is the Watcom C library GPL-compatible? C

[Wireshark-dev] Windows: Specific icons for capture interfaces (using a name heuristic)

2009-01-30 Thread Ulf Lamping
Hi! Another patch I had lying around for months ... The following will only have an effect on Windows based systems (I know to little about Unix systems to do it right here) ... If you have more than one or two capture interfaces (especially with the usually long capture interface names on W

Re: [Wireshark-dev] New toplevel Telephone menu item

2009-01-30 Thread Ulf Lamping
Jaap Keuter schrieb: > Hi, > > Well that was easy: > grep 'everything with telephone icon' | xargs mv menu/Telephony > ;) No, even easier: There was already a menu group telephony, I only needed to put this into a seperate menu ;-) > I'm oke with this idea, but would suggest to call it 'Telecom

Re: [Wireshark-dev] New toplevel Telephone menu item

2009-01-30 Thread Ulf Lamping
Michael Tüxen schrieb: > That sound like an excellent idea... Hmmm, I'm not that sure. > > On Jan 29, 2009, at 10:16 AM, Guy Harris wrote: > >> On Jan 29, 2009, at 12:27 AM, Michael Tüxen wrote: >> >>> I like the idea, but I do not think that the SCTP related items >>> should >>> be moved ther

Re: [Wireshark-dev] MSVC variant problem in v1.0.5

2009-01-30 Thread Ulf Lamping
gogr...@wi.rr.com schrieb: > Darn. So does this mean that when the ABI changes, I will have to compile the > plugin with the new source? Yes and no, see below. > Also, what is ABI? Application Binary Interface This is the interface provided by Wireshark to the plugins. Some background This A

[Wireshark-dev] New toplevel Telephone menu item

2009-01-28 Thread Ulf Lamping
Hi! There was a patch lingering around on my hard drive for months, so I thought: "commit it and let's see what people think". Motivation: very long toplevel menus are hard to handle. They are hard to "scan", hard to remember and hard to work with (e.g. the longer the menu get's, it's harder

Re: [Wireshark-dev] Issue loading a new plugin

2009-01-28 Thread Ulf Lamping
Heude Pascal schrieb: > Hello Jim, > > Do you try to build the whole wireshark or only to build your dll ? > I had this problem on some windows version and I solved it by building > the whole wireshark. But I still do not know why ! > > Pascal > > James Gallogly a écrit : >> I am trying to deve

Re: [Wireshark-dev] [Wireshark-bugs] [Bug 3115] Wireshark on Windows Server 2008 - not in the docs

2008-12-12 Thread Ulf Lamping
bugzilla-dae...@wireshark.org schrieb: > https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3115 > > --- Comment #5 from Gerald Combs 2008-12-12 17:02:57 > PDT --- > (In reply to comment #4) >> It looks like they were both generated from the web site, but now differ by >> one >> line. The web

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

2008-12-12 Thread Ulf Lamping
Gerald Combs schrieb: > June is so very far away and there are a ton of cool new features in the > trunk. > Do we really have to wait that long? :) Well, if we are in a hurry, we might be able to have a christmas release - SCNR ;-) > > If I copy /trunk to /trunk-1.2 around March or April, that

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

2008-12-10 Thread Ulf Lamping
Gerald Combs schrieb: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I'm proud to announce the release of Wireshark 1.0.5. > Hi Gerald! Good news :-) Any ideas, when you want to make the current dev 1.1.x the new release branch (aka 1.2.0)? Probably next Sharkfest? Regards, ULFL _

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

2008-12-09 Thread Ulf Lamping
[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. > Sh..! Sorry for any inconvenie

Re: [Wireshark-dev] How to share enhanced plugin

2008-12-02 Thread Ulf Lamping
Jaap Keuter schrieb: > Hi, > > I always wondered why this isn't included in the Windows build scripts. Can > anyone shed some light on that? > Hi! Simply I got no trouble with it and noone else cared about it? ;-) Regards, ULFL ___ Wireshark-dev mai

Re: [Wireshark-dev] PCAP File Question

2008-12-02 Thread Ulf Lamping
Barry Constantine schrieb: > Hello, > > > > My company builds hardware based network analyzers and we are going to > capture 1G/10G line rate and store in native pcap format. > > > > If possible, it would be beneficial for us to store some extra > information in the packet headers that is

Re: [Wireshark-dev] heuristic Dissector for Dummies

2008-09-09 Thread Ulf Lamping
Maynard, Chris schrieb: > Nice job Ulf. Thanks! > Attached is a small patch with minor formatting changes > and a few XXX's filled in with some additional information. Applied as SVN 26170 - thanks :-) > > I do have one more question/thought about heuristic dissectors as it > pertains to TCP he

Re: [Wireshark-dev] heuristic Dissector for Dummies

2008-09-06 Thread Ulf Lamping
Maynard, Chris schrieb: > I think this information would best be placed in the doc/ directory, > either residing in its own README.heuristic file (with a mention of it > from README.developer) or residing directly in README.developer itself, > under its own section. Wherever it lives, I think it w

Re: [Wireshark-dev] trunk vs trunk-1.0

2008-09-04 Thread Ulf Lamping
Brown, Mark C (WTEC) schrieb: > How/when do changes to the development branch get merged into the stable > branch? Is there a specific process? I submitted some simple changes back > in April (bug 2451/SVN 24926) that I'd love to see in the stable branch... > Hi Mark! The development vs. sta

Re: [Wireshark-dev] heuristic Dissector for Dummies

2008-08-29 Thread Ulf Lamping
Peter Johansson schrieb: > Nicely put Ulf! This information is certainly a candidate for addition > to the Wireshark Wiki. > Thanks! While writing it, I was having in mind to put it into the sources doc dir. As it turns out, this info might also be of general interest for the common WS user

Re: [Wireshark-dev] heuristic Dissector for Dummies

2008-08-29 Thread Ulf Lamping
Tom Stevens schrieb: > Hello! > > Is there a simple tutorial on the web where i can find some information > about how to write a heuristic dissector. > > http://www.wireshark.org/docs/wsdg_html_chunked/ChapterDissection.html > -> On this side i couldn't find anything about heuristic dissectors.

Re: [Wireshark-dev] Lint of packet-tcp.c

2008-08-21 Thread Ulf Lamping
Maynard, Chris schrieb: > I've been using Gimpel's PC-Lint for a long time and really like it a > lot. It's a commercial product but it's pretty cheap for a single seat > license at $239: http://www.gimpel.com/. PC-Lint runs on Windows, but > their Flexelint product runs on *nix's. > > Splint is

Re: [Wireshark-dev] First time compiling with VS2008EE

2008-08-06 Thread Ulf Lamping
Maynard, Chris schrieb: > When I ran wireshark to test it, one thing I noticed that I hadn't > before is that when I did a File -> Open, then dragged the dialog window > across the main page, the main page was corrupted with window edges of > the dragged FileOpen dialog. I don't recall that happen

Re: [Wireshark-dev] VALS macro causing Wireshark to crash on Windows

2008-08-06 Thread Ulf Lamping
Chih Wang schrieb: > Hi all, > > I have a custom dissector in plugin form originally developed on Linux > (Ubuntu on x86). Wireshark ran fine on the system with the plugin. > > The code was moved to a Windows XP box verbatim. After setting up the > build environment on the box, I was able to bui

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

2008-08-05 Thread Ulf Lamping
Sake Blok schrieb: > On Tue, Aug 05, 2008 at 02:22:58PM +0200, Paolo Abeni wrote: >> hello, >> >> In a pending patch for the SSL dissector: >> >> https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2725 >> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=2029 >> >> it's implemented the attac

Re: [Wireshark-dev] Getting rid of proto_tree_add_*_hidden()

2008-07-23 Thread Ulf Lamping
Jeff Morriss schrieb: > I ran checkAPIs on the dissectors today and was amazed at how few > warnings came out. :-) > > One of the things I noticed was there were no warnings about dissectors > using the proto_tree_add_*_hidden() functions. I just cleaned up a > couple spots the tool missed and

Re: [Wireshark-dev] What's the versions of GTK and GLib we're expecting as a minimum?

2008-05-20 Thread Ulf Lamping
Stephen Fisher schrieb: > On Wed, May 21, 2008 at 12:29:50AM +0200, Ulf Lamping wrote: > >> What's the current version we require for the developer (latest) >> trunk: >> > On Unix, the configure script enforces the following minimum version > numbers: &

[Wireshark-dev] What's the versions of GTK and GLib we're expecting as a minimum?

2008-05-20 Thread Ulf Lamping
Hi! Being "on the road" the last two weeks, I'm a bit out of sync with current WS development ;-) What's the current version we require for the developer (latest) trunk: GTK: 2.4? GLib: ? Regards, ULFL ___ Wireshark-dev mailing list Wireshark-dev@wi

Re: [Wireshark-dev] Problem (and fix?) building pdfs from docbook

2008-05-20 Thread Ulf Lamping
Jaap Keuter schrieb: > Hi, > > Changing "fop.extensions" to "fop1.extensions" just addresses a non-existing > object. That is the same as removing it or commenting out, as you did. You > can > just set it to "0", as the comment says "FOP 0.93 doesn't handle them, yet". > Neither does 0.94, so i

Re: [Wireshark-dev] Requiring GTK+ 2.4 or later

2008-05-19 Thread Ulf Lamping
Guy Harris schrieb: > Jeff Morriss wrote: > >> packaging/svr4/checkinstall.in also uses the GTK version for >> install-time dependency checking but I can't seem to figure out how to >> get a variable in configure.in to populate that file when it builds the >> real file. >> >> (OTOH it would b

Re: [Wireshark-dev] Problem (and fix?) building pdfs from docbook

2008-05-19 Thread Ulf Lamping
Joerg Mayer schrieb: > I'm running opensuse-factory with fop-0.94. > When trying to build the documentation, it failed. After making the follwing > change I could build the docs again: > > Index: custom_layer_pdf.xsl > === > --- custom

Re: [Wireshark-dev] Compiling with VS-2005

2008-05-09 Thread Ulf Lamping
Maynard, Chris schrieb: > Would installing the redistributable package from Microsoft on the other > machines resolve Barry's problem? > > http://www.microsoft.com/downloads/details.aspx?FamilyId=32BC1BEE-A3F9-4 > C13-9C99-220B62A191EE&displaylang=en > I would expect No. The redistributable pac

Re: [Wireshark-dev] Should we support GTK+ 2.0[.x] and 2.2[.x], or just 2.4 and later?

2008-04-20 Thread Ulf Lamping
Guy Harris schrieb: > The SVN trunk of Wireshark has had the GTK+ 1.2[.x]/GLib 1.2[.x] support > removed. There's still code in there that checks for GTK+ releases > prior to 2.4; however: > > 1) I checked in a fix to the configure script and to gtk/file_dlg.c > that prevented Wireshark f

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-20 Thread Ulf Lamping
Joerg Mayer schrieb: > On Thu, Apr 17, 2008 at 10:20:31PM -0600, Stephen Fisher wrote: > >>> The Widget settings I've chosen are for a min. resolution of 1024*768, >>> before scrollbars appear (well, slightly less about 1000*700 or so, so >>> there's some space left for things like a startmenu

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-19 Thread Ulf Lamping
Stig Bjørlykke schrieb: > When starting a capture with a file loaded, or restarting a running > capture, we always get the welcome page in a split second after the > current file is closed and before the new capture starts. > > Maybe we should have the old empty page in this situations? > We

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-19 Thread Ulf Lamping
Ulf Lamping schrieb: > Jim Young schrieb: > >> Attached patch (to SVN 25119) stops these particular >> messages during startup of Wireshark on my system. >> >> In my case it's the first call to gtk/main_welcome.c's >> main_welcome_reset_rece

Re: [Wireshark-dev] [Wireshark-commits] rev 25011: /trunk/gtk/ /trunk/gtk/: main_menu.c

2008-04-19 Thread Ulf Lamping
[EMAIL PROTECTED] schrieb: > http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=25011 > > User: tuexen > Date: 2008/04/14 01:51 AM > > Log: > #ifdef HAVE_LUA_5_1 the handling of REGISTER_TOOLS_GROUP_NONE > > Does this make a lot of sense, as the Tools top menu is now permanently

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-19 Thread Ulf Lamping
Stig Bjørlykke schrieb: > On 19. april. 2008, at 15.39, Ulf Lamping wrote: > >> Huh, that was a real though one - I spend several days on it now, but >> still no optimal solution! >> > My list of recent files is empty after this update, and I get this new >

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-19 Thread Ulf Lamping
Jim Young schrieb: > Attached patch (to SVN 25119) stops these particular > messages during startup of Wireshark on my system. > > In my case it's the first call to gtk/main_welcome.c's > main_welcome_reset_recent_capture_files() that triggers > the error messages. Specifically it's the call to

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-19 Thread Ulf Lamping
Gerald Combs schrieb: > Ulf Lamping wrote: > >> However, a basic news panel *might* be useful. Problem here: for example >> you won't get freshly developed features if you are using the WS release >> versions. I currently don't see a good way to handle thes

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-19 Thread Ulf Lamping
Stig Bjørlykke schrieb: > On 19. april. 2008, at 15.39, Ulf Lamping wrote: > > >> Huh, that was a real though one - I spend several days on it now, but >> still no optimal solution! >> > > My list of recent files is empty after this update, and I get this

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-19 Thread Ulf Lamping
Gerald Combs schrieb: > Ulf Lamping wrote: > > >> I would be interested in feedback: >> - was the page intuitive right from the start or was something really >> confusing? >> - something missing / should be added? >> - should something really be removed?

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-19 Thread Ulf Lamping
Michael Tüxen schrieb: > Dear all, > > actually I think that > - all entries in 'Capture Help' should be moved to 'Online'. > - 'Capture Help' can be removed. > - 'Sample Captures' should be moved to 'Online'. > > This would result in three columns: > * Capture > * Files > * Onine > > For me this w

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-19 Thread Ulf Lamping
Michael Tüxen schrieb: > and what I missed: > > Put 'Capture Options' on top of 'Interface List' like > 'Open' is on top of the recent file list. IMHO 'Capture Options' is a really cluttered and hard to understand dialog - which provides options that most users just don't need. I hesitate to put

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-19 Thread Ulf Lamping
Graeme Lunt schrieb: >> No, that's what the about dialog is for. I want to avoid too much >> information on that page, because it will get more and more confusing >> and less informative. >> > I think it is useful to have this information on the front page as > most users will never actually g

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-18 Thread Ulf Lamping
Thomas Anders schrieb: > Ulf Lamping wrote: > >> I've just finished the initial version of a Wireshark welcome page. >> > > I agree it's an excellent idea. > > >> Files: Open a file >> > > Isn't the term "Ope

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-17 Thread Ulf Lamping
Stephen Fisher schrieb: > On Thu, Apr 17, 2008 at 03:21:37AM +0200, Ulf Lamping wrote >> I've just finished the initial version of a Wireshark welcome page. >> >> That welcome page is shown when no capture file is loaded - well, >> you'll immediately see it ju

Re: [Wireshark-dev] [Wireshark-commits] rev 25072: /trunk/gtk/ /trunk/gtk/: dlg_utils.c export_object.c stock_icons.c stock_icons.h

2008-04-17 Thread Ulf Lamping
Stephen Fisher schrieb: > On Wed, Apr 16, 2008 at 08:47:20AM +, [EMAIL PROTECTED] wrote: > > >> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=25072 >> >> User: ulfl >> Date: 2008/04/16 08:47 AM >> >> Log: >> add "Save As" and "Save All" buttons to the dialog / stock_icons

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-17 Thread Ulf Lamping
Michael Tüxen schrieb: > Hi Ulf, > > I really like it. And I think it should have a clean not overload > design. Like it is now. > > One comment from me: > > There is a column 'Online' which I would then expect to contain > all contents which is online. But this is not true... There are > links to

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-17 Thread Ulf Lamping
Stig Bjørlykke schrieb: > Just some small comments: > > - Hiding an interface in the interface options does not update the > interface list in the welcome page. > Sounds reasonable. I'll implement it - remind me in a week or so, in case I'll forget about to do it. > - When having a lot of inter

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-17 Thread Ulf Lamping
Joerg Mayer schrieb: > On Thu, Apr 17, 2008 at 10:29:14AM +0200, Ulf Lamping wrote: > >> Is this the behaviour that you see? Than it's a bug. >> >> The list of interfaces is build by asking dumpcap about the interface >> list (which should have the privileg

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-17 Thread Ulf Lamping
Stig Bjørlykke schrieb: > 2008/4/17, Ulf Lamping <[EMAIL PROTECTED]>: > >> What I did is to "gray out" items that are currently not available, >> which makes much more sense to me. >> > > But it is possible to select them, and a warnin

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-17 Thread Ulf Lamping
Graeme Lunt schrieb: > Brilliant! > Thanks! > One suggestion - how about including the version information > (including a build date)? > No, that's what the about dialog is for. I want to avoid too much information on that page, because it will get more and more confusing and less informati

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-17 Thread Ulf Lamping
Jaap Keuter schrieb: > Hi Ulf, > > I like it, it's clean, simple, uncluttered. Lets see that we can keep it that > way gentlemen. > Ack > On the tip of the day: as long as it doesn't required a mouse click to get > rid > of it I'm oke with it. It would be another section in the right hand col

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-17 Thread Ulf Lamping
Joerg Mayer schrieb: > I'm not talking about removing it from the recently-used list but just > to not display it on the welcome page. > I guess not displaying it on the list would be confusing to users "why is it gone now?". What I did is to "gray out" items that are currently not available,

Re: [Wireshark-dev] [Wireshark-commits] rev 25062: /trunk/gtk/ /trunk/gtk/: dlg_utils.c

2008-04-17 Thread Ulf Lamping
Stig Bjørlykke schrieb: > 2008/4/16, Ulf Lamping <[EMAIL PROTECTED]>: > >> P.S: There's also some strange words in your button labels "Hjelp", but >> there's not a lot I can do about it ;-))) >> > Is it possible to disable locale in w

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-17 Thread Ulf Lamping
Guy Harris schrieb: > Stig Bjørlykke wrote: > >> On startup I get this warning: >> (wireshark:26750): Gtk-CRITICAL **: gtk_container_foreach: assertion >> `GTK_IS_CONTAINER (container)' failed >> > That appears to be happening in the gtk_container_foreach() call in > clear_menu_recent_capt

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-17 Thread Ulf Lamping
Joerg Mayer schrieb: > One thing about the capture sections: In case I start wireshark without > capture privileges this should be displayed instead of providing an empty > list of capture interfaces. > Is this the behaviour that you see? Than it's a bug. The list of interfaces is build by aski

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-17 Thread Ulf Lamping
Jaap Keuter schrieb: > Hi, > > Carefull here. You suggest to prune the list if captures aren't found. What > happens when captures are on a network share you forgot to mount? Or even more likely, your Notebook is simply not connected to the/any network :-) > Then your > list would be gone, whil

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-16 Thread Ulf Lamping
Guy Harris schrieb: > On Apr 16, 2008, at 7:10 PM, Maynard, Chris wrote: > >> Hi Ulf, >> >> I like it. I always thought the blank gray screen at startup was >> somewhat plain and boring. We've got all the real estate to do >> something with, why not put it to good use? >> > Yes - the

Re: [Wireshark-dev] New Wireshark welcome page!

2008-04-16 Thread Ulf Lamping
Maynard, Chris schrieb: > Hi Ulf, > > I like it. I always thought the blank gray screen at startup was > somewhat plain and boring. We've got all the real estate to do > something with, why not put it to good use? > > Somewhat related to this - I was thinking about proposing a "Wireshark >

[Wireshark-dev] New Wireshark welcome page!

2008-04-16 Thread Ulf Lamping
Hi! I've just finished the initial version of a Wireshark welcome page. That welcome page is shown when no capture file is loaded - well, you'll immediately see it just when you start Wireshark (SVN25083 or later). It contains stuff that should be useful to start work with Wireshark (both hel

Re: [Wireshark-dev] [Wireshark-commits] rev 25062: /trunk/gtk/ /trunk/gtk/: dlg_utils.c

2008-04-16 Thread Ulf Lamping
Stig Bjørlykke schrieb: > 2008/4/16, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: > >> special handling for the dialog boxes Copy buttons, as the behaviour is >> more like an auxiliary button (like Help), than one of the "action" buttons >> as "Ok" (as e.g. Ok will close the dialog). >> >> To ma

  1   2   3   4   5   6   7   >