http://www.nbee.org/ 2010-09-07T22:18:49+02:00 http://www.nbee.org/ http://www.nbee.org/lib/images/favicon.ico text/html 2010-03-31T14:57:00+02:00 http://www.nbee.org/doku.php?id=netpdl:advanced&rev=1270040220&do=diff This document presents a set of NetPDL primitives that are mainly targeted to advanced protocol description and verification, and that include session tracking. Although these primitives are part of the NetPDL specification, a separate document has been created due to the (relative) complexity of these constructs. text/html 2009-04-20T11:35:15+02:00 http://www.nbee.org/doku.php?id=netpdl:changelog&rev=1240220115&do=diff Version 0.2 (work-in-progress) * Expressions: supported new functions hasstring() and extractstring() and added the possibility to support other functions * Expressions: added the possibility to specify a ”0” size when the [startat:size] operator is used for variables, fields, packetbuffer, etc. * Expressions: matching can be done through regular expressions (see hasstring() and extractstring() functions) * Expressions: new notation for hexadecimal strings (the ”#” character is no longe… text/html 2010-07-26T08:26:19+02:00 http://www.nbee.org/doku.php?id=netpdl:core_specs&rev=1280125579&do=diff Language Basics Before describing the NetPDL language in depth, a brief overview of the language itself is presented. <netpdl>: the root element A NetPDL file starts with the <netpdl> root element, which supports the following attributes in addition to the ones: text/html 2009-04-20T11:35:12+02:00 http://www.nbee.org/doku.php?id=netpdl:expressions&rev=1240220112&do=diff The protocol header description, as well as the encapsulation description, requires the support of mathematical and string expressions. For instance, we should evaluate the length field of an IP packet before determining if that protocol contains any optional fields, and more. text/html 2010-03-31T14:55:42+02:00 http://www.nbee.org/doku.php?id=netpdl:index&rev=1270040142&do=diff This document provides a complete introduction to NetPDL, a Markup Language that aims to describe Protocols from OSI layer 2 to OSI layer 7. NetPDL is an acronym that stands for Network Protocol Description Language. Network Protocol stands for Cell, Frame, Packet or PDU, while Description Language means that different tools can use the same description to accomplish different tasks. This document assumes that the reader is familiar with the format of the most commonly used network protocols. text/html 2010-03-31T14:53:37+02:00 http://www.nbee.org/doku.php?id=netpdl:license&rev=1270040017&do=diff This page contains the license of the NetPDL, PDML and PSML languages. /* * Copyright (c) 2003 - 2010 * NetGroup, Politecnico di Torino (Italy) * All rights reserved. * * The NetGroup hereby grants to you a free of charge, nonexclusive, * nontransferable, perpetual, worldwide limited license (without the right * to sublicense) under NetGroup's intellectual property rights. * This license allows and is limited to the creation and distribution of * clean room implementations of this … text/html 2009-04-20T11:35:14+02:00 http://www.nbee.org/doku.php?id=netpdl:netpdl_dissector&rev=1240220114&do=diff Here is a list of all supported protocols. Download A XML version of the NetPDL dissectors can be downloaded here. A ZIP version of the NetPDL dissectors can be downloaded here. text/html 2010-03-31T14:56:25+02:00 http://www.nbee.org/doku.php?id=netpdl:netpdlfabio&rev=1270040185&do=diff Defining the structure of the protocol headers: the <fields> element This element is a container for all the structures that defines the header of the protocol. The protocol header starts with the first <field> or <cfield> element contained in the <fields> section. text/html 2010-03-31T14:56:09+02:00 http://www.nbee.org/doku.php?id=netpdl:netpdlfulvio&rev=1270040169&do=diff Draft - Defining a set of Abstract Data Types for complex fields Network applications often define a some very peculiar data structures for data exchange. Although the primitives defined in NetPDL are suitable for describin a large set of fields, it may be useful to define some complex fields once, and then reuse these definitions when needed. text/html 2010-06-23T08:01:32+02:00 http://www.nbee.org/doku.php?id=netpdl:netpdlregex&rev=1277272892&do=diff This document briefly presents Regular Expressions, which are supported by NetPDL. Most of the content of this document is elsewhere available on the Internet (e.g. Wikipedia, the RegularExpression.info tutorial (probably the best source), and the David Mertz Tutorial). An excellent manual can be found in the pcrepattern.html file, which is distributed as part of the PCRE documentation. text/html 2010-03-31T14:54:46+02:00 http://www.nbee.org/doku.php?id=netpdl:pdml_specification&rev=1270040086&do=diff The PDML language is a very simple language that keeps the information related to a decoded packet. PDML stands for Packet Details Markup Language and it is strongly related to NetPDL. This language is used by a NetPDL engine that understands the NetPDL Visualization Extension to create a detailed view of each packet. text/html 2010-03-31T14:53:17+02:00 http://www.nbee.org/doku.php?id=netpdl:psml_specification&rev=1270039997&do=diff The PSML language is a very simple language that keeps the most important information related to a decoded packet (i.e. the summary view). PSML stands for Packet Summary Markup Language and it is strongly related to the NetPDL. This language is used by a NetPDL engine that understands the NetPDL Visualization Extension to create a summary view of each packet. text/html 2010-03-31T14:47:07+02:00 http://www.nbee.org/doku.php?id=netpdl:schema&rev=1270039627&do=diff This page points to the XSD schema for the NetPDL, PDML and PSML languages: * NetPDL XSD Schema * PDML XSD Schema * PSML XSD Schema text/html 2010-07-13T09:06:00+02:00 http://www.nbee.org/doku.php?id=netpdl:visualization_expression&rev=1279004760&do=diff A tool that has to inspect network packets for visualizing its hex dump in a human-readable form can choose between two different views: * a summary view, in which the most important fields of each packet are shown (for example source and destination address) * a detailed view, in which all the fields are shown, each one with the most detailed information available.