On Thu, Mar 13, 2003 at 04:50:13PM +0100, Tomas Kukosa wrote: > preference name chacking is too strict and I can not register > "tcp.port" preference for "tc" module (it is module in my plugin). > Suggested solution is attached.
Checked in. (Just out of curiosity, why do people use "tcp.port" rather than "tcp_port" for TCP port preferences? There aren't a bunch of TCP-related options, one of which is a port number, in those dissectors, so it's not a multi-level name space.)
