Developer support list for Wireshark ()

Krishnamurthy Mayya | 1 Mar 2012 04:01

Query

Hi all,

Is it ok if we create a new bug in wireshark bugzilla to say that we are working on writing the decoding module for these protocols and attach the patches, packets after we are done with it??

I just wanted to avoid the duplicate work getting done by many. I am currently working on writing the decoding modules based on few RFCs and will actually take some time to submit it back.

Thanks in advance for the reply.

Thanks and regards

Krishnamurthy Mayya

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe

headers

Guy Harris | 1 Mar 2012 09:06

Re: [Wireshark-commits] rev 41242: /trunk/ /trunk/ui/gtk/: edit_packet_comment_dlg.c edit_packet_comment_dlg.h main_statusbar.c /trunk/: file.c file.h summary.c /trunk/wiretap/: wtap.c


On Feb 29, 2012, at 1:36 PM, Stig Bjørlykke wrote:

> - What about having a severity for each packet comment, with a
> matching color?  Some notes are important while some are just for info
> or clarification.

Note that this would require either a convention for the text of the comment, or a new option in pcap-NG, to
save severity information (for other file formats we'd presumably just have to tag all comments as
"info", as we don't get to modify, for example, NetMon or Network Instruments Observer format).
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe

headers

Tyson Key | 1 Mar 2012 12:11

Re: Query

Hi Krishnamurthy,

Whilst I'm not a core developer, I don't see why that would be a
problem. (In fact, that's how I submitted some of my own dissectors).

Tyson.

On 1 March 2012 03:01, Krishnamurthy Mayya <krishnamurthymayya <at> gmail.com> wrote:
> Hi all,
> Is it ok if we create a new bug in wireshark bugzilla to say that we are
> working on writing the decoding module for these protocols and attach the
> patches, packets after we are done with it??
> I just wanted to avoid the duplicate work getting done by many. I am
> currently working on writing the decoding modules based on few RFCs and will
> actually take some time to submit it back.
>
> Thanks in advance for the reply.
>
> Thanks and regards
> Krishnamurthy Mayya
>
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev <at> wireshark.org>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>             mailto:wireshark-dev-request <at> wireshark.org?subject=unsubscribe

--

-- 
                                          Fight Internet Censorship!
http://www.eff.org
http://vmlemon.wordpress.com | Twitter/FriendFeed/Skype: vmlemon |
00447934365844
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev <at> wireshark.org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request <at> wireshark.org?subject=unsubscribe

headers

Alexis La Goutte | 1 Mar 2012 12:31

Re: Query

Hi,

Sur ! it is not a problem ! :-)

Regards

On Thu, Mar 1, 2012 at 12:11 PM, Tyson Key <tyson.key-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

Hi Krishnamurthy,

Whilst I'm not a core developer, I don't see why that would be a
problem. (In fact, that's how I submitted some of my own dissectors).

Tyson.

On 1 March 2012 03:01, Krishnamurthy Mayya <krishnamurthymayya-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Hi all,
> Is it ok if we create a new bug in wireshark bugzilla to say that we are
> working on writing the decoding module for these protocols and attach the
> patches, packets after we are done with it??
> I just wanted to avoid the duplicate work getting done by many. I am
> currently working on writing the decoding modules based on few RFCs and will
> actually take some time to submit it back.
>
> Thanks in advance for the reply.
>
> Thanks and regards
> Krishnamurthy Mayya
>

> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev-IZ8446WsY0/dtAWm4Da02A@public.gmane.org>
> Archives: http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request-IZ8446WsY0/dtAWm4Da02A@public.gmane.org?subject=unsubscribe

--
Fight Internet Censorship!
http://www.eff.org
http://vmlemon.wordpress.com | Twitter/FriendFeed/Skype: vmlemon |
00447934365844
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev-IZ8446WsY0/dtAWm4Da02A@public.gmane.org>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request-IZ8446WsY0/dtAWm4Da02A@public.gmane.org?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe

headers

Anders Broman | 1 Mar 2012 12:43

Re: Query

Hi,

It can be an advantage to submit in smaller steps to get those reviewed and any quirks ironed out rather than submitting a huge fulfledged dissector.

Regards

Anders

From: wireshark-dev-bounces <at> wireshark.org [mailto:wireshark-dev-bounces-IZ8446WsY0/dtAWm4Da02A@public.gmane.org] On Behalf Of Alexis La Goutte
Sent: den 1 mars 2012 12:31
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Query

Hi,

Sur ! it is not a problem ! :-)

Regards

On Thu, Mar 1, 2012 at 12:11 PM, Tyson Key <tyson.key-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

Hi Krishnamurthy,

Whilst I'm not a core developer, I don't see why that would be a
problem. (In fact, that's how I submitted some of my own dissectors).

Tyson.

On 1 March 2012 03:01, Krishnamurthy Mayya <krishnamurthymayya-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Hi all,
> Is it ok if we create a new bug in wireshark bugzilla to say that we are
> working on writing the decoding module for these protocols and attach the
> patches, packets after we are done with it??
> I just wanted to avoid the duplicate work getting done by many. I am
> currently working on writing the decoding modules based on few RFCs and will
> actually take some time to submit it back.
>
> Thanks in advance for the reply.
>
> Thanks and regards
> Krishnamurthy Mayya
>

> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev-IZ8446WsY0/dtAWm4Da02A@public.gmane.org>
> Archives: http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request <at> wireshark.org?subject=unsubscribe

--
Fight Internet Censorship!
http://www.eff.org
http://vmlemon.wordpress.com | Twitter/FriendFeed/Skype: vmlemon |
00447934365844
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev-IZ8446WsY0/dtAWm4Da02A@public.gmane.org>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request <at> wireshark.org?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe

headers

Munish Dayal | 1 Mar 2012 14:38

Unable to build wireshark-1.6.5

Hi,

I am unable to compile wireshark-1.6.5 source code due to the following error.

Build environment is Linux RHEL5. The compilation machine is not connected to the internet.

Is there a way to bypass this step ?

/usr/bin/perl ./tools/make-services.pl
starting to fetch http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt ...
request for http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt failed with result code:500 at ./tools/make-services.pl line 98.
gmake[2]: *** [services] Error 9

Regards,

Munish

===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe

headers

Martin Kaiser | 1 Mar 2012 16:02

Re: Unable to build wireshark-1.6.5

Thus wrote Munish Dayal (munish.dayal@...):

> I am unable to compile wireshark-1.6.5 source code due to the following error.
> Build environment is Linux RHEL5. The compilation machine is not connected to the internet.

> Is there a way to bypass this step ?

> /usr/bin/perl ./tools/make-services.pl
> starting to fetch
http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt ...
> request for
http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt
failed with result code:500 at ./tools/make-services.pl line 98.
> gmake[2]: *** [services] Error 9

I can't test this now, but could we just ignore the error from the make
target and continue anyway? IIRC this can be done (at least for gnu
make) by prefixing the rule with -

diff --git a/Makefile.am b/Makefile.am
index f79f5c4..ea3fa97 100644
--- a/Makefile.am
+++ b/Makefile.am
 <at>  <at>  -571,7 +571,7  <at>  <at>  ps.c: print.ps $(srcdir)/tools/rdps.py
        $(PYTHON) $(srcdir)/tools/rdps.py $(srcdir)/print.ps ps.c

 services: tools/make-services.pl
-       $(PERL) $(srcdir)/tools/make-services.pl
+       -$(PERL) $(srcdir)/tools/make-services.pl

 CLEANFILES =           \
        *~              \

We'd need something similar for CMake and nmake, I don't know how that
works.
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe

headers

RUOFF, LARS (LARS)** CTR ** | 1 Mar 2012 14:13

Re: Query

... not that there would have been any examples of recent submissions with that problem of course!

(And if there would have been, any similarity is purely coincidental!)

Lars

From: wireshark-dev-bounces <at> wireshark.org [mailto:wireshark-dev-bounces-IZ8446WsY0/dtAWm4Da02A@public.gmane.org] On Behalf Of Anders Broman
Sent: jeudi 1 mars 2012 12:43
To: alexis.lagoutte-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org; Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Query

Hi,

It can be an advantage to submit in smaller steps to get those reviewed and any quirks ironed out rather than submitting a huge fulfledged dissector.

Regards

Anders

From: wireshark-dev-bounces <at> wireshark.org [mailto:wireshark-dev-bounces-IZ8446WsY0/dtAWm4Da02A@public.gmane.org] On Behalf Of Alexis La Goutte
Sent: den 1 mars 2012 12:31
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Query

Hi,

Sur ! it is not a problem ! :-)

Regards

On Thu, Mar 1, 2012 at 12:11 PM, Tyson Key <tyson.key-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

Hi Krishnamurthy,

Whilst I'm not a core developer, I don't see why that would be a
problem. (In fact, that's how I submitted some of my own dissectors).

Tyson.

On 1 March 2012 03:01, Krishnamurthy Mayya <krishnamurthymayya-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Hi all,
> Is it ok if we create a new bug in wireshark bugzilla to say that we are
> working on writing the decoding module for these protocols and attach the
> patches, packets after we are done with it??
> I just wanted to avoid the duplicate work getting done by many. I am
> currently working on writing the decoding modules based on few RFCs and will
> actually take some time to submit it back.
>
> Thanks in advance for the reply.
>
> Thanks and regards
> Krishnamurthy Mayya
>

> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev-IZ8446WsY0/dtAWm4Da02A@public.gmane.org>
> Archives: http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request <at> wireshark.org?subject=unsubscribe

--
Fight Internet Censorship!
http://www.eff.org
http://vmlemon.wordpress.com | Twitter/FriendFeed/Skype: vmlemon |
00447934365844
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev-IZ8446WsY0/dtAWm4Da02A@public.gmane.org>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request <at> wireshark.org?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe

headers

Joerg Mayer | 1 Mar 2012 16:16

Re: Unable to build wireshark-1.6.5

On Thu, Mar 01, 2012 at 04:02:00PM +0100, Martin Kaiser wrote:
> Thus wrote Munish Dayal (munish.dayal <at> aricent.com):
> 
> > I am unable to compile wireshark-1.6.5 source code due to the following error.
> > Build environment is Linux RHEL5. The compilation machine is not connected to the internet.
> 
> > Is there a way to bypass this step ?
> 
> > /usr/bin/perl ./tools/make-services.pl
> > starting to fetch
http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt ...
> > request for
http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt
failed with result code:500 at ./tools/make-services.pl line 98.
> > gmake[2]: *** [services] Error 9
> 
> I can't test this now, but could we just ignore the error from the make
> target and continue anyway? IIRC this can be done (at least for gnu
> make) by prefixing the rule with -
> 
> diff --git a/Makefile.am b/Makefile.am
> index f79f5c4..ea3fa97 100644
> --- a/Makefile.am
> +++ b/Makefile.am
>  <at>  <at>  -571,7 +571,7  <at>  <at>  ps.c: print.ps $(srcdir)/tools/rdps.py
>         $(PYTHON) $(srcdir)/tools/rdps.py $(srcdir)/print.ps ps.c
>  
>  services: tools/make-services.pl
> -       $(PERL) $(srcdir)/tools/make-services.pl
> +       -$(PERL) $(srcdir)/tools/make-services.pl
>  
>  CLEANFILES =           \
>         *~              \
> 
> We'd need something similar for CMake and nmake, I don't know how that
> works.

The "easiest" way would be to put a services file in the output directory
that is newer than tools/make-services.pl (just guessing here).

ciao
     Jörg
--

-- 
Joerg Mayer                                           <jmayer <at> loplof.de>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev <at> wireshark.org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request <at> wireshark.org?subject=unsubscribe

headers

Gilbert Ramirez | 1 Mar 2012 16:48

Re: Unable to build wireshark-1.6.5

"services" is a strange file; its Makefile dependency is just on the tool that creates it, but in reality it's a snapshot in time of data from a remote server.

There should be a way to run a build and NOT regenerated this 'services' files at all; the default services file that comes with the wireshark distro should suffice. When Gerald is rolling a new source release tarball, then the services file could be updated for the release.

A developer that WANTED to re-create services, could, but IMHO it shouldn't happen by default.

Gilbert

On Thu, Mar 1, 2012 at 7:02 AM, Martin Kaiser <lists-XxZfDwE/svGeZLLa646FqQ@public.gmane.org> wrote:

Thus wrote Munish Dayal (munish.dayal-pccXkzZloW5BDgjK7y7TUQ@public.gmane.org):

> I am unable to compile wireshark-1.6.5 source code due to the following error.
> Build environment is Linux RHEL5. The compilation machine is not connected to the internet.

> Is there a way to bypass this step ?

> /usr/bin/perl ./tools/make-services.pl
> starting to fetch http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt ...
> request for http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt failed with result code:500 at ./tools/make-services.pl line 98.
> gmake[2]: *** [services] Error 9

I can't test this now, but could we just ignore the error from the make
target and continue anyway? IIRC this can be done (at least for gnu
make) by prefixing the rule with -

diff --git a/Makefile.am b/Makefile.am
index f79f5c4..ea3fa97 100644
--- a/Makefile.am
+++ b/Makefile.am
<at> <at> -571,7 +571,7 <at> <at> ps.c: print.ps $(srcdir)/tools/rdps.py
$(PYTHON) $(srcdir)/tools/rdps.py $(srcdir)/print.ps ps.c

services: tools/make-services.pl
- $(PERL) $(srcdir)/tools/make-services.pl
+ -$(PERL) $(srcdir)/tools/make-services.pl

CLEANFILES = \
*~ \

We'd need something similar for CMake and nmake, I don't know how that
works.
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev-IZ8446WsY0/dtAWm4Da02A@public.gmane.org>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request-IZ8446WsY0/dtAWm4Da02A@public.gmane.org?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@...?subject=unsubscribe

Mon	Tue	Wed	Thu	Fri	Sat	Sun

			1	2	3	4
5	6	7	8	9	10	11
12	13	14	15	16	17	18
19	20	21	22	23	24	25
26	27	28	29	30	31

157	May 2013
306	April 2013
286	March 2013
226	February 2013
157	January 2013
141	December 2012
145	November 2012
271	October 2012
231	September 2012
270	August 2012
259	July 2012
212	June 2012
271	May 2012
155	April 2012
188	March 2012
218	February 2012
267	January 2012
141	December 2011
189	November 2011
271	October 2011
297	September 2011
702	August 2011
519	July 2011
330	June 2011
367	May 2011
371	April 2011
293	March 2011
235	February 2011
278	January 2011
311	December 2010
369	November 2010
376	October 2010
313	September 2010
248	August 2010
254	July 2010
225	June 2010
341	May 2010
382	April 2010
357	March 2010
313	February 2010
382	January 2010
204	December 2009
287	November 2009
341	October 2009
350	September 2009
380	August 2009
463	July 2009
372	June 2009
393	May 2009
425	April 2009
397	March 2009
368	February 2009
192	January 2009
266	December 2008
288	November 2008
330	October 2008
218	September 2008
259	August 2008
348	July 2008
347	June 2008
280	May 2008
555	April 2008
342	March 2008
344	February 2008
350	January 2008
279	December 2007
513	November 2007
389	October 2007
325	September 2007
633	August 2007
431	July 2007
305	June 2007
433	May 2007
394	April 2007
675	March 2007
512	February 2007
736	January 2007
386	December 2006
523	November 2006
536	October 2006
578	September 2006
392	August 2006
322	July 2006
84	June 2006