Don't fetch fields until you need them, so you don't throw an early
exception.
Give the fields names starting with the name of the protocol.
svn path=/trunk/; revision=8495
sequence numbers and window scaling" option is set, as that option says
it controls whether we attempt to display the real post-scaling window
size.
Also, don't store it unless the "Analyze TCP sequence numbers" option is
set, as "Relative sequence numbers and window scaling" requires it,
because, unless "Analyze TCP sequence numbers" is set, we don't set up
conversations for TCP connections and don't have a pool of data
structures for per-connection information into which to store the window
scale option value.
svn path=/trunk/; revision=8490
Tools/Statistics; change the taps to put things under Statistics
themselves. That allows taps to go elsewhere if appropriate.
svn path=/trunk/; revision=8488
When a socks connection was used to create a second socks connection
the socks dissector would be called recursively until a heap overflow
occurred.
svn path=/trunk/; revision=8487
well-known port), so we remove the extra code to handle changing it - if
it ever becomes useful to have the port number settable, we can put it
back.
svn path=/trunk/; revision=8485
don't have to worry about the file name being null when
"cf_get_display_name()" is called. (It should never be called before we
have a capture file open; if it is, that's a bug.)
svn path=/trunk/; revision=8482
capture temporary files, it's "<capture", and for saved capture files,
it's the last component of the pathname of the file. Use that in
various places when displaying the file name.
svn path=/trunk/; revision=8474
Don't crash if "-z" is used on the command line when a live
capture is being done (e.g., with "-k -S" - in that case,
"cfile.filename" is null when the window is created), just don't
display the file name in the title.
Don't set the title of a non-existent window - create the window
first.
svn path=/trunk/; revision=8472
and V6 AODV messages is the addresses in the message.
According to the now-expired draft-perkins-aodv6-01, some of the
messages differ in the order of the fields as well.
Dissect the draft-ietf-manet-aodv-13 messages correctly.
svn path=/trunk/; revision=8466
are that the address fields are enlarged", so presumably that supercedes
the now-expired draft-perkins-aodv6-01 which gives different type
numbers for V6. We support both - the draft-ietf-manet-aodv-13 messages
are dissected based on the address type of the source address, while the
draft-perkins-aodv6-01 messages are dissected as V6.
Handle the Route Reply Acknowledgment message.
svn path=/trunk/; revision=8465
Updated the COPS dissector to print the names of the Prefix
PRIDs correctly. The last fix to PRID OID printout caused this
minor problem for PPRIDs.
Rename a few variables to make the code more logical to read.
svn path=/trunk/; revision=8464
Track window scaling and display the window field after it has been scaled to its real value
If we have seen a SYN packet with a WindowScalingOption
then if the option to use RelativeSequence numbers has been enabled,
then ethereal will change the presented window field to be the window after it has been scaled to the real value.
This obviously only works if we have seen the SYN packet and if the SYN packet contained a window scaling option
svn path=/trunk/; revision=8461
One can now select a packet and mark it as a TimeReference packet using the menu.
A TimeReference packet will be indicated by having all timestamp related column entries replaced by the string *REF*
A TimeReference packet will always be displayed in the packet pane, and overrides any display filters.
When a frame is a TimeReference frame, all later frames will calculate the TimeRelativeToFirstPacket relative to the timestamp of the TimeReference frame instead of the first frame of the capture.
You can have any number of TimeReference frames you like.
svn path=/trunk/; revision=8459
The tap listener will try to parse this pointer at a much later stage where the stack frame where this object lived will have dissapeared and possible got overwritten.
best that can happen is that service response times for dcerpc interfaces is screwed up
more probable is that we get a coredump
svn path=/trunk/; revision=8455
the option to print only marked packets similarly, rather than as
"Suppress unmarked packets" (for consistency, and because the latter
isn't unlike a double negative).
svn path=/trunk/; revision=8451
Tim Potter