I have filed this report in bugzilla as
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1124
Thanks,
-- John.
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Could someone with OS X check if they have the same problem as I do.
When I go into the View -> Color Filters -> Edit Color Filter, the text
color is always black even when the foreground is set to another color.
This makes text on black backgrounds invisible. I'm not experiencing
this probl
Being the C++ generated lua interface sluggish (at least twice slower)
I decided that I'll keep working on the old one.
Here's what I'll do:
For now I checked in a slightly modified version into epan/ which by
now only *nix build uses (that's why I haven't deleted the plugin
yet).
I'll drop ssu
Using tcp_dissect_pdus I have been having issues with improper
dissection of application level protocol PDUs with my proprietary
protocol.
So that this problem can be efficiently debugged, I have reproduced
the issue against a BitTorrent peer.
Problem:
tcp_dissect_pdus is used by many dissectors
On Sun, Sep 24, 2006 at 03:18:19PM -0700, Stephen Fisher wrote:
> There is a problem on OS X between the system's jpeg library and one
> installed by DarwinPorts in /opt when running Wireshark from the build
> directory.
The symptom is this error:
[EMAIL PROTECTED]:/usr/local/src/wireshark>./w
There is a problem on OS X between the system's jpeg library and one
installed by DarwinPorts in /opt when running Wireshark from the build
directory. I wanted to confirm that this is not a Wireshark problem we
can fix before I add it to the FAQ...
To fix, I change the "wireshark" script from:
Hi, I need to parse GTP' packet consisting in its message field the GCDR and then SRecord. Srecord is the record defined by us. Now obviously I need to add code to the ethereal to do this. I plan to check for the type fields in the pay load of the packet myself and then call the corresponding de
Hi,
I have checked in a fix please verify it with your traces.
Best regards
Anders
-Ursprungligt meddelande-
Från: Oleg Kostenko [mailto:[EMAIL PROTECTED]
Skickat: den 20 september 2006 10:41
Till: Anders Broman; wireshark-dev@wireshark.org
Ämne: Re[2]: Fwd: And again BER errors while de
Graeme Lunt wrote:
> Well, it actually doesn't need a new type (FT_URL) as the FI_URL is
> sufficient.
>
Unsure. Having a string tagged as an URL *might* be awkward, however
didn't thought about it too much.
It might be better to see what other developers think.
> See the attached patch (whic
On 9/23/06, Ulf Lamping <[EMAIL PROTECTED]> wrote:
> Graeme Lunt wrote:
> > Hi,
> >
> > Attached is a new version of the related information functionality I had
> > previously submitted (back in May).
> > I thought I would ask for comments before checking it in this time! 8^)
> >
> :-)
> > It adds
Ulf,
> >> I guess this will present the field in the protocol
> >> details tree as a link (similar to "go to frame" fields)
> >> to open it in a browser? Sounds
> >> reasonable.
> >>
> >
> > It doesn't do this at the moment - but it easily could.
> >
>
> Hmmm, thinking of it ag
Ulf,
Thanks for the comments.
> > It adds a new menu item "Related Information" and provides a generic
> > mechanism to register related information for:
> > * a specific hf_index - register_related_hfid_callback()
> > * a range of hf_indexes (e.g. "owned" by a given dissector) -
> > register_rel
12 matches
Mail list logo