On Sep 8, 2010, at 8:47 AM, Petr Sumbera wrote:
> But the problem is that stored packets for *outgoing* traffic doesn't
> contain "Header length" (it's zero as at layer where it was captured it
> wasn't filled,
...which means, of course, that no outgoing IPv4 traffic *ever* has IP options.
Ot
Hi,
Have you tried adding those two functions to libwireshark.def?
If that works I suppose that change can be added to trunk.
An alternative if you are OK with building your own wireshark is to add your
dissector in
Custom.nmake to minimize the changes needed.
Regards
Anders
-Original Messag
On Thu, Sep 09, 2010 at 05:03:04PM +0200, Jaap Keuter wrote:
> Otherwise you'll have to modify libwireshark.def and recompile. Call
> Redmond if you don't like it. ;)
We can add those functions to the libwireshark.def in the main source
code tree for use in future builds.
__
Hi,
> this problem seems to be pretty old and was requested in the past
> already
But was a bug filed? If so, ping that so it pops up on the radar again.
> exist there in the meanwhile a possible way without modifying
> original wireshark sources?
Sure, build on !Windows...
Otherwise you'll ha
hello experts,
we made a subdissector for TCAP analyzing a proprietary protocol.
as integrated subdissector it works (building of the whole wireshark).
then we tried to make a plugin but this does not work because of unresolved
references (delete_itu_tcap_subdissector, add_itu_tcap_subdissector).
Hi,
I'm evaluating the way how to add support into Wireshark for Solaris
snoop files with IP tunnel links data.
The data are basically RAW IP so I wouldn't have to write new dissector.
But the problem is that stored packets for *outgoing* traffic doesn't
contain "Header length" (it's zero as a
The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark 1.4.
Full details are available at:
http://buildbot.wireshark.org/trunk-1.4/builders/Windows-XP-x86/builds/91
Buildbot URL: http://buildbot.wireshark.org/trunk-1.4/
Buildslave for this Build: windows-xp-x86
Build Reason: The
