[Wireshark-dev] Problem building wireshark-1.2.0 (and wireshark-1.0.8) when trying to configure using --with-pcre

Hello, I try to build wireshark-1.0.8 and wireshark-1.2.0 on Red Hat Enterprise Linux ES release 4 (Nahant). It is important to me to have the libpcre library (for matches). So I ran ./configire --with-pcre=/usr/include/pcre but I get these errors (both under wireshark-1.0.8 and wireshark-1.2.0)

Re: [Wireshark-dev] Problem of packet-per.c on ASN.1 PER Encoding

Sorry for not including the Bug Number: 3733 --- On Wed, 7/15/09, Sean wrote: > From: Sean > Subject: Re: [Wireshark-dev] Problem of packet-per.c on ASN.1 PER Encoding > To: "Developer support list for Wireshark" > Date: Wednesday, July 15, 2009, 9:44 AM > > Additional information for this

Re: [Wireshark-dev] Problem of packet-per.c on ASN.1 PER Encoding

Additional information for this issue: Source code version: wireshark-1.2.0.tar.gz Build on Windows XP Pro with MSVC2008EE --- On Wed, 7/15/09, Sean wrote: > From: Sean > Subject: [Wireshark-dev] Problem of packet-per.c on ASN.1 PER Encoding > To: wireshark-dev@wireshark.org > Date: Wednes

[Wireshark-dev] Problem of packet-per.c on ASN.1 PER Encoding

Hi, We're using the LTE RRC dissector(packet-lte-rrc.c) recently and we find a problem while parsing the RRC Connection Request, Following is the definition of the RRC Connection Request: -- ASN1START RRCConnectionRequest ::=SEQUENCE { criticalExtensions

Re: [Wireshark-dev] Question to header fields and tvb

On Tue, Jul 14, 2009 at 11:09:01AM -0700, Guy Harris wrote: > Making the field FT_UINT32 - or FT_UINT64 if it's likely to have > values > 2^32-1, or FT_INT32 if it's signed, or FT_INT64 if it's > signed and likely to have values > 2^31-1 or < -2^31 - and using > proto_tree_add_uint() after fetc

Re: [Wireshark-dev] How to submit changes in wireshark?

On Jul 14, 2009, at 4:15 PM, kahou lei wrote: > I made some changes on fibre channel support in wireshark. How can I > submit the changes? File a bug on bugs.wireshark.org (you'll need to open a Bugzilla account), and attach a patch for the changes ("diff -c" or "diff -u") - don't just att

[Wireshark-dev] How to submit changes in wireshark?

Hi, I made some changes on fibre channel support in wireshark. How can I submit the changes? Do I need to go thru a code review before I submit the change? Thanks, Kahou ___ Sent via:Wireshark-dev mailing list Archives:

Re: [Wireshark-dev] registry path Re: how to edit/add an entry in windows registry?

On Jul 14, 2009, at 2:55 PM, Joshua (Shiwei) Zhao wrote: > I want to edit a registry related to the capture device selected. > To get the registry path of a capture device, we need to know its > SubDriverKey which could be specified somewhere in windows registry. > > When Wireshark make a list

[Wireshark-dev] registry path Re: how to edit/add an entry in windows registry?

I want to edit a registry related to the capture device selected. To get the registry path of a capture device, we need to know its SubDriverKey which could be specified somewhere in windows registry. When Wireshark make a list of available devices for capture preparation, we get the list from dum

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

The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/6531 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: windows-xp-x86 Build Reason

Re: [Wireshark-dev] Adding mp2t sub dissector plugin

Thanks On Tue, Jul 14, 2009 at 11:20 AM, Guy Harris wrote: > > On Jul 14, 2009, at 10:56 AM, Frederic Turmel wrote: > > > Hi, I'm trying to build a plugin to dissect the payload of an mpeg > > transport packet. I'm using the following to add my plugin: > > > > dissector_add("mp2t.pid", 0x1f7

Re: [Wireshark-dev] Dissector bug ... failed assertion

On Jul 14, 2009, at 12:11 PM, Jeremy Duff wrote: > I've managed to reuse some of the code in epan/dissectors/packet- > fr.c that hands off information to the osinl so that I could make > epan/dissectors/lapd.c act the same way. Everything appears to be > working correctly, however, I'm getti

[Wireshark-dev] Dissector bug ... failed assertion

I've managed to reuse some of the code in epan/dissectors/packet-fr.c that hands off information to the osinl so that I could make epan/dissectors/lapd.c act the same way. Everything appears to be working correctly, however, I'm getting this bug and can't figure out why: [Dissector bug, protocol L

Re: [Wireshark-dev] Question to header fields and tvb

On Jul 14, 2009, at 10:59 AM, arno wrote: > The problem is that many parts of the protocol do not always consist > of > the same amount of bytes. Therefore the bytes have to be decoded that > way (java code): > int decode(bytestream stream){ >int b = stream.readByte(); >int t = b; >

Re: [Wireshark-dev] regarding Wireshark's TCP plugin

On Jul 14, 2009, at 5:59 AM, Selçuk Cevher wrote: > Does Wireshark's TCP plugin only use port numbers No. > or some other additional mechanisms Yes. > to identify the application layer traffic ? ... > If it uses other mechanisms for traffic identification, what are > these ? The

Re: [Wireshark-dev] Adding mp2t sub dissector plugin

On Jul 14, 2009, at 10:56 AM, Frederic Turmel wrote: > Hi, I'm trying to build a plugin to dissect the payload of an mpeg > transport packet. I'm using the following to add my plugin: > > dissector_add("mp2t.pid", 0x1f76, pluginHandle); > > However when I build the code, wireshark crash at

[Wireshark-dev] Question to header fields and tvb

Hey Guys, I`m writing a plugin to dissect a protocol the company I`m working for uses and i have one problem, that no readme or developer guide could solve yet. The problem is that many parts of the protocol do not always consist of the same amount of bytes. Therefore the bytes have to be deco

[Wireshark-dev] Adding mp2t sub dissector plugin

Hi, I'm trying to build a plugin to dissect the payload of an mpeg transport packet. I'm using the following to add my plugin: dissector_add("mp2t.pid", 0x1f76, pluginHandle); However when I build the code, wireshark crash at startup. Is there another way to add a dissector based on the PID

Re: [Wireshark-dev] Time for 1.2.1?

Hi, Here we go, Gerald set the date for 1.2.1 on July 16th. Gerald, need any help? Thanx, Jaap Gerald Combs wrote: > Anders Broman wrote: >> Hi, >> We have a considerable amount of fixed bugs in the queue and we are >> getting a few bug reports on the Windows problems when >> >> no IP address i

Re: [Wireshark-dev] frame relay --> osi

On Jul 13, 2009, at 12:07 PM, Jeremy Duff wrote: > I just can't seem to get this to work. Is there any advice you can > give me to make this happen? Arrange that dissect_lapd_nlpid() gets called at some point? It's static to your version of packet-lapd.c, but nothing in there calls it or

Re: [Wireshark-dev] Extending wireshark with Python

instead of binpac, and since you're doing python, would it be useful to to use pyconstruct http://pyconstruct.wikispaces.com/ as a (simplified) protocol fields "Description Language"? That way pythoners can reuse their pyconstruct code directly in Wireshark? What might be some performance implicat

[Wireshark-dev] frame relay --> osi

I'm not sure if using this email address to ask for help is frowned upon, but I'll give it a shot. In epan/dissectors, the three files I'm working on are packet-fr.c, packet-osi.c and packet-lapd.c. The frame relay dissector hands off information to the osi dissector, and my goal is to mimick this

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

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/2922 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-x86 Build Reason: Bui

[Wireshark-dev] regarding Wireshark's TCP plugin

Hi, Does Wireshark's TCP plugin only use port numbers or some other additional mechanisms to identify the application layer traffic ? To me, using only port numbers does not make sense. If it uses other mechanisms for traffic identification, what are these ? For example, in case of POP3 and SMT

Re: [Wireshark-dev] How to capture udp data?

Siva, A switch sends data only to the ports related to specific data conversations. A hub sends/floods all data to all ports. You'll need to mirror a port or add a hub or network tap. Like Jaap Keuter said: Check the Wiki on CaptureSetup. It's probably a switch you're connected to. http://wiki.wi

Re: [Wireshark-dev] Implementation and Integration of new Protocol

mouquai mouquai wrote: > > > Hello, > > because there is a plethora of Ethernet based protocols not all are > included in Wireshark. I want to integrate a protocol which isn't > supported. What shall i do - is there a "how to" available? > See the developers guide: http://www.wireshark.org/docs/wsd

[Wireshark-dev] Implementation and Integration of new Protocol

Hello, because there is a plethora of Ethernet based protocols not all are included in Wireshark. I want to integrate a protocol which isn't supported. What shall i do - is there a "how to" available? Thx ___ Sent via:Wir

[Wireshark-dev] Speex/16000 support

Hi; I have captured some speex - sampling rate 16000 - When I run RTP analysis the value of Jitter is so weired. I have read that the calculation of Jitter is based on codec sampling rate, does speex or sampling rate 16000 affect this I mean the calculation of Jitter? Thanx _

Re: [Wireshark-dev] How to capture udp data?

Hi, That's src port only.. Thanks & Regards, Siva S Selçuk Cevher wrote: Is it src or dest port or both that you are checking ? On Tue, Jul 14, 2009 at 9:56 AM, Siva S > wrote: Hi, I'm using udp port no 4635 in one machine. Also, I tried out wit

Re: [Wireshark-dev] How to capture udp data?

Hi, Check the Wiki on CaptureSetup. It's probably a switch you're connected to. Thanx, Jaap Sent from my iPhone On 14 jul 2009, at 08:56, Siva S wrote: > Hi, > >I'm using udp port no 4635 in one machine. Also, I tried out with > different port nos. Wireshark on different machine within

Re: [Wireshark-dev] How to capture udp data?

Is it src or dest port or both that you are checking ? On Tue, Jul 14, 2009 at 9:56 AM, Siva S wrote: > Hi, > >I'm using udp port no 4635 in one machine. Also, I tried out with > different port nos. Wireshark on different machine within the same > subnet is not capturing this udp data. If I'

[Wireshark-dev] How to capture udp data?

Hi, I'm using udp port no 4635 in one machine. Also, I tried out with different port nos. Wireshark on different machine within the same subnet is not capturing this udp data. If I'm using the wireshark in the same machine where the udp data is on, then it's working fine. Can anyone help me