["Yann -EADS-" <yann_eads@xxxxxxxxxxx>]

Hello,

I'm currently adding a functionality to an OLSR daemon and noticed that 
Ethereal decoding may be improved a little bit.
As I add a new functionality, I use an undefined message type. Then, after 
the common message header, Ethereal can of course not decode what follows. 
But to me, it should indicate something like "Data:" until the next message 
(by referring to the message length) instead of guessing that the next 
message starts immediately. Because in this latter case, what follows is not 
well decoded and the packet is considered "Malformed".

Hope this help the development.
Yann

_________________________________________________________________
MSN Actions Solidaires : volontaire � l'�tranger 
http://www.msn.fr/actionssolidaires/Default.asp?Ath=f