forked from osmocom/wireshark
From John Bradshaw:
Spelling fixes https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6296 svn path=/trunk/; revision=38834daniel/osmux
Anders Broman
parent
f16a746c63
commit
b2633b05d8
|
|
@ -38,7 +38,7 @@ set(CPACK_STRIP_FILES true)
|
|||
|
||||
set(CPACK_SOURCE_PACKAGE_FILE_NAME "${CPACK_PACKAGE_NAME}-${CPACK_PACKAGE_VERSION}")
|
||||
set(CPACK_PACKAGE_INSTALL_DIRECTORY "/usr")
|
||||
# Win: NSIS, ZIP, SORUCE_ZIP, CYGWIN_BINARY, SOURCE_CYGWIN,
|
||||
# Win: NSIS, ZIP, SOURCE_ZIP, CYGWIN_BINARY, SOURCE_CYGWIN,
|
||||
# Linux/Unix: DEB, RPM, STGZ, TBZ2, TZ, SOURCE_TZ, SOURCE_TGZ
|
||||
# OSX: PACKAGEMAKER, OSXX11
|
||||
# Syntax: "Type1;Type2;Type3"
|
||||
|
|
|
|||
4
README
4
README
|
|
@ -106,7 +106,7 @@ Network General/Network Associates DOS-based Sniffer (compressed and
|
|||
uncompressed)
|
||||
Microsoft Network Monitor
|
||||
AIX's iptrace
|
||||
Cinco Networks NetXRray
|
||||
Cinco Networks NetXray
|
||||
Network Associates Windows-based Sniffer
|
||||
AG Group/WildPackets EtherPeek/TokenPeek/AiroPeek/EtherHelp
|
||||
RADCOM's WAN/LAN Analyzer
|
||||
|
|
@ -114,7 +114,7 @@ Lucent/Ascend access products
|
|||
HP-UX's nettl
|
||||
Toshiba's ISDN routers
|
||||
ISDN4BSD "i4btrace" utility
|
||||
Cisco Secure Intrustion Detection System iplogging facility
|
||||
Cisco Secure Intrusion Detection System iplogging facility
|
||||
pppd logs (pppdump-format files)
|
||||
VMS's TCPIPtrace utility
|
||||
DBS Etherwatch for VMS
|
||||
|
|
|
|||
|
|
@ -2,11 +2,11 @@ $Id$
|
|||
|
||||
Description:
|
||||
============
|
||||
DECT pcap files can be obtained by using tools coming with the linux
|
||||
DECT pcap files can be obtained by using tools included with the linux
|
||||
kernel driver for the Dosch-and-Amand COM-ON-AIR cards. The driver is
|
||||
called com-on-air_cs.
|
||||
|
||||
Wireshark itself cannot directy record from the DECT HW, as the driver
|
||||
Wireshark cannot directly record from the DECT HW, as the driver
|
||||
currently lacks a virtual network interface.
|
||||
|
||||
There is ongoing work to change this (see this work by Patrick McHardy):
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@ FreeBSD 6.0 and later this can be done by creating an /etc/devfs.rules
|
|||
file with content such as
|
||||
|
||||
[localrules=10]
|
||||
add path 'bpf*' {mode and permissons}
|
||||
add path 'bpf*' {mode and permissions}
|
||||
|
||||
where "mode and permissions" can include clauses such as
|
||||
|
||||
|
|
|
|||
|
|
@ -108,7 +108,7 @@ About cmake in general and why KDE4 uses it
|
|||
Introductory/tutorial presentation
|
||||
http://ait.web.psi.ch/services/linux/hpc/hpc_user_cookbook/tools/cmake/docs/Cmake_VM_2007.pdf
|
||||
|
||||
Introductory arcticle in Linux Journal
|
||||
Introductory article in Linux Journal
|
||||
http://www.linuxjournal.com/node/6700/print
|
||||
|
||||
Useful variables
|
||||
|
|
|
|||
|
|
@ -253,11 +253,11 @@ promiscuous mode support.
|
|||
|
||||
An additional note, from Jost Martin, for HP-UX 10.20:
|
||||
|
||||
Q: How do I get ethereral on HPUX to capture the _outgoing_ packets
|
||||
Q: How do I get wireshark on HPUX to capture the _outgoing_ packets
|
||||
of an interface
|
||||
A: You need to get PHNE_20892,PHNE_20725 and PHCO_10947 (or
|
||||
newer, this is as of 4.4.00) and its dependencies. Then you can
|
||||
enable the feature as descibed below:
|
||||
enable the feature as described below:
|
||||
|
||||
Patch Name: PHNE_20892
|
||||
Patch Description: s700 10.20 PCI 100Base-T cumulative patch
|
||||
|
|
|
|||
22
airpcap.h
22
airpcap.h
|
|
@ -138,7 +138,7 @@ typedef enum _AirpcapValidationType
|
|||
{
|
||||
AIRPCAP_VT_ACCEPT_EVERYTHING = 1, ///< Accept all the frames the device captures
|
||||
AIRPCAP_VT_ACCEPT_CORRECT_FRAMES = 2, ///< Accept correct frames only, i.e. frames with correct Frame Check Sequence (FCS).
|
||||
AIRPCAP_VT_ACCEPT_CORRUPT_FRAMES = 3, ///< Accept corrupt frames only, i.e. frames with worng Frame Check Sequence (FCS).
|
||||
AIRPCAP_VT_ACCEPT_CORRUPT_FRAMES = 3, ///< Accept corrupt frames only, i.e. frames with wrong Frame Check Sequence (FCS).
|
||||
AIRPCAP_VT_UNKNOWN = 4 ///< Unknown validation type. You should see it only in case of error.
|
||||
}AirpcapValidationType, *PAirpcapValidationType;
|
||||
|
||||
|
|
@ -193,7 +193,7 @@ typedef struct _AirpcapKeysCollection
|
|||
/*!
|
||||
\brief Packet header.
|
||||
|
||||
This structure defines the BPF that preceeds every packet delivered to the application.
|
||||
This structure defines the BPF that precedes every packet delivered to the application.
|
||||
*/
|
||||
typedef struct _AirpcapBpfHeader
|
||||
{
|
||||
|
|
@ -380,7 +380,7 @@ void AirpcapClose(PAirpcapHandle AdapterHandle);
|
|||
|
||||
The main reason to turn monitor mode off is that, when not in monitor mode, the adapter will acknowledge the
|
||||
data frames sent to its address. This is useful when the adapter needs to interact with other devices on the
|
||||
802.11 network, bacause handling the ACKs in software is too slow.
|
||||
802.11 network, because handling the ACKs in software is too slow.
|
||||
|
||||
\note When an adapter is plugged into the system, it's always configured with monitor mode ON. The monitor mode
|
||||
configuration is not stored persistently, so if you want to turn monitor mode off, you will need to do it
|
||||
|
|
@ -417,7 +417,7 @@ gboolean AirpcapGetMonitorMode(PAirpcapHandle AdapterHandle, gboolean * PMonitor
|
|||
the developer's pack can be used as a reference on how to decode 802.11 frames with radiotap headers.
|
||||
- \ref AIRPCAP_LT_802_11_PLUS_PPI, to capture 802.11 frames (including control frames) with a Per Packet Information (PPI)
|
||||
header that contains per-packet meta information like channel and power information. More details on the PPI header can
|
||||
be founf in the PPI online documentation (TODO).
|
||||
be found in the PPI online documentation (TODO).
|
||||
*/
|
||||
gboolean AirpcapSetLinkType(PAirpcapHandle AdapterHandle, AirpcapLinkType NewLinkType);
|
||||
|
||||
|
|
@ -460,7 +460,7 @@ gboolean AirpcapSetFcsPresence(PAirpcapHandle AdapterHandle, gboolean IsFcsPrese
|
|||
\param PIsFcsPresent User-provided variable that will be set to true if the adapter is including the FCS.
|
||||
\return TRUE if the operation is successful. FALSE otherwise.
|
||||
|
||||
In the default configuration, the adatper has FCS inclusion turned on. The MAC Frame Check Sequence is 4 bytes
|
||||
In the default configuration, the adapter has FCS inclusion turned on. The MAC Frame Check Sequence is 4 bytes
|
||||
and is located at the end of the 802.11 packet, with both AIRPCAP_LT_802_11 and AIRPCAP_LT_802_11_PLUS_RADIO
|
||||
link types.
|
||||
When the FCS inclusion is turned on, and if the link type is AIRPCAP_LT_802_11_PLUS_RADIO, the radiotap header
|
||||
|
|
@ -483,7 +483,7 @@ gboolean AirpcapSetFcsValidation(PAirpcapHandle AdapterHandle, AirpcapValidation
|
|||
\brief Checks if the specified adapter is configured to capture frames with incorrect an incorrect Frame Check Sequence (FCS).
|
||||
\param AdapterHandle Handle to the adapter.
|
||||
\param ValidationType Pointer to a user supplied variable that will contain the type of validation the driver will perform. See the documentation of \ref AirpcapValidationType for details.
|
||||
\return TRUE if the operation is succesful. FALSE otherwise.
|
||||
\return TRUE if the operation is successful. FALSE otherwise.
|
||||
|
||||
\note By default, the driver is configured in \ref AIRPCAP_VT_ACCEPT_EVERYTHING mode.
|
||||
*/
|
||||
|
|
@ -518,7 +518,7 @@ gboolean AirpcapSetDeviceKeys(PAirpcapHandle AdapterHandle, PAirpcapKeysCollecti
|
|||
\param KeysCollection User-allocated PAirpcapKeysCollection structure that will be filled with the keys.
|
||||
\param PKeysCollectionSize \b IN: pointer to a user-allocated variable that contains the length of the KeysCollection structure, in bytes.
|
||||
\b OUT: amount of data moved by the driver in the buffer pointed by KeysBuffer, in bytes.
|
||||
\return TRUE if the operation is succesful. If an error occurs, the return value is FALSE and KeysCollectionSize is zero.
|
||||
\return TRUE if the operation is successful. If an error occurs, the return value is FALSE and KeysCollectionSize is zero.
|
||||
If the provided buffer is too small to contain the keys, the return value is FALSE and KeysCollectionSize contains the
|
||||
needed KeysCollection length, in bytes. If the device doesn't have any decryption key configured, the return value is TRUE, and
|
||||
KeysCollectionSize will be zero.
|
||||
|
|
@ -567,7 +567,7 @@ gboolean AirpcapSetDriverKeys(PAirpcapHandle AdapterHandle, PAirpcapKeysCollecti
|
|||
\param KeysCollection User-allocated PAirpcapKeysCollection structure that will be filled with the keys.
|
||||
\param PKeysCollectionSize \b IN: pointer to a user-allocated variable that contains the length of the KeysCollection structure, in bytes.
|
||||
\b OUT: amount of data moved by the driver in the buffer pointed by KeysBuffer, in bytes.
|
||||
\return TRUE if the operation is succesful. If an error occurs, the return value is FALSE and KeysCollectionSize is zero.
|
||||
\return TRUE if the operation is successful. If an error occurs, the return value is FALSE and KeysCollectionSize is zero.
|
||||
If the provided buffer is too small to contain the keys, the return value is FALSE and KeysCollectionSize contains the
|
||||
needed KeysCollection length, in bytes. If the device doesn't have any decryption key configured, the return value is TRUE, and
|
||||
KeysCollectionSize will be zero.
|
||||
|
|
@ -598,7 +598,7 @@ gboolean AirpcapSetDecryptionState(PAirpcapHandle AdapterHandle, AirpcapDecrypti
|
|||
\brief Tells if this open instance is configured to perform the decryption of the incoming frames with the <b>adapter-specific</b> keys.
|
||||
\param AdapterHandle Handle to the adapter.
|
||||
\param PEnable Pointer to a user supplied variable that will contain the decryption configuration. See \ref PAirpcapDecryptionState for details.
|
||||
\return TRUE if the operation is succesful. FALSE otherwise.
|
||||
\return TRUE if the operation is successful. FALSE otherwise.
|
||||
|
||||
The adapter-specific decryption keys can be configured with the \ref AirpcapSetDeviceKeys() function.
|
||||
\note By default, the driver is configured with \ref AIRPCAP_DECRYPTION_ON.
|
||||
|
|
@ -665,7 +665,7 @@ gboolean AirpcapGetDeviceChannel(PAirpcapHandle AdapterHandle, guint * PChannel)
|
|||
application is busy, at the cost of higher kernel memory usage.
|
||||
|
||||
\note don't use this function unless you know what you are doing. Due to caching issues and bigger non-paged
|
||||
memory consumption, bigger buffer sizes can decrease the capture performace instead of improving it.
|
||||
memory consumption, bigger buffer sizes can decrease the capture performance instead of improving it.
|
||||
*/
|
||||
gboolean AirpcapSetKernelBuffer(PAirpcapHandle AdapterHandle, guint BufferSize);
|
||||
|
||||
|
|
@ -729,7 +729,7 @@ gboolean AirpcapStoreCurConfigAsAdapterDefault(PAirpcapHandle AdapterHandle);
|
|||
\return TRUE on success.
|
||||
|
||||
The AirPcap driver is able to perform kernel-level filtering using the standard BPF pseudo-machine format. You can read
|
||||
the WinPcap documentation at http://www.winpcap.org/devel.htm for more details on the BPF filtering mechaism.
|
||||
the WinPcap documentation at http://www.winpcap.org/devel.htm for more details on the BPF filtering mechanism.
|
||||
|
||||
A filter can be automatically created by using the pcap_compile() function of the WinPcap API. This function
|
||||
converts a human readable text expression with the tcpdump/libpcap syntax into a BPF program.
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@
|
|||
|
||||
</avp>
|
||||
|
||||
<!--Cisco-Charging-Rule-Defination-->
|
||||
<!--Cisco-Charging-Rule-Definition-->
|
||||
|
||||
<avp name="Cisco-Charging-Rule-Definition" code="131072" vendor-id="Cisco" mandatory="must" may-encrypt="yes" protected="mustnot" vendor-bit="must">
|
||||
<grouped>
|
||||
|
|
@ -936,7 +936,7 @@
|
|||
|
||||
<avp name="Billing-Plan-Install" code="131187" vendor-id="Cisco" mandatory="must" protected="mustnot" may-encrypt="yes" vendor-bit="must">
|
||||
<grouped>
|
||||
<gavp name="Billing-Plan-Defination"/>
|
||||
<gavp name="Billing-Plan-Definition"/>
|
||||
|
||||
|
||||
</grouped>
|
||||
|
|
|
|||
|
|
@ -102,7 +102,7 @@
|
|||
<gavp name="CC-Time"/>
|
||||
<gavp name="CC-Money"/>
|
||||
<gavp name="CC-Total-Octets"/>
|
||||
<gavp name="CC-Imput-Octets"/>
|
||||
<gavp name="CC-Input-Octets"/>
|
||||
<gavp name="CC-output-Octets"/>
|
||||
<gavp name="CC-Service-Specific-Units"/>
|
||||
</grouped>
|
||||
|
|
@ -138,7 +138,7 @@
|
|||
<gavp name="CC-Time"/>
|
||||
<gavp name="CC-Money"/>
|
||||
<gavp name="CC-Total-Octets"/>
|
||||
<gavp name="CC-Imput-Octets"/>
|
||||
<gavp name="CC-Input-Octets"/>
|
||||
<gavp name="CC-output-Octets"/>
|
||||
<gavp name="CC-Service-Specific-Units"/>
|
||||
</grouped>
|
||||
|
|
@ -183,7 +183,7 @@
|
|||
<gavp name="CC-Time"/>
|
||||
<gavp name="CC-Money"/>
|
||||
<gavp name="CC-Total-Octets"/>
|
||||
<gavp name="CC-Imput-Octets"/>
|
||||
<gavp name="CC-Input-Octets"/>
|
||||
<gavp name="CC-output-Octets"/>
|
||||
<gavp name="CC-Service-Specific-Units"/>
|
||||
</grouped>
|
||||
|
|
|
|||
|
|
@ -56,7 +56,7 @@
|
|||
-->
|
||||
<!-- *********************** Commands ***************************** -->
|
||||
<!-- Diameter Base Protocol Command Codes -->
|
||||
<!-- 0-255 RADIUS compatability codes [http://www.iana.org/assignments/radius-types] -->
|
||||
<!-- 0-255 RADIUS compatibility codes [http://www.iana.org/assignments/radius-types] -->
|
||||
<!--256 Unassigned -->
|
||||
<command name="Capabilities-Exchange" code="257" vendor-id="None"/>
|
||||
<command name="Re-Auth" code="258" vendor-id="None"/>
|
||||
|
|
@ -2234,7 +2234,7 @@
|
|||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
|
||||
<!-- AVP:s 411 - 461 Belongs to Carge Control and is defined in chargecontrol.xml
|
||||
<!-- AVP:s 411 - 461 Belongs to Charge Control and is defined in chargecontrol.xml
|
||||
411 CC-Correlation-Id [RFC4006]
|
||||
412 CC-Input-Octets [RFC4006]
|
||||
413 CC-Money [RFC4006]
|
||||
|
|
@ -2573,75 +2573,75 @@ Note: The AVP codes from 320 to 399 are reserved for TS 29.234
|
|||
<enum name="Private identity not requested" code="1"/>
|
||||
</avp>
|
||||
<avp name="GBA-Push-Info" code="417" vendor-bit="must" may-encrypt="no" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
<avp name="NAF-SA-Identifier" code="418" vendor-bit="must" may-encrypt="no" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
<avp name="Security-Feature-Request" code="419" vendor-bit="must" may-encrypt="no" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
<avp name="Security-Feature-Response" code="420" vendor-bit="must" may-encrypt="no" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
<!-- Note: The AVP codes from 421 to 499 are reserved for TS 29.109
|
||||
|
||||
<avp name="Reserved for TS 29.109" code="421" vendor-bit="must" may-encrypt="no" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
<avp name="Reserved for TS 29.109" code="422" vendor-bit="must" may-encrypt="no" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
<avp name="Reserved for TS 29.109" code="423" vendor-bit="must" may-encrypt="no" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
<avp name="Reserved for TS 29.109" code="424" vendor-bit="must" may-encrypt="no" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
<avp name="Reserved for TS 29.109" code="425" vendor-bit="must" may-encrypt="no" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
<avp name="Reserved for TS 29.109" code="426" vendor-bit="must" may-encrypt="no" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
<avp name="Reserved for TS 29.109" code="427" vendor-bit="must" may-encrypt="no" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
<avp name="Reserved for TS 29.109" code="428" vendor-bit="must" may-encrypt="no" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
<avp name="Reserved for TS 29.109" code="429" vendor-bit="must" may-encrypt="no" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
<avp name="Reserved for TS 29.109" code="430" vendor-bit="must" may-encrypt="no" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
<avp name="Reserved for TS 29.109" code="431" vendor-bit="must" may-encrypt="no" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
<avp name="Reserved for TS 29.109" code="432" vendor-bit="must" may-encrypt="no" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
<avp name="Reserved for TS 29.109" code="433" vendor-bit="must" may-encrypt="no" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
<avp name="Reserved for TS 29.109" code="434" vendor-bit="must" may-encrypt="no" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
<avp name="Reserved for TS 29.109" code="435" vendor-bit="must" may-encrypt="no" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
<avp name="Reserved for TS 29.109" code="436" vendor-bit="must" may-encrypt="no" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
<avp name="Reserved for TS 29.109" code="437" vendor-bit="must" may-encrypt="no" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
<avp name="Reserved for TS 29.109" code="438" vendor-bit="must" may-encrypt="no" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
<avp name="Reserved for TS 29.109" code="439" vendor-bit="must" may-encrypt="no" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
29.109 [7]
|
||||
Note: The AVP codes from 421 to 499 are reserved for TS 29.109
|
||||
|
|
@ -3261,7 +3261,7 @@ Note: The AVP codes from 800 to 822 are reserved for TS 32.299.
|
|||
<enum name="Other" code="6"/>
|
||||
</avp>
|
||||
<avp name="TMGI" code="900" mandatory="must" may-encrypt="no" protected="mustnot" vendor-bit="must" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
<avp name="Required-MBMS-Bearer-Capabilities" code="901" mandatory="must" may-encrypt="no" protected="mustnot" vendor-bit="must" vendor-id="TGPP">
|
||||
<type type-name="UTF8String"/>
|
||||
|
|
@ -3273,7 +3273,7 @@ Note: The AVP codes from 800 to 822 are reserved for TS 32.299.
|
|||
<enum name="UPDATE" code="2"/>
|
||||
</avp>
|
||||
<avp name="MBMS-Service-Area" code="903" mandatory="must" may-encrypt="no" protected="mustnot" vendor-bit="must" vendor-id="TGPP">
|
||||
<type type-name="OctectString"/>
|
||||
<type type-name="OctetString"/>
|
||||
</avp>
|
||||
<avp name="MBMS-Session-Duration" code="904" mandatory="must" may-encrypt="no" protected="mustnot" vendor-bit="must" vendor-id="TGPP">
|
||||
<type type-name="Unsigned32"/>
|
||||
|
|
@ -3498,8 +3498,8 @@ Note: The AVP codes from 924 to 999 are reserved for TS 29.061
|
|||
<avp name="QoS-Information" code="1016" mandatory="must" may-encrypt="yes" protected="may" vendor-bit="must" vendor-id="TGPP">
|
||||
<grouped>
|
||||
<gavp name="QoS-Class-Identifier"/>
|
||||
<gavp name="Max-Requested-Bandwdith-DL"/>
|
||||
<gavp name="Max-Requested-Bandwdith-UL"/>
|
||||
<gavp name="Max-Requested-Bandwidth-DL"/>
|
||||
<gavp name="Max-Requested-Bandwidth-UL"/>
|
||||
<gavp name="Guaranteed-Bitrate-UL"/>
|
||||
<gavp name="Guaranteed-Bitrate-DL"/>
|
||||
<gavp name="Bearer-Identifier"/>
|
||||
|
|
@ -5347,7 +5347,7 @@ Note: The AVP codes from 1634 to 1699 are reserved for TS 29.272.
|
|||
<enum name="INVITE_INTO_CONF" code="2"/>
|
||||
<enum name="QUIT_CONF" code="3"/>
|
||||
</avp>
|
||||
<avp name="PDN-Conncetion-ID" code="2050" vendor-bit="must" vendor-id="TGPP">
|
||||
<avp name="PDN-Connection-ID" code="2050" vendor-bit="must" vendor-id="TGPP">
|
||||
<type type-name="Unsigned32"/>
|
||||
</avp>
|
||||
<avp name="Dynamic-Address-Flag" code="2051" vendor-bit="must" vendor-id="TGPP">
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@
|
|||
|
||||
<application id="16777231" name="Diameter e2e4 Application" uri="http://pda.etsi.org">
|
||||
|
||||
<!-- ETSI ES 283 026 V1.6.0 (2008-02) Specifies some eperimental resultcodes with vendor id ETSI
|
||||
<!-- ETSI ES 283 026 V1.6.0 (2008-02) Specifies some experimental resultcodes with vendor id ETSI
|
||||
6.3.2 Experimental-Result-Code AVP values defined in the present
|
||||
document
|
||||
This clause defines the specific values of the Experimental-Result-Code AVP (vendor-id is ETSI):
|
||||
|
|
|
|||
|
|
@ -124,7 +124,7 @@ do
|
|||
local tap = Listener.new();
|
||||
|
||||
function remove()
|
||||
-- this way we remove the listener than otherwise will remain running indifinitelly
|
||||
-- this way we remove the listener than otherwise will remain running indefinitely
|
||||
tap:remove();
|
||||
end
|
||||
|
||||
|
|
|
|||
|
|
@ -260,7 +260,7 @@
|
|||
<listitem><para>
|
||||
Windows 95, 98 and ME are no longer supported. The "old technology"
|
||||
releases of Windows lack memory protection (specifically <ulink
|
||||
url="http://msdn.microsoft.com/en-us/library/aa366898.aspx">VirutalProtect</ulink>)
|
||||
url="http://msdn.microsoft.com/en-us/library/aa366898.aspx">VirtualProtect</ulink>)
|
||||
which we use to improve program safety and security. The last known
|
||||
version to work was Ethereal 0.10.14 (which includes WinPcap 3.1). You
|
||||
can get it from <ulink url="http://ethereal.com/download.html" />.
|
||||
|
|
|
|||
Loading…
Reference in New Issue