Re: [Wireshark-dev] 1.8 branch + release schedule

2012-06-01 Thread Graham Bloice
-Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev- boun...@wireshark.org] On Behalf Of Gerald Combs Sent: 31 May 2012 19:59 To: Developer support list for Wireshark Subject: [Wireshark-dev] 1.8 branch + release schedule Hi, I'd like to branch

[Wireshark-dev] Fwd: [Wireshark-commits] rev 42961: /trunk/ /trunk/: file.c /trunk/wiretap/: file_access.c file_wrappers.c file_wrappers.h wtap.c wtap.def wtap.h

2012-06-01 Thread Anders Broman
(resend, seems lost) This broke wiretap plugins Remove the file_ routines from the .def file for Wiretap - they should only be called by code inside Wiretap. Regards Anders Ursprungligt meddelande Ämne: [Wireshark-commits] rev 42961: /trunk/ /trunk/: file.c

Re: [Wireshark-dev] Fwd: [Wireshark-commits] rev 42961: /trunk/ /trunk/: file.c /trunk/wiretap/: file_access.c file_wrappers.c file_wrappers.h wtap.c wtap.def wtap.h

2012-06-01 Thread Guy Harris
On Jun 1, 2012, at 11:47 AM, Anders Broman wrote: (resend, seems lost) This broke wiretap plugins OK, I added back those routines that Wiretap plugins would use. ___ Sent via:Wireshark-dev mailing list

Re: [Wireshark-dev] Should payload dissectors' (RTP) packets depend on call-setup dissectors' (SIP) packets?

2012-06-01 Thread Jaap Keuter
Hi, Yes, that setup frame should be sufficient. The problem now is that not the correct setup frame is tagged, but that is another matter. Point is case is the SIP/SDP packet defining the conversation, to which the RTP dissector is set. Thanks, Jaap Send from my iPhone On 1 jun. 2012, at

Re: [Wireshark-dev] Should payload dissectors' (RTP) packets depend on call-setup dissectors' (SIP) packets?

2012-06-01 Thread Jeff Morriss
Are you saying that the correct frame is currently not tagged or that it may not always be or...? I suppose I should find a sample capture and try it out. Anyway: good idea, bad idea? Jaap Keuter wrote: Hi, Yes, that setup frame should be sufficient. The problem now is that not the correct

Re: [Wireshark-dev] Should payload dissectors' (RTP) packets depend on call-setup dissectors' (SIP) packets?

2012-06-01 Thread Jeff Morriss
Richard Sharpe wrote: On Fri, Jun 1, 2012 at 11:44 AM, Jeff Morriss jeff.morriss...@gmail.com wrote: One of the more frequently asked questions/reported bugs is users filtering for RTP, saving^W exporting those displayed packets, then opening the new capture file only to find plain UDP.

Re: [Wireshark-dev] Should payload dissectors' (RTP) packets depend on call-setup dissectors' (SIP) packets?

2012-06-01 Thread Anders Broman
Jeff Morriss skrev 2012-06-01 22:15: Richard Sharpe wrote: On Fri, Jun 1, 2012 at 11:44 AM, Jeff Morrissjeff.morriss...@gmail.com wrote: One of the more frequently asked questions/reported bugs is users filtering for RTP, saving^W exporting those displayed packets, then opening the new

Re: [Wireshark-dev] Should payload dissectors' (RTP) packets depend on call-setup dissectors' (SIP) packets?

2012-06-01 Thread Richard Sharpe
On Fri, Jun 1, 2012 at 1:30 PM, Anders Broman a.bro...@bredband.net wrote: Jeff Morriss skrev 2012-06-01 22:15: Richard Sharpe wrote: On Fri, Jun 1, 2012 at 11:44 AM, Jeff Morrissjeff.morriss...@gmail.com wrote: One of the more frequently asked questions/reported bugs is users filtering

Re: [Wireshark-dev] Should payload dissectors' (RTP) packets depend on call-setup dissectors' (SIP) packets?

2012-06-01 Thread Anders Broman
Jeff Morriss skrev 2012-06-01 22:13: Are you saying that the correct frame is currently not tagged or that it may not always be or...? (Simplified) In SIP there is an offer answer model the offer contains a list of possible codecs and perhaps ports The answer contains the choices acceptable by

Re: [Wireshark-dev] Make giop plugins built in dissectors?

2012-06-01 Thread Alexis La Goutte
On Thu, May 31, 2012 at 10:37 PM, Jeff Morriss jeff.morriss...@gmail.comwrote: Anders Broman wrote: Hi, It should be possible to make the giop plugins built in dissectors now, is that something we'd want to do? I'd be all for it mainly so/if we can put packet-parlay.c at the top of the

[Wireshark-dev] ERROR Duplicate protocol name

2012-06-01 Thread Alex Lindberg
Build just before SVN update today was fine., however now after update this PM (01June) builds OK, but failure when running ./tshark -v. $ svn info Path: . URL: http://anonsvn.wireshark.org/wireshark/trunk Repository Root: http://anonsvn.wireshark.org/wireshark Repository UUID:

Re: [Wireshark-dev] ERROR Duplicate protocol name

2012-06-01 Thread Jeff Morriss
Alex Lindberg wrote: Build just before SVN update today was fine., however now after update this PM (01June) builds OK, but failure when running ./tshark -v. [...] ** (process:9695): ERROR **: Duplicate protocol name Coseventcomm Dissector Using GIOP API! This might be caused by an

Re: [Wireshark-dev] ERROR Duplicate protocol name

2012-06-01 Thread Alex Lindberg
Yep - Thanks. --- On Fri, 6/1/12, Jeff Morriss jeff.morriss...@gmail.com wrote: From: Jeff Morriss jeff.morriss...@gmail.com Subject: Re: [Wireshark-dev] ERROR Duplicate protocol name To: Developer support list for Wireshark wireshark-dev@wireshark.org Date: Friday, June 1, 2012, 4:32 PM

[Wireshark-dev] Add new plugin in trunk

2012-06-01 Thread Alexis La Goutte
Hi, I hope to include 2 new dissectors before the 1.8 release. - WSE Remote Ethernet protocol ( https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7260 ) - SPDY dissector ( http://code.google.com/p/spdyshark/ ) This dissector has actually plugin dissector. It makes sense to include

Re: [Wireshark-dev] Add new plugin in trunk

2012-06-01 Thread Anders Broman
Alexis La Goutte skrev 2012-06-01 23:47: Hi, I hope to include 2 new dissectors before the 1.8 release. * WSE Remote Ethernet protocol ( https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7260 ) * SPDY dissector ( http://code.google.com/p/spdyshark/ ) This dissector has actually