| Bug ID |
11479
|
| Summary |
LUA: Read preferences of other/existing protocols
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Enhancement
|
| Priority |
Medium
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 1.12.0 (v1.12.0-0-g4fab41a from master-1.12)
Copyright 1998-2014 Gerald Combs <[email protected]> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with GTK+ 2.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.1.22, with Gcrypt 1.6.0,
without Kerberos, with GeoIP, with PortAudio V19-devel (built Jul 31 2014),
with
AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 3.1.22, Gcrypt 1.6.0, without AirPcap.
Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz, with 4029MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
It would be nice to read preferences of existing protocols from within LUA
scripts. For this, it would be necessary to access existing Proto objects.
Use case: Write a dissector for some protocol residing on top of another
protocol and make the behavior of that higher-layer dissector dependent on what
the settings for the lower layer protocol are.
Example: The lower layer protocol is Ethernet, the higher-layer one is IEEE
1905.1. Depending on Ethernet's setting of "Assume packets have FCS", the
(minimum) length of the 1905.1 payload is either 46 or 50 bytes. So, it's
important to know that Ethernet preference in order to dissect correctly and
recognize malformed packets reliably.
You are receiving this mail because:
- You are watching all bug changes.