- conversation.[ch] - To support not setting port2 on matching a
conversation. This is used by protocols such as iSNS in which the client
registers a TCP/UDP port with the server for notifications and the server
sends notifications to this port from different source ports.
- packet-isns.c - Added support for handling zero-length TLVs and ESI & SCN
frames (when registering an SCN/ESI port, a conversation dissector is
setup).
svn path=/trunk/; revision=11320
Don't try to dissect the MD5 authentication data as a route
entry (RTE). It's not. I made sure it's also the last entry in
the packet and it gets dissected only if MD5 authentication is
used.
Some implementation use the Auth. Data Length field value as
the WHOLE Authentication data length (0xFFFF (2 bytes) + 0x0001
(2 bytes) + 16 bytes of auth. data = 20) while others only as
the auth. data length ( = 16). Since MD5's auth data is 16
bytes anyway, I've hard coded it in the code (in #define), and
not relied on auth_data_len. I've tested it on implementations
using either way and it seems to work fine.
svn path=/trunk/; revision=11317
strength for AVS headers.
Also add them for the Prism and Radiotap headers, and for the
pseudo-header from non-native captures.
svn path=/trunk/; revision=11316
"SLAB_ITEM_TYPE_DEFINE()" macro to define a union of the type of object
for the slab and a pointer to an object of that union type, and use that
type for items on the slab allocator free lists; that *should* avoid
having the compiler think two pointers to an item being added to or
removed from the free list don't point to the same object just because
they have different types.
svn path=/trunk/; revision=11306
object being allocated, rather than the name of the free list, as an
argument (with the name of the free list constructed from the name of
the type), and add macros to define and declare the free list, also
taking the type of the object being allocated.
svn path=/trunk/; revision=11305
create the parameter tvbuff, as that requires that there's at least one
byte of parameter data, and some messages have no parameters and would
cause an exception to be thrown in that case.
Just use -1 for the length parameters when creating the parameter
tvbuff, so that it includes the full reported length.
Don't put undissected parameter information into the protocol tree if
there aren't any parameters - and don't bother getting the number of
bytes of parameter information unless we're putting undissected
parameter information into the protocol tree and need it to see whether
there are any parameters.
svn path=/trunk/; revision=11297
Note that it's been claimed that an address field whose first byte has
the low-order bit not zero indicates Frame Relay fragmentation, FRF.12,
and that we should perhaps handle that.
svn path=/trunk/; revision=11295
of operands, changed most values to be output as decimal.
Many thanks to Martin Regner for valuable ideas, reviewing the output and assisting in debuging the code.
svn path=/trunk/; revision=11271
