Looking through tcpdump-current at how it decides to decode data for a
particular port, it appears to be all hard coded on a per-port and per-
protocol basis.
This is not really convenient when you happen to run a service on a
different port and want to make use of tcpdump's in-built decoding.
(This may also apply to ethereal...)
WHat I'd like to be able to do, for example, is say port 5353 should
be decoded as "domain" traffic or that port 53 is ssh or ...
Comments ?
Darren
-
This is the TCPDUMP workers list. It is archived at
http://www.tcpdump.org/lists/workers/index.html
To unsubscribe use mailto:[EMAIL PROTECTED]?body=unsubscribe
