We are interested in extending Wireshark's GUI support for adding pcap-ng
comments to editcap. It seems like editcap is a logical place for this type
of functionality. This would allow other tools to modify the comment field
of pcap-ng files. We envisioned a simple command-line interface that would
Gerald Combs wrote:
On 7/31/12 4:02 PM, Jeff Morriss wrote:
morr...@wireshark.org wrote:
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=44174
User: morriss
Date: 2012/07/31 03:57 PM
Log:
(Attempt to) reflect the file moves from r44165.
I wasn't sure what to do with these r
Using your own instance of CloudShark would provide more control than using
the existing cloudshark.org. We also have features in the appliance version
that are turned off on cloudshark.org. But using the existing
cloudshark.orgis also an option.
Cloudshark is not a test tool so its not going to h
Hi,
I think we have reached a point where we need some more testing and
verification on GTK3.
Perhaps we should build a Win GTK3 installer for people to try out. Is
the OSX GTK3 port in better shape
than the GTK2 one? If so perhaps we should build for OSX.
Some things that might need some atte
On Wed, Aug 01, 2012 at 10:51:29AM +0200, Kurt Knochner wrote:
>
> ==> Guy Harris wrote:
>
> > I don't know whether pcapr.net accepts files that aren't in pcap (or
>
> I mentioned pcapr just as an example. I think it would be better to
> host that archive in the wireshark.org domain.
Why? The
On Wed, Aug 1, 2012 at 9:55 AM, Kurt Knochner
wrote:
> would it make sense to add version sections to the preferences file? Parsing
> the
> preference file would a bit more work, but one could separate the modified
> preferences
> in a proper way from each other.
>
> Extra benefit: One could use t
> -Original Message-
> From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-
> boun...@wireshark.org] On Behalf Of Kurt Knochner
> Sent: 01 August 2012 14:51
> To: wireshark-dev@wireshark.org
> Subject: Re: [Wireshark-dev] Capture File Archive
>
>
> Joe McEachern wrote:
>
> > The
would it make sense to add version sections to the preferences file?
Parsing the
preference file would a bit more work, but one could separate the
modified preferences
in a proper way from each other.
Extra benefit: One could use the same preference file with different
(older) versions of
Joe McEachern wrote:
The idea for having a CloudShark instance available to the Wireshark core
team originally surfaced at Sharkfest. We would be happy to provide this.
Joe,
I just brought up the discussion, based on the mentioned question. I'm
glad to hear this has already been discussed at
On Wed, Aug 1, 2012 at 3:38 PM, Anders Broman
wrote:
> And as a consequence we have a few of these cluttering up the code, should
> those live forever or
> Can the be removed after a suitable amount of time?
We should at least support one major upgrade :)
--
Stig Bjørlykke
___
On Wed, Aug 1, 2012 at 3:29 PM, wrote:
> Technically the prefences aren't "obsolete", they are just renamed for
> (internally) optimized code.
We already handle a lot of renamed preferences in set_pref().
--
Stig Bjørlykke
__
-Original Message-
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Stig Bjørlykke
Sent: den 1 augusti 2012 15:06
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Warnings when loading preferences
On Wed, Aug 1, 20
Technically the prefences aren't "obsolete", they are just renamed for
(internally) optimized code. Should the "old names" still be noted as such in
a current preferences file? The main reason for the new "optimized" code was
to get the "general" preferences to use the "preference API", like
On Wed, Aug 1, 2012 at 2:50 PM, Anders Broman
wrote:
> Is it worth it when you can just resave your preferences?
The user may have several profiles with different settings, and will
have to update all profiles with new settings again.
I think we should try preserving the preferences instead of gi
Hello Kurt,
The idea for having a CloudShark instance available to the Wireshark core
team originally surfaced at Sharkfest. We would be happy to provide this.
We'd also be happy to host it or it could live with other Wireshark
resources. Our virtual appliance can run under a VM or be installed di
Is it worth it when you can just resave your preferences?
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of mman...@netscape.net
Sent: den 1 augusti 2012 14:11
To: wireshark-dev@wireshark.org
Subject: Re: [Wireshar
The code won't look as clean, but I can add the backwards compatibility
functionality.
-Original Message-
From: Stig Bjørlykke
To: Developer support list for Wireshark
Sent: Wed, Aug 1, 2012 6:51 am
Subject: [Wireshark-dev] Warnings when loading preferences
Hi.
After upgrading my
Hi.
After upgrading my local wireshark to latest trunk I get some warnings
from my preferences.
I suspect someone rewrote the preference format without handling /
converting old values?
The user should not loose the preferences when upgrading, just because
we changed the format.
12:33:02
==> Guy Harris wrote:
I don't know whether pcapr.net accepts files that aren't in pcap (or
I mentioned pcapr just as an example. I think it would be better to
host that archive in the wireshark.org domain.
Presumably you mean "what protocols are used", as pcapr doesn't take
that's what
19 matches
Mail list logo
