Ethereal-dev: [Ethereal-dev] Discussion about extension facilities within Ethereal ...
In my guise of Dilletante of Sniffer Development, I would like to
encourage discussion about the topic of extension facilities within
Ethereal.
This urge comes about because I sent out an email about random ideas for
improving Ethereal the other day where I suggested that it would be nice
to have a feature that tagged each packet within a TCP
conversation/connection with the source port number of the first SYN
packet.
This seems to come dangerously close to providing an ability for user
extenstion of Ethereal in the form of a programming language of some sort.
It seemed to me that any such programming language should have access to
all the header fields in a packet tree, but should also be able to add
header fields of its own and should be able to access objects like
conversations and per-packet info, and so on, and should be able to create
such info as well.
Now, I realize that all of these ideas are simply generalities, but
perhaps we should talk in generatities for a while, and then get down to
designing the specifics and then implement them.
Regards
-----
Richard Sharpe, rsharpe@xxxxxxxxxx, rsharpe@xxxxxxxxx,
sharpe@xxxxxxxxxxxx
