2015-03-15 23:07:38 +01:00
|
|
|
|
2015-03-28 08:29:59 +01:00
|
|
|
Terms used by Cisco, CAPWAP, LWAPP and others ...
|
|
|
|
|
|
|
|
Slot ID = Radio ID
|
|
|
|
AC = MWAR = WLC
|
|
|
|
AP = RAD = WTP
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-21 15:24:48 +01:00
|
|
|
2. Cisco MWAR Addr
|
|
|
|
|
2015-03-23 21:58:11 +01:00
|
|
|
Address of AC
|
|
|
|
|
2015-03-21 15:24:48 +01:00
|
|
|
0 1 2 3
|
|
|
|
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
| MWAR Type | Address |
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
| Adress |
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
|
|
|
|
Type: 2 for MWAR Addr
|
|
|
|
Length: 7
|
|
|
|
|
2015-03-23 21:58:11 +01:00
|
|
|
MWAR Type: 0 SPAM Normal MWAR
|
|
|
|
1 SPAM Master MWAR
|
|
|
|
|
|
|
|
Address: IPv4 Address of AC
|
|
|
|
|
|
|
|
Usage of this field differs from LWAPP where the MAC address
|
|
|
|
of AP is stored in the Address field.
|
|
|
|
(See RFC 5412 - Message type 2: AC Address)
|
2015-03-21 15:24:48 +01:00
|
|
|
|
2015-03-29 01:55:06 +01:00
|
|
|
8. Cisco WTP Radio Configuration
|
|
|
|
|
|
|
|
See RFC 5412 - LWAPP 80211 WTP WLAN Radio Configuration. This Cisco
|
|
|
|
CAPWAP element is slightly different.
|
|
|
|
|
|
|
|
0 1 2 3
|
|
|
|
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
| Radio ID | CFG Type | Occupancy Limit |
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
| CFP Per | CFP Maximum Duration | BSS ID |
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
| BSS ID |
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
| BSS ID | Beacon Period | Country Str1 |
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
| Country Str1 | Country String 2 |
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
| Countr Str2 | gPeriod | Reg(?) |
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
| Reg(?) | ? |
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
|
|
|
|
Type: 8
|
|
|
|
Length: 28
|
|
|
|
|
|
|
|
Radio ID: An 8-bit value representing the radio to configure.
|
|
|
|
|
|
|
|
Config Type:
|
|
|
|
0 = Automatic
|
|
|
|
|
|
|
|
Occupancy Limit: This attribute indicates the maximum amount of
|
|
|
|
time, in Time Units (TUs), that a point coordinator MAY control
|
|
|
|
the usage of the wireless medium without relinquishing control for
|
|
|
|
long enough to allow at least one instance of Distributed
|
|
|
|
Coordination Function (DCF) access to the medium. The default
|
|
|
|
value of this attribute SHOULD be 100, and the maximum value
|
|
|
|
SHOULD be 1000.
|
|
|
|
|
|
|
|
CFP Period: The attribute describes the number of DTIM intervals
|
|
|
|
between the start of Contention-Free Periods (CFPs).
|
|
|
|
|
|
|
|
CFP Maximum Duration: The attribute describes the maximum duration
|
|
|
|
of the CFP in TU that MAY be generated by the Point Coordination
|
|
|
|
Function (PCF).
|
|
|
|
|
|
|
|
BSSID: The WLAN Radio's base MAC address. For WTPs that support
|
|
|
|
more than a single WLAN, the value of the WLAN Identifier is added
|
|
|
|
to the last octet of the BSSID. Therefore, a WTP that supports 16
|
|
|
|
WLANs MUST have 16 MAC addresses reserved for it, and the last
|
|
|
|
nibble is used to represent the WLAN ID.
|
|
|
|
|
|
|
|
Beacon Period: This attribute specifies the number of TUs that a
|
|
|
|
station uses for scheduling Beacon transmissions. This value is
|
|
|
|
transmitted in Beacon and Probe Response frames.
|
|
|
|
|
|
|
|
Country Code: This attribute identifies the country in which the
|
|
|
|
station is operating. The first two octets of this string is the
|
|
|
|
two-character country code as described in document ISO/IEC 3166-
|
|
|
|
1. The third octet MUST be one of the following:
|
|
|
|
|
|
|
|
1. an ASCII space character, if the regulations under which the
|
|
|
|
station is operating encompass all environments in the country,
|
|
|
|
|
|
|
|
2. an ASCII 'O' character, if the regulations under which the station
|
|
|
|
is operating are for an outdoor environment only, or
|
|
|
|
|
|
|
|
|
|
|
|
/* DTIM Period: This attribute specifies the number of Beacon
|
|
|
|
intervals that elapses between transmission of Beacons frames
|
|
|
|
containing a TIM element whose DTIM Count field is 0. This value
|
|
|
|
is transmitted in the DTIM Period field of Beacon frames.
|
|
|
|
*/
|
|
|
|
|
2015-03-21 15:24:48 +01:00
|
|
|
|
2015-03-15 23:47:42 +01:00
|
|
|
83. Cisco AP IP Address
|
2015-03-28 08:29:59 +01:00
|
|
|
The IPv4 configuration of the WTP
|
2015-03-15 23:47:42 +01:00
|
|
|
|
2015-03-29 01:55:06 +01:00
|
|
|
0 1 2 3
|
|
|
|
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
|
2015-03-15 23:47:42 +01:00
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
| IP Address |
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
| Netmask |
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
| Default Gateway |
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
2015-03-28 08:29:59 +01:00
|
|
|
| Type | Reserved ... |
|
2015-03-15 23:47:42 +01:00
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
2015-03-28 08:29:59 +01:00
|
|
|
| Reserved |
|
|
|
|
+-+-+-+-+-+-+-+-+
|
2015-03-15 23:07:38 +01:00
|
|
|
|
2015-03-21 15:24:48 +01:00
|
|
|
Type: 83
|
|
|
|
Length: 16
|
|
|
|
|
|
|
|
IP Address: The IP address of AP
|
|
|
|
Netmask: Netmask
|
|
|
|
Default Gateway: default gateway
|
2015-03-28 08:29:59 +01:00
|
|
|
Type:
|
|
|
|
1=Static
|
|
|
|
0=DHCP
|
|
|
|
Reserved: (?)
|
2015-03-21 15:24:48 +01:00
|
|
|
|
|
|
|
|
2015-03-29 01:55:06 +01:00
|
|
|
91. AC Name with Index
|
|
|
|
|
|
|
|
Same as AC Name with Priority, defined in CAPWAP RFC 5415.
|
|
|
|
|
|
|
|
|
|
|
|
The AC Name with Priority message element is sent by the AC to the
|
|
|
|
WTP to configure preferred ACs. The number of instances of this
|
|
|
|
message element is equal to the number of ACs configured on the WTP.
|
|
|
|
The WTP also uses this message element to send its configuration to
|
|
|
|
the AC.
|
|
|
|
|
|
|
|
0 1
|
|
|
|
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
| Index | AC Name...
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
|
|
|
|
Type: 91 for AC Name with Index
|
|
|
|
|
|
|
|
Length: >= 2
|
|
|
|
|
|
|
|
Priority: A value between 1 and 255 specifying the priority order
|
|
|
|
of the preferred AC. For instance, the value of one (1) is used
|
|
|
|
to set the primary AC, the value of two (2) is used to set the
|
|
|
|
secondary, etc.
|
|
|
|
|
|
|
|
|
|
|
|
AC Name: A variable-length UTF-8 encoded string [RFC3629]
|
|
|
|
containing the AC name, whose maximum size MUST NOT exceed 512
|
|
|
|
bytes.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-21 15:24:48 +01:00
|
|
|
126. Cisco AP Regulatory Domain
|
|
|
|
|
|
|
|
//bandId[0], regDomainSet[1], regDomainSlotId[0], regDomainCode0:[0], regDomainCode1:[1]
|
|
|
|
|
|
|
|
0 1 2 3
|
|
|
|
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
2015-03-28 08:29:59 +01:00
|
|
|
| Band ID | regDomainSet | RegDomainSlot | RegDomainCode0 |
|
2015-03-21 15:24:48 +01:00
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
2015-03-28 08:29:59 +01:00
|
|
|
| RegDomainCode1|
|
2015-03-21 15:24:48 +01:00
|
|
|
+-+-+-+-+-+-+-+-+
|
|
|
|
|
|
|
|
Type: 126
|
|
|
|
Length: 7
|
2015-03-15 23:07:38 +01:00
|
|
|
|
2015-03-20 22:30:51 +01:00
|
|
|
|
|
|
|
|
2015-03-23 07:48:27 +01:00
|
|
|
128. Cisco Reset Button State
|
2015-03-21 15:24:48 +01:00
|
|
|
|
|
|
|
The state of the reset button
|
2015-03-20 22:30:51 +01:00
|
|
|
|
|
|
|
0
|
|
|
|
0 1 2 3 4 5 6 7
|
|
|
|
+-+-+-+-+-+-+-+-+
|
|
|
|
| ResetBtnState |
|
|
|
|
+-+-+-+-+-+-+-+-+
|
|
|
|
|
2015-03-21 15:24:48 +01:00
|
|
|
Type: 128 for Cisco Rest Button State
|
|
|
|
Length: 1
|
2015-03-20 22:30:51 +01:00
|
|
|
|
2015-03-21 15:24:48 +01:00
|
|
|
ResetBtnState: 1 = Enabeled
|
|
|
|
0 = Disabled (?)
|
2015-03-20 22:30:51 +01:00
|
|
|
|
|
|
|
|
2015-03-23 21:58:11 +01:00
|
|
|
151. Cisco AP Time Sync
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
| Unix timestamp |
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
| Type |
|
|
|
|
+-+-+-+-+-+-+-+-+
|
|
|
|
|
|
|
|
Type: 151
|
|
|
|
|
|
|
|
Unix timestamp: Time in seconds since 1.1.1970
|
|
|
|
Type: Time type
|
|
|
|
0 = Manual (?)
|
|
|
|
|
2015-03-28 08:29:59 +01:00
|
|
|
169. Cisco AP IP Domain
|
|
|
|
|
|
|
|
170. Cisco AP IP Name Server
|
2015-03-20 22:30:51 +01:00
|
|
|
|
2015-03-15 23:07:38 +01:00
|
|
|
|
|
|
|
207. Cisco Board Data Options
|
|
|
|
|
2015-03-16 21:41:33 +01:00
|
|
|
The Cisco Board Data element is present in Discovery Request and
|
2015-03-15 23:07:38 +01:00
|
|
|
Join Request messages sent by the WTP.
|
|
|
|
|
|
|
|
0 1 2 3
|
|
|
|
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
2015-03-16 21:41:33 +01:00
|
|
|
| ANT Type | Reserved | AP Type | Join Priority |
|
2015-03-15 23:07:38 +01:00
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
|
2015-03-21 15:24:48 +01:00
|
|
|
Type: 207
|
|
|
|
Length: 4
|
|
|
|
|
|
|
|
|
2015-03-23 07:48:27 +01:00
|
|
|
208. Cisco MWAR Type
|
|
|
|
|
|
|
|
0
|
|
|
|
0 1 2 3 4 5 6 7
|
|
|
|
+-+-+-+-+-+-+-+-+
|
|
|
|
| MWAR Type |
|
|
|
|
+-+-+-+-+-+-+-+-+
|
|
|
|
|
2015-03-23 21:58:11 +01:00
|
|
|
MWAR Type:
|
|
|
|
00 = Normal MWAR
|
|
|
|
01 = Normal MWAR
|
|
|
|
02 = Configured MWAR
|
2015-03-23 07:48:27 +01:00
|
|
|
|
2015-03-28 08:29:59 +01:00
|
|
|
254. Cisco SPAM AP LED Flash Config
|
|
|
|
|
2015-03-23 07:48:27 +01:00
|
|
|
|
2015-03-21 15:24:48 +01:00
|
|
|
|
|
|
|
LWAPP
|
|
|
|
=====
|
2015-03-28 12:51:34 +01:00
|
|
|
In this section Cisco vendor specific message elements used in LWAPP
|
|
|
|
are listed.
|
|
|
|
|
|
|
|
Some of these elements are used by Cisco in CAPWAP where the
|
|
|
|
vendor specific LWAPP message element is encapsulated in a vendor
|
|
|
|
specific CAPWAP message element. So in CAPWAP we see headers like
|
|
|
|
this:
|
|
|
|
|
|
|
|
Vendor spec CAPWAP | Vedor spec LWAPP | Vendor specific LWAPP data
|
|
|
|
00 40 96 00 00 68 | 00 40 96 00 00 86 | ...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
20. Cisco AP Username Password
|
2015-03-28 08:29:59 +01:00
|
|
|
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
| Username (32 bytes) ...
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
... Username |
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
| Password hash ...
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
44. Cisco AP Telnet SSH
|
|
|
|
0 1
|
|
|
|
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
| | |
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
|
|
|
|
Type: 44
|
|
|
|
Length: 2
|
|
|
|
|
2015-03-21 15:24:48 +01:00
|
|
|
|
2015-03-23 07:48:27 +01:00
|
|
|
73. Cisco Path MTU
|
2015-03-21 15:24:48 +01:00
|
|
|
|
|
|
|
0 1 2 3
|
|
|
|
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
| Data length | Padding |
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
2015-03-28 08:29:59 +01:00
|
|
|
| Padding data ..
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
2015-03-21 15:24:48 +01:00
|
|
|
|
|
|
|
Type: 73
|
|
|
|
Length: >=4
|
2015-03-15 23:07:38 +01:00
|
|
|
|
2015-03-28 12:51:34 +01:00
|
|
|
134. Cisco MWAR Hash Value
|
|
|
|
|
|
|
|
0 1 2 3
|
|
|
|
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
| Hash ...
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
|
|
|
|
Hash: ASCII string witch represents in hexadecimal notation
|
|
|
|
the SHA1 hash of the device certificate.
|
|
|
|
|
2015-03-15 23:07:38 +01:00
|
|
|
|
|
|
|
|