This wiki has been migrated to https://gitlab.com/wireshark/wireshark/-/wikis/home and is now deprecated. Please use that site instead.
Differences between revisions 15 and 16
Revision 15 as of 2006-02-06 13:29:37
Size: 3911
Editor: LuisOntanon
Comment:
Revision 16 as of 2006-02-06 21:27:45
Size: 3976
Editor: LuisOntanon
Comment:
Deletions are marked like this. Additions are marked like this.
Line 38: Line 38:
 * [:Lua/Gui: TextWindow] class that manages text-only windows.

Lua

  • attachment:lua_logo.gif

    Lua is a powerful light-weight programming language designed for extending applications. Lua is designed and implemented by a [http://www.lua.org/authors.html team] at [http://www.puc-rio.br/ PUC-Rio], the Pontifical Catholic University of Rio de Janeiro in Brazil. Lua was born and raised at [http://www.tecgraf.puc-rio.br/ Tecgraf], the Computer Graphics Technology Group of PUC-Rio, and is now housed at [http://www.lua.org Lua.org]. Both Tecgraf and Lua.org are laboratories of the [http://www.inf.puc-rio.br/ Department of Computer Science]. Lua's been added to ethereal as for prototyping and scripting.

For more information about Lua refer to [http://www.lua.org Lua's main site], there you can find its [http://www.lua.org/manual/5.0/manual.html Reference Manual] and a [http://www.lua.org/pilhttp://www.lua.org/pil book] that describes the language.

Lua in Ethereal

Lua can be used to write [:Lua/Dissectors: dissectors], post-dissectors and [:Lua/Taps: taps].

Although it's possible to write [:Lua/Dissectors: dissectors] in Lua, ethereal dissectors are written in C, as C is several times faster than Lua. Lua is ok for prototyping dissectors, during Reverse Engineering you can use your time for finding out how things work instead of compiling and debugging your C dissector.

Post-dissectors are dissectors meant to run after every other dissector has run. They can add items the dissection tree so they can be used to create your own extensions to the filtering mechanism.

[:Lua/Taps: Taps] are used to collect information after the packet has been dissected.

Classes

  • [:Lua/Tap: Tap]
  • [:Lua/Field: Field] a handy tool to get fileds from the tree
  • [:Lua/Proto: Proto] represents a protocol
  • [:Lua/ProtoField: ProtoField] the fields of a protocol

  • [:Lua/ProtoFieldArray: ProtoFieldArray]

  • [:Lua/Dissector: Dissector] utility class to handle dissectors
  • [:Lua/Dissector: DissectorTable] utility class to handle dissectors

  • [:Lua/Pinfo: Pinfo] current packet information
  • [:Lua/ProtoTree: ProtoTree]

  • [:Lua/ProtoTree: ProtoItem]

  • [:Lua/SubTree: SubTree] subtrees

  • [:Lua/Tvb: Tvb] access to the packet's actual bytes
  • [:Lua/ByteArray: ByteArray] utility class to manage an array of bytes

  • [:Lua/Gui: TextWindow] class that manages text-only windows.

Examples

  • Examples of generic Lua code can be found in [http://lua-users.org/wiki/SampleCode The Sample Code] page of Lua-Users wiki.

  • [:Lua/Examples/Tap: tap example]
  • [:Lua/Examples/Dissector: dissector example]
  • [:Lua/Examples/PostDissector: post-dissector example]

Discussion

This page is a good start. However, some things remain unclear:

  • How to install/use lua?
  • What's the difference between a post-dissector and a tap

That's what it is, a start... I think it's soon to complete as things are changing as I go ahead.

  • So far it works only on *NIX as I'm still bringing it up. If you want the lua plugin installed configure --with-lua=<lua_directory> to get it to work for windows I'll need help.

  • I do not have yet a clear idea on how Lua will be invoked from ethereal.
    • So far as a temporary solution:
      • it either looks for ~/.ethereal/init.lua and loads that script
      • or looks for a file pointed by the environment variable ETHEREAL_LUA_INIT.
    • It will change as soon as I (or someone else, proposals are welcome) come out with a good way to do it.
  • Tap vs. Postdissector
    • a post dissector is it's like a normal dissector called every time a tree needs to be generated for a frame it just gets called at last.
    • a tap is run once after the first dissection of a packet and it has no access to the tree, it cannot add fields (a postdissector can but it will be called every time a tree needs to be generated).
      • -- Luis E. G. O.

Lua (last edited 2020-03-31 15:55:54 by GeraldCombs)