show voice port - Tecnológico de Costa Rica
show voice port - Tecnológico de Costa Rica show voice port - Tecnológico de Costa Rica
4 - 10 Aironet 340 Series Bridge The “Encryption” value may also be set to “mixed’. In this mode a root or repeater bridge will accept association from clients that have encryption turned on or off. In this case only data packets between nodes that both support it will be encrypted. Multicast packets will be sent in the clear so that all nodes may see them. CAUTION: We do not recommend the use of “mixed” mode. If a client with encryption enabled sends a multicast packet to its parent, the packet will be encrypted. The parent will then decrypt the packet and re-transmit it in the clear to the cell for the other nodes to see. Seeing a packet in both encrypted and un-encrypted form can greatly aid in breaking a key. This mode is only included for compatibility with other vendors. The 802.11 protocol specifies a procedure in which a client must authenticate with a parent before it can associate. The “open” method of authentication is essentially a null operation. All clients will be allowed to authenticate. With the “shared key” the parent send the client a challenge text which the client encrypts and sends back to the parent. If the parent can de-crypt it correctly the client is authenticated. CAUTION: With the “shared-key” mode, since a clear text and encrypted version of the same data is transmitted on the air, we again do not recommend its use. It does not really gain you anything, since if the user’s key is wrong the unit will not be able to de-crypt any of his packets and they cannot gain access to the network. The “Client” option determines the authentication mode that the client nodes are allowed to use to associate to the unit. The values allowed are “open”, “shared-key”, or “both”. The “Auth” is used on repeater bridges to determine which authentication mode the unit will use to connect with its parent. The allowed values are “open” or “shared-key”.
Configuring the Radio Network 4 - 11 Using the Configuration Radio LinkTests Menu The options in this menu can be used to determine system performance on individual nodes as well as individual node radio performance. Configuration Radio Linktests Menu Option Value Description 1 - Strength - Run a signal strength test 2 - Carrier - Carrier busy statistics 3 - Multicast - Run a multicast echo test 4 - Unicast - Run a unicast echo test 5 - Remote - Run a remote echo test 6 - Destination [ any ] - Target address 7 - Size [ 512 ] - Packet size 8 - Count [ 100 ] - Number of packets to send 9 - Rate [ auto ] - Data rate 01 - Errors - Radio error statistics 02 - Autotest [ once ] - Auto echo test 03 - Continuous [ 0 ] - Repeat echo test once started Enter an option number or name, “=” main menu, previous menu >_ Running a Signal Strength Test (Strength) The strength option sends a packet once per second to our parent access point and each node in the association table. This packet is echoed back to the Aironet 340 Series Bridge which records and displays the RF signal strength associated with that particular node. It can be used to quickly check the link to each radio partner or could be monitored while aligning directional antennas between two nodes. As the antennas are moved, the signal strength could be monitored until the maximum value is achieved. SIGNAL LEVELS BRxxxx 00409611d1e5 Strength In ******************************* Out ********************************** (^C to exit) |--------------------------------| Running a Carrier Busy Test The Carrier option can be used to determine the amount of activity on each of the available frequencies. Its main use is to pick an unused frequency or to check for the presence of a jammer.
- Page 307 and 308: xii Aironet 340 Series Bridge Welco
- Page 309 and 310: xiv Aironet 340 Series Bridge Radio
- Page 311 and 312: xvi Aironet 340 Series Bridge Paren
- Page 313 and 314: xviii Aironet 340 Series Bridge The
- Page 315 and 316: Part 1 - Getting Started Part 1 - G
- Page 317 and 318: 1 - 2 Aironet 340 Series Bridge Bef
- Page 319 and 320: 1 - 4 Aironet 340 Series Bridge 2.
- Page 321 and 322: 1 - 6 Aironet 340 Series Bridge Ins
- Page 323 and 324: 1 - 8 Aironet 340 Series Bridge Att
- Page 325 and 326: 1 - 10 Aironet 340 Series Bridge Ty
- Page 327 and 328: Chapter 2 - Accessing the Console S
- Page 329 and 330: Sub-Menus Each menu contains the fo
- Page 331 and 332: Accessing the Console System 2 - 5
- Page 333 and 334: Web Access Accessing the Console Sy
- Page 335 and 336: Accessing the Console System 2 - 9
- Page 337 and 338: Using the Configuration Console Men
- Page 339 and 340: Controlling SNMP access to the conf
- Page 341 and 342: Setting the Communication Port Para
- Page 343 and 344: Monitoring of the DTR Signal Access
- Page 345 and 346: Chapter 3 - Before You Begin CHAPTE
- Page 347 and 348: Before You Begin 3 - 3 Time: Used t
- Page 349 and 350: Chapter 4 - Configuring the Radio N
- Page 351 and 352: Using the Configuration Radio Menu
- Page 353 and 354: Configuring the Radio Network 4 - 5
- Page 355 and 356: Configuring the Radio Network 4 - 7
- Page 357: Packet Encryption (Privacy Menu) Co
- Page 361 and 362: Configuring the Radio Network 4 - 1
- Page 363 and 364: Viewing Errors (Errors) Configuring
- Page 365 and 366: Configuring the Radio Network 4 - 1
- Page 367 and 368: Roaming Notification Mode (Roaming)
- Page 369 and 370: Chapter 5 - Configuring the Etherne
- Page 371 and 372: Configuring the Ethernet Port 5 - 3
- Page 373 and 374: 6 - 2 Aironet 340 Series Bridge Usi
- Page 375 and 376: 6 - 4 Aironet 340 Series Bridge 2.
- Page 377 and 378: Chapter 7 - Configuring Mobile IP C
- Page 379 and 380: Configuring Mobile IP 7 - 3 On a fo
- Page 381 and 382: Configuring Mobile IP 7 - 5 work. T
- Page 383 and 384: Chapter 8 - Using the Spanning Tree
- Page 385 and 386: Understanding Loops Using the Spann
- Page 387 and 388: Using the Spanning-Tree Protocol 8
- Page 389 and 390: Establishing Timeouts Node Address
- Page 391 and 392: Using the Configuration STP Menu (R
- Page 393 and 394: Using the Spanning-Tree Protocol 8
- Page 395 and 396: Using the Spanning-Tree Protocol 8
- Page 397 and 398: Setting the Local Port Priority (Pr
- Page 399 and 400: Viewing the Port State (State) Usin
- Page 401 and 402: Chapter 9 - Viewing Statistics CHAP
- Page 403 and 404: Throughput Statistics (Throughput)
- Page 405 and 406: Error Statistics Viewing Statistics
- Page 407 and 408: Displaying Overall Status (Status)
4 - 10 Aironet 340 Series Bridge<br />
The “Encryption” value may also be set to “mixed’. In this mo<strong>de</strong> a root<br />
or repeater bridge will accept association from clients that have encryption<br />
turned on or off. In this case only data packets between no<strong>de</strong>s that<br />
both sup<strong>port</strong> it will be encrypted. Multicast packets will be sent in the<br />
clear so that all no<strong>de</strong>s may see them.<br />
CAUTION: We do not recommend the use of “mixed” mo<strong>de</strong>. If a client with<br />
encryption enabled sends a multicast packet to its parent, the packet will<br />
be encrypted. The parent will then <strong>de</strong>crypt the packet and re-transmit it in<br />
the clear to the cell for the other no<strong>de</strong>s to see. Seeing a packet in both<br />
encrypted and un-encrypted form can greatly aid in breaking a key. This<br />
mo<strong>de</strong> is only inclu<strong>de</strong>d for compatibility with other vendors.<br />
The 802.11 protocol specifies a procedure in which a client must authenticate<br />
with a parent before it can associate. The “open” method of<br />
authentication is essentially a null operation. All clients will be allowed<br />
to authenticate. With the “shared key” the parent send the client a challenge<br />
text which the client encrypts and sends back to the parent. If the<br />
parent can <strong>de</strong>-crypt it correctly the client is authenticated.<br />
CAUTION: With the “shared-key” mo<strong>de</strong>, since a clear text and encrypted<br />
version of the same data is transmitted on the air, we again do not recommend<br />
its use. It does not really gain you anything, since if the user’s key<br />
is wrong the unit will not be able to <strong>de</strong>-crypt any of his packets and they<br />
cannot gain access to the network.<br />
The “Client” option <strong>de</strong>termines the authentication mo<strong>de</strong> that the client<br />
no<strong>de</strong>s are allowed to use to associate to the unit. The values allowed are<br />
“open”, “shared-key”, or “both”.<br />
The “Auth” is used on repeater bridges to <strong>de</strong>termine which authentication<br />
mo<strong>de</strong> the unit will use to connect with its parent. The allowed values<br />
are “open” or “shared-key”.
Change language