From owner-freebsd-net@FreeBSD.ORG  Fri Mar  4 20:05:00 2005
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 40DFC16A4CE; Fri,  4 Mar 2005 20:05:00 +0000 (GMT)
Received: from green.homeunix.org (green@localhost [127.0.0.1])
	by green.homeunix.org (8.13.3/8.13.1) with ESMTP id j24K4xTm076678;
	Fri, 4 Mar 2005 15:04:59 -0500 (EST)
	(envelope-from green@green.homeunix.org)
Received: (from green@localhost)
	by green.homeunix.org (8.13.3/8.13.1/Submit) id j24K4xXT076677;
	Fri, 4 Mar 2005 15:04:59 -0500 (EST)
	(envelope-from green)
Date: Fri, 4 Mar 2005 15:04:58 -0500
From: Brian Fundakowski Feldman <green@freebsd.org>
To: Aziz KEZZOU <opensource.enthousiat@gmail.com>
Message-ID: <20050304200458.GG6011@green.homeunix.org>
References: <37e13166050304080715525d7e@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <37e13166050304080715525d7e@mail.gmail.com>
User-Agent: Mutt/1.5.6i
cc: freebsd-net@freebsd.org
cc: hackers@freebsd.org
Subject: Re: generic network protocols parser ?
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Mar 2005 20:05:00 -0000

On Fri, Mar 04, 2005 at 11:07:34AM -0500, Aziz KEZZOU wrote:
> Hi all,
> I am wondering if any one knows  about a generic parser which takes a
> packet (mbuf) of a certain protocol (e.g RSVP ) as input and generates
> some data structre representing the packet ?
> 
> I've been searching for a while and found that ethereal and tcpdump
> for example use specific data structres and functions to dissect each
> protocol packets. Is this the only approach possible ?
> 
> My supervisor suggested using a TLV (Type/Length/Value) approach
> instead. Any opinions about that?
> 
> If no such a parser exists is there any practical reason why ?

Ethereal uses TLV...

-- 
Brian Fundakowski Feldman                           \'[ FreeBSD ]''''''''''\
  <> green@FreeBSD.org                               \  The Power to Serve! \
 Opinions expressed are my own.                       \,,,,,,,,,,,,,,,,,,,,,,\