Use the specific MCC/MNC fields for the LAI, CGI, ECGI, NR-CGI, TAI,
and 5GS-TAI IEs, continuing to use E212_NONE for PLMNidentity in all
other cases. Add fields and an enum value for 5GS-TAI to packet-e212.
(The 5GSTAC has an additional octet compared to the original TAC.)
- IEC 60870-5-103 is a derivative protocol of the main 101/104 variants.
- It is used primarily for RTU to IED communication and facilitates
collection of basic status, metering and fault data with several same or
similar field types and data formatting.
- This protocol is primarily serial-only but it can be present on
Ethernet-tunneled-serial communication circuits if port servers are used.
- This initial version supports the following ASDU Types:
Prim-to-Sec (RTU-to-IED): Types 6, 7, 20, 45/46 (private)
Sec-to-Prim (IED-to-RTU): Types 1, 5, 6, 8, 9, 205 (private)
When the PLMNidentity information element is part of the CGI, LAI, RAI,
SAI, or TAI, use the specific MNC/MCC field types as appropriate.
Otherwise, use E212_NONE as before.
Implemented dissector for FS_Charset_Cap attribute of fattr4.bitmap4;
it is needed for NFS4 GETATTR or READDIR Reply packets
when FS_Charset_Cap attr was used in request. Closes#17377
This patch adds support for a WTLV encoding. While this feature is
not part of the original SOME/IP standard, it got later added as
experimental/draft feature to the AUTOSAR specification.
GitLab CI annoyingly shows "⚙ blocked" in the pipeline UI if you have
any jobs that can be run manually instead of a green checkmark even if
all of the other jobs in the pipeline have passed. It's not clear that
"blocked" means "you can run this manually if needed," so adjust the
Documentation rule so that this doesn't happen.
Set CMAKE_AUTO{MOC,UIC,RCC} if we're running CMake 3.20.0 or 3.20.1 in
order to work around CMake issue 22085, otherwise set the AUTOMOC,
AUTOUIC, and AUTORCC properties for the qtui target. The latter is
preferred since it keeps us from running Qt's meta-object, user
interface, or resource compilers on code outside of ui/qt. Ping #17314.
Fix multiple problems with UE IP address Pool Identity
* the length of the length field needs to be added to offset
* the length field is two bytes long
* the bitmask on the lenght field is wrong
* add "Length" to the description of the length field
* decode UE IP address Pool Identity as string
Decoding the field as string makes sense because it originates from
a DIAMETER attrbiute that would usually also be decoded as string.
Fixes a very small part of #11398.
The fields were incorrectly identified as error fields because Mangos,
the most popular open source emulator in 2009 incorrectly identified it
as such.
Reverse engineering of the client revealed that the fields were protocol
versions.
As well as misidentifying the field, the WOW_SERVER_TO_CLIENT version
also read the wrong field. The actual error field is the one that comes
after the protocol version field.
Correct packets are in Ember
WOW_CLIENT_TO_SERVER
03c130d3d6/src/login/grunt/client/LoginChallenge.h (L39)
WOW_SERVER_TO_CLIENT
03c130d3d6/src/login/grunt/server/LoginChallenge.h (L33)
As well as the Wiki
https://wowdev.wiki/Packets/Login/Vanilla#Challenge_packets
Move common fuzzing configuration items to .fuzz-ubuntu. Build using
Clang, which is what the Buildbot fuzzers did. Add jobs for fuzzing
using Valgrind and randpkt.
Gerald Combs