configure Wireshark, so we don't, for example, do "make distcheck" with
no options, and thus default to GTK+ 3, on a system without GTK+ 3 where
Wireshark was configured with --with-gtk2. (This also means that if
we're configuring only with Qt, or with GTK+ *and* Qt, "make distcheck"
will check with those.)
svn path=/trunk/; revision=51456
Add Support of Decoding 802.11s Mesh Channel Switch Parameter Element
From me:
Remove some trailing whitespace
Add subtree for flag
Change typo of display filter
svn path=/trunk/; revision=51453
According to RFC, TTL valid values are the positive values of a 32 bit signed field. This means that, despite the negative values can be put in a packet, they should be ignored. Wireshark prints them correctly, but a warning expert info could be useful.
svn path=/trunk/; revision=51452
In sss_string():
-> Protect against tvb_length_remaining() possibly returning -1.
-> Fix off-by-1 potential buffer overflow condition.
-> Use isprint() rather than "do-it-yourself" code.
-> Remove the extra unnecessary "length_remaining" checks in the for() loop.
#BACKPORT(1.10, 1.8)
svn path=/trunk/; revision=51448
[ 6%] Building C object epan/CMakeFiles/epan.dir/addr_resolv.c.o
/home/jmayer/work/wireshark/svn/trunk/epan/addr_resolv.c:1927:1: error: unused function
'get_ipxnetbyname' [-Werror,-Wunused-function]
get_ipxnetbyname(const gchar *name)
^
/home/jmayer/work/wireshark/svn/trunk/epan/addr_resolv.c:2009:1: error: unused function
'add_ipxnet_name' [-Werror,-Wunused-function]
by #if 0/#endif the functions. If they really are not needed any more
they should be removed.
svn path=/trunk/; revision=51438
Speaking of r51356, a clarification to its commit message is in order: Initially my intention was to only add the urgent pointer field when the URG bit was set; however, I then noticed that the acknowledgment number field was always being added irrespective of the ACK bit. Had I made the change as I originally intended, it would have introduced an inconsistency. After some deliberation, I opted for consistency, but botched the commit message.
svn path=/trunk/; revision=51431
is internally consistent.
TODO: include r11 sequence that can overwrite some of these values.
TODO: actx->private_data gets reused for several purposes, need to
separate these uses out and avoid possible conflicts...
svn path=/trunk/; revision=51429
packet-rtpproxy.c:226: warning: implicit conversion shortens 64-bit value into
a 32-bit value
I'm not quite sure what's going on here, all the values in use are either gint
or guint so they should all be the same size?
svn path=/trunk/; revision=51419
Dissector for the Sippy RTPproxy controlling protocol. RTPproxy is a well-known
(among SIP-engineers) application and it operates using its own simple
text-based protocol. There are several competing products but all of them
implements it (sometimes slightly extending).
svn path=/trunk/; revision=51417
From Michal Labedzki.
From me:
1. Have boolean filters use tfs_true_false instead of NULL (because it appears previous functionality had "TRUE" and "FALSE"). Perhaps other tfs_ values could be used, but tfs_true_false makes a good placeholder.
2. Add FT_ETHER field as a proto_tree_add_item.
svn path=/trunk/; revision=51410
- Expert info for CRC 0x5935 got wrongly attached to Slim SSDO packages
- SPDO Data Requests that fit in the last bytes of a frame got missed
- Slim SSDOs got detected, that actually are not Slim SSDOs, to prevent this in the future, two checks have been added
- The reported length of a Slim SSDO must be larger than 0 (correct
Slim SSDOs always have at least 1 byte)
- Both crc's must differ from another. There is a very unlikely
possibility, that they may collide, but in such a case openSAFETY
in itself would be flawed by design.
svn path=/trunk/; revision=51408
Guy Harris