Re: [Wireshark-dev] Regarding Interface

2009-06-02 Thread Guy Harris
On Jun 1, 2009, at 10:54 PM, tulip neo wrote: May be this n't a vallid question but keeps wondering me.over which interface the following is possible. What do you mean by interface? If you're referring to the network hardware, that's possible over *any* interface for a network type that

Re: [Wireshark-dev] Wireshark can't read PcapNG file

2009-06-02 Thread SOLTANI FATEN
Hello, In this link below, are many are some example PcapNG files http://wiki.wireshark.org/Development/PcapNg I tried to open its by Wireshark, But it posts an empty window! I don't understand why; someone have any idea! Regards Faten

[Wireshark-dev] Modifying port number for TFTP

2009-06-02 Thread yvanmmailbox-web
Hi all, I need to dissect frames that use tftp protocol but not on the standard port. Is it possible to modify it without compiling the whole Wireshark or re-writing a plugin with the same code (I don't want to have a compiled-specific version of Wireshark)? Why are the port numbers of all

Re: [Wireshark-dev] Modifying port number for TFTP

2009-06-02 Thread Stig Bjørlykke
On Tue, Jun 2, 2009 at 9:49 AM, yvanmmailbox-...@yahoo.fr wrote: I need to dissect frames that use tftp protocol but not on the standard port. Is it possible to modify it without compiling the whole Wireshark or re-writing a plugin with the same code (I don't want to have a compiled-specific

Re: [Wireshark-dev] Ubuntu buildbot error

2009-06-02 Thread Stig Bjørlykke
On Tue, Jun 2, 2009 at 6:07 AM, Ravi Kondamuru ravikondam...@gmail.com wrote: The compilation on ubuntu-7.10-x86-64 seems to be completing without warnings now. But it seems to be continuously failing at fuzz-menagerie. This is because nstrace_open() (really nspm_signature_version()) is looping

[Wireshark-dev] how recognise a udp packet data part is sip packet?

2009-06-02 Thread zhangchuangde
hi, as the define in packet-sip.c #define TCP_PORT_SIP 5060 #define UDP_PORT_SIP 5060 #define TLS_PORT_SIP 5061 I know when a tcp/udp/tls packet's port is 5060/5061, the protocol analyzer will dissect it into sip protocol. however, as the first packet in the accessory, its src port is

[Wireshark-dev] PING: sync expert_tapdata_t structs

2009-06-02 Thread Jakub Zawadzki
Hi, In wireshark there are two expert_tapdata_t, one defined in expert_comp_table.h, second in expert_dlg.c. There're some memory issues nicely described in https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2504#c3 (with quickdirty patch) Could someone look at it? Cheers.

[Wireshark-dev] Help decrypting 802.1x PEAP Traffic

2009-06-02 Thread Harsha gowda
Hi, Please Help me Decrypting 802.1x Traffic. I have a private key of the radius server. Can any one help me derive the keys. I know EAP-TLS session is created then The user identity is sent and exchange Client random and Access Point Random. Bu my question is How can i decrypt the TLS traffic ?

[Wireshark-dev] dissect proprietary hdlc based protocol from SLL

2009-06-02 Thread Weberhofer, Daniel
Hi all, I need to dissect a proprietary hdlc based protocol. With tcpdump I get the packets as SLL (Linux cooked capture) cap file. I've written a lua dissector based on http://thomasfischer.biz/?p=175 - but I can't get a dissector table for SSL: my_table = DissectorTable.get(sll)

[Wireshark-dev] 答复: how recognise a udp packet data part is sip packet?

2009-06-02 Thread 董明
Hi,chuangde: Let’s read the code together: packet-udp.c: decode_udp_ports(tvbuff_t *tvb, int offset, packet_info *pinfo, proto_tree *tree, int uh_sport, int uh_dport, int uh_ulen) { /*First, try to dissector udp data by udp-port*/ if (low_port != 0

Re: [Wireshark-dev] Linking wireshark.exe --- Error

2009-06-02 Thread Leonardo
Hi Guy, perfect!!! you have resolve my problem! you are awesome! For a simple the linker crashed. i could think that was a special character for the script! However, thanks,thanks,thanks a lot!! 2009/5/31 Guy Harris g...@alum.mit.edu On May 31, 2009, at 12:14 PM, Anders

[Wireshark-dev] 答复: Regarding Interface

2009-06-02 Thread 董明
Hi, It should be impossible to send packet in the two stacks on one logic network interface. But the following scenario meets your capture log, capture packets from two interfaces in the same communication path, (use a Ethernet switch, which support mirror) : start a SIP service from UE

Re: [Wireshark-dev] Ubuntu buildbot error

2009-06-02 Thread Ravi Kondamuru
Stig, Can you provide the location or forward the file, reading which nstrace_open is going into a loop? I want to test it with a fix. thanks, Ravi. 2009/6/2 Stig Bjørlykke s...@bjorlykke.org On Tue, Jun 2, 2009 at 6:07 AM, Ravi Kondamuru ravikondam...@gmail.com wrote: The compilation on

Re: [Wireshark-dev] How do I know the wireshark version ?

2009-06-02 Thread wsgd
epan_get_version() is good enough for my needs. Thanks, Olivier Eloy Paris a écrit : On Mon, Jun 01, 2009 at 10:48:15PM +0200, wsgd wrote: Hello, From a plugin dissector, at execution time : How do I know the wireshark version ? epan_get_version() is not good enough for your

Re: [Wireshark-dev] How do I know the wireshark version FROM a plugin dissector AT execution time ?

2009-06-02 Thread wsgd
Guy Harris a écrit : On Jun 1, 2009, at 2:44 PM, wsgd wrote: There is an additional field into pinfo (1.1.z). And so, the following fields are not at the same place. We've never guaranteed that plugins will be binary-compatible between major versions - until 1.0, I don't think

[Wireshark-dev] buildbot failure in Wireshark (development) on Ubuntu-7.10-x86-64

2009-06-02 Thread buildbot-no-reply
The Buildbot has detected a new failure of Ubuntu-7.10-x86-64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Ubuntu-7.10-x86-64/builds/1079 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: ubuntu-7.10-x86

Re: [Wireshark-dev] Ubuntu buildbot error

2009-06-02 Thread Stig Bjørlykke
On 2. juni. 2009, at 17.48, Ravi Kondamuru wrote: Can you provide the location or forward the file, reading which nstrace_open is going into a loop? I want to test it with a fix. I have already provided a fix for this in revision 28585, and in later revisions improved some handling.

Re: [Wireshark-dev] Wireshark 1.2.0pre1 is now available

2009-06-02 Thread Maynard, Chris
I am experiencing another 1.2pre1 problem. When trying to create an rpm installer on Linux 2.6.18-8.el5 (RHEL5) x86_64 platform, I get the following fatal error while compiling the sources via make rpm-package that I don't get if I simply run make: gcc -DINET6 -D_U_=__attribute__((unused)) -g

[Wireshark-dev] 1.2.0 trunk doesn't build ?

2009-06-02 Thread Michael Lum
Is anyone successfully building the 1.2.0 trunk on Windows? (MSVC6) packet-memcache.c doesn't compile: cl -DWIN32 -DNULL=0 -D_MT -D_DLL -WX -DHAVE_CONFIG_H /I. /I.. /I../.. /I C:\wireshark-win32-libs-new\glib\include\glib-2.0 /IC:\wireshark-win32-libs-new \glib\lib\glib-2.0\include

Re: [Wireshark-dev] 1.2.0 trunk doesn't build ?

2009-06-02 Thread Maynard, Chris
Mike is: http://www.wireshark.org/lists/wireshark-dev/200905/msg00364.html -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev- boun...@wireshark.org] On Behalf Of Michael Lum Sent: Tuesday, June 02, 2009 2:57 PM To: Developer support list for Wireshark

Re: [Wireshark-dev] Modifying port number for TFTP

2009-06-02 Thread Heude Pascal
The main drawback of this method is that wireshark refreshes the trace window and this could take a while, depending on the trace size and on your PC power. I had the same request than Yvan, because I have a TFTP protocol based on port 59 (for call) and 50450-50460 ports for the rest of

Re: [Wireshark-dev] 1.2.0 trunk doesn't build ?

2009-06-02 Thread Michael Lum
That's fixed packet-memcache.c. Thanks -- Michael Lum Principal Software Engineer 4600 Jacombs Road +1.604.276.0055 Richmond, B.C. Canada V6V 3B1 Star Solutions -Original Message- From: wireshark-dev-boun...@wireshark.org

[Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-x86

2009-06-02 Thread buildbot-no-reply
The Buildbot has detected a new failure of OSX-10.5-x86 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/OSX-10.5-x86/builds/2568 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-x86 Build Reason:

Re: [Wireshark-dev] Wireshark can't read PcapNG file

2009-06-02 Thread Stephen Fisher
On Tue, Jun 02, 2009 at 09:21:48AM +0200, SOLTANI FATEN wrote: In this link below, are many are some example PcapNG files http://wiki.wireshark.org/Development/PcapNg I tried to open its by Wireshark, But it posts an empty window! I don't understand why; someone have any idea! What

Re: [Wireshark-dev] Modifying port number for TFTP

2009-06-02 Thread Stephen Fisher
On Tue, Jun 02, 2009 at 09:28:09PM +0200, Heude Pascal wrote: I had the same request than Yvan, because I have a TFTP protocol based on port 59 (for call) and 50450-50460 ports for the rest of protocol. What setup is TFTP going over port 59 in? I see that the official IANA designation for

Re: [Wireshark-dev] dissect proprietary hdlc based protocol from SLL

2009-06-02 Thread Stephen Fisher
On Tue, Jun 02, 2009 at 01:34:02PM +0200, Weberhofer, Daniel wrote: I need to dissect a proprietary hdlc based protocol. With tcpdump I get the packets as SLL (Linux cooked capture) cap file. - but I can't get a dissector table for SSL: my_table = DissectorTable.get(sll) sll is wrong:

[Wireshark-dev] buildbot failure in Wireshark (development) on Windows-XP-Win64

2009-06-02 Thread buildbot-no-reply
The Buildbot has detected a new failure of Windows-XP-Win64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Windows-XP-Win64/builds/643 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-xp-win64 Build