[Wireshark-dev] Wireshark 1.6.5 is now available

2012-01-10 Thread Gerald Combs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm proud to announce the release of Wireshark 1.6.5. What is Wireshark? Wireshark is the world's most popular network protocol analyzer. It is used for troubleshooting, analysis, development and education. What's New Bug Fixes The f

[Wireshark-dev] Wireshark 1.4.11 is now available

2012-01-10 Thread Gerald Combs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm proud to announce the release of Wireshark 1.4.11. What is Wireshark? Wireshark is the world's most popular network protocol analyzer. It is used for troubleshooting, analysis, development and education. What's New Bug Fixes The

Re: [Wireshark-dev] Wireshark ABI stability 1.6.4 -> 1.6.5

2012-01-10 Thread Gerald Combs
On 1/10/12 2:09 PM, Balint Reczey wrote: > diff --git a/debian/wireshark-common.files b/debian/wireshark-common.files > index 41341be..4403c04 100644 > --- a/debian/wireshark-common.files > +++ b/debian/wireshark-common.files > @@ -5,7 +5,7 @@ > /usr/bin/text2pcap > /usr/bin/rawshark > /usr/lib

Re: [Wireshark-dev] Wireshark ABI stability 1.6.4 -> 1.6.5

2012-01-10 Thread Balint Reczey
Hi Gerald, On 01/09/2012 11:44 PM, Gerald Combs wrote: On 1/9/12 1:39 PM, Balint Reczey wrote: Hi Gerald, On 01/09/2012 07:56 PM, Gerald Combs wrote: The ABI change is the result of fixing a bug. If we revert the change the ZigBee ZCL dissector will revert back to its previous broken behavi

Re: [Wireshark-dev] Wireshark ABI stability 1.6.4 -> 1.6.5

2012-01-10 Thread Gerald Combs
On 1/10/12 10:53 AM, Balint Reczey wrote: > I meant the proper change in the library version would be bumping the > major version for the #define change since the ABI is not backward > compatible. > There would be an alternate way, redefining the constants in the C file > in the backported fix. > T

Re: [Wireshark-dev] Win32 build

2012-01-10 Thread Bill Meier
On 1/10/2012 3:02 PM, Bill Meier wrote: On 1/10/2012 2:47 PM, Andriy Beregovenko wrote: Hi, I'm write a custom dissector, and it works fine... under Linux, but not under Windows. Thus I have a problem to run wireshark under Windows as well as debug problem. So, I built wireshark stable version

Re: [Wireshark-dev] Win32 build

2012-01-10 Thread Bill Meier
On 1/10/2012 2:47 PM, Andriy Beregovenko wrote: Hi, I'm write a custom dissector, and it works fine... under Linux, but not under Windows. Thus I have a problem to run wireshark under Windows as well as debug problem. So, I built wireshark stable version 1.6.4 and 1.4.10 using manual [0]. Of c

[Wireshark-dev] Win32 build

2012-01-10 Thread Andriy Beregovenko
Hi, I'm write a custom dissector, and it works fine... under Linux, but not under Windows. Thus I have a problem to run wireshark under Windows as well as debug problem. So, I built wireshark stable version 1.6.4 and 1.4.10 using manual [0]. Of course, I add my file to nmake make files/rules and

Re: [Wireshark-dev] Wireshark ABI stability 1.6.4 -> 1.6.5

2012-01-10 Thread Balint Reczey
Hi Gerald, On 01/09/2012 11:44 PM, Gerald Combs wrote: On 1/9/12 1:39 PM, Balint Reczey wrote: Hi Gerald, On 01/09/2012 07:56 PM, Gerald Combs wrote: The ABI change is the result of fixing a bug. If we revert the change the ZigBee ZCL dissector will revert back to its previous broken behavi

Re: [Wireshark-dev] capture from multiple interfaces / dumpcap usage alert in wireshark 1.7.0

2012-01-10 Thread Michael Tuexen
On Jan 10, 2012, at 8:31 AM, vijay wrote: > Hi, > > I need to capture from multiple interfaces simultaneously. Wireshark captures > from a pipe and eth1 separately but when i try them > togather using wireshark -k -i /tmp/pipe -i eth1 it displays some dumpcap > usage error. > > unknown messa