Re: [Wireshark-dev] Eliminate annoying color filter dialog

2011-03-09 Thread Jaap Keuter
On 03/08/2011 10:14 PM, Anders Broman wrote: Chris Maynard skrev 2011-03-08 21:02: I regularly switch between a custom build of Wireshark for analyzing my company's protocols and the trunk when doing general Wireshark development/testing. Unfortunately, I have lots of custom color filters in pla

[Wireshark-dev] Any suggestions for using wireshark to capture/display interactions over netlink?

2011-03-09 Thread Sam Roberts
netlink is a linux IPC mechanism commonly used for complex interactions between userspace and the linux kernel. The API uses socket() with a PF_NETLINK, and sendfrom/recvfrom. Since it's IPC, there is no ethX device to pcap - I'm wondering if anybody knows of ways to watch netlink traffic? I coul

Re: [Wireshark-dev] Eliminate annoying color filter dialog

2011-03-09 Thread Jeff Morriss
Chris Maynard wrote: Well, that's essentially what we've got. The warning would now be printed in the console window, assuming the user has configured his preferences such that "Open a console window" is not set to "Never". Of course, this is currently a "Windows-only" preference, but is there

Re: [Wireshark-dev] Eliminate annoying color filter dialog

2011-03-09 Thread Chris Maynard
Stig Bjørlykke writes: > I think this sort of warnings are important to an user trying to > configure the installed version of Wireshark (which usually is only > one) with some custom configurations, because he/she may not be able > to spot an error if not given a warning. They are less importan

Re: [Wireshark-dev] Different wireshark behaviour on Linux as on Windows

2011-03-09 Thread Guy Harris
On Mar 9, 2011, at 10:34 AM, Roland Knall wrote: > I agree, but the current situation, where the selection seems to > happen purely by chance is also not ideal. The *ideal* situation would be one wherein registering more than one dissector for a given type value would be an error, and other, be

Re: [Wireshark-dev] Different wireshark behaviour on Linux as on Windows

2011-03-09 Thread Roland Knall
On Wed, Mar 9, 2011 at 7:04 PM, Guy Harris wrote: > > On Mar 9, 2011, at 7:39 AM, Roland Knall wrote: > >> It would definitly not solve the underlying problem. but at least it >> would make the whole process predictable, which is definitly not the >> case now. > > That might or might not constitut

Re: [Wireshark-dev] Different wireshark behaviour on Linux as on Windows

2011-03-09 Thread Guy Harris
On Mar 9, 2011, at 7:39 AM, Roland Knall wrote: > It would definitly not solve the underlying problem. but at least it > would make the whole process predictable, which is definitly not the > case now. That might or might not constitute an improvement; the file name given to a plugin, or whethe

Re: [Wireshark-dev] Different wireshark behaviour on Linux as on Windows

2011-03-09 Thread Roland Knall
On Wed, Mar 9, 2011 at 4:14 PM, Chris Maynard wrote: > Roland Knall writes: > >> On Linux, when the gtk-based filehandler loads the list of plugins, it >> does so alphabetically. This does not seem to be the case on Windows. >> So here, someone might argue, that this indeed is plattform-specific,

Re: [Wireshark-dev] Different wireshark behaviour on Linux as on Windows

2011-03-09 Thread Chris Maynard
Roland Knall writes: > On Linux, when the gtk-based filehandler loads the list of plugins, it > does so alphabetically. This does not seem to be the case on Windows. > So here, someone might argue, that this indeed is plattform-specific, > and not exactly a bug. You would have to sort the plugin

Re: [Wireshark-dev] [Wireshark-commits] rev 36170: / /trunk/epan/dissectors/: packet-mndp.c /trunk/epan/: CMakeLists.txt

2011-03-09 Thread Stig Bjørlykke
On Tue, Mar 8, 2011 at 8:10 PM, wrote: > Log: >  Add support for Mikrotiks Neigbor Discovery Protocol (MNDP). >  Sample capture at >  http://wiki.wireshark.org/SampleCaptures?action=AttachFile&do=get&target=mndp.pcap Did you want to add this to epan/dissectors/Makefile.common? I tried, but I ge

Re: [Wireshark-dev] Eliminate annoying color filter dialog

2011-03-09 Thread Stig Bjørlykke
On Tue, Mar 8, 2011 at 9:02 PM, Chris Maynard wrote: > I regularly switch between a custom build of Wireshark for analyzing my > company's protocols and the trunk when doing general Wireshark > development/testing.  Unfortunately, I have lots of custom color filters in > place that are invalid for