User manual SMC 2582W-B

[. . . ] However, no responsibility is assumed by SMC for its use, nor for any infringements of patents or other rights of third parties which may result from its use. No license is granted by implication or otherwise under any patent or patent rights of SMC. SMC reserves the right to change specifications at any time without notice. 38 Tesla Irvine, California 92618 All rights reserved. Trademarks SMC is a registered trademark; and EliteConnect is a trademark of SMC Networks. [. . . ] The relationships among the operational modes and the wireless link types are shown in the following table: Table 2. From the table, a WDS link can be establish between two APs, a BM-BS link can be established between a Bridge Master and a Bridge Slave, but no wireless link can be established between a Bridge Slave and an AP. 3. 3. 2. On this page, you can change the user name and password for the right to modify the configuration of the SMC2582W-B. The new password must be typed twice for confirmation. 3. 3. 3. Firmware management operations for the SMC2582W-B include firmware upgrade, configuration backup, configuration restore, and configuration reset. Firmware upgrade, configuration 26 backup, and configuration restore can be achieved via HTTP or TFTP. The HTTP-based way is suggested because it's more user-friendly. However, due to different behavior of different Web browser types and versions, HTTP-based firmware management operations may not work properly with some Web browsers. If you cannot successfully perform HTTP-based firmware management operations with your Web browser, try the TFTP-based method. 3. 3. 3. 1. Click Browse and then select a correct firmware . bin file. The firmware file path will be shown in the Firmware file name text box. 3. The configuration file is named by the SMC2582W-B's MAC address. For example, if the SMC2582W-B's MAC address is 00-01-02-33-44-55, the configuration backup file should be "000102334455. hex" Don't change the configuration file name in the Save As dialog box. NOTE: The procedure may be a little different with different Web browsers. Fig. Configuration restore by HTTP. 27 To restore configuration of the SMC2582W-B by HTTP: 1. Click Browse and then select a correct configuration . hex file. You have to make sure the file name is the SMC2582W-B's MAC address. The firmware file path will be shown in the Firmware file name text box. Click Restore to upload the configuration file to the SMC2582W-B. 3. 3. 3. 3. When use TFTP as the firmware management protocol, you can configure settings for the SMC2582W-B's TFTP client to communicate with a TFTP server. If the TFTP client does not get a response from the TFTP server within a period specified by the Timeout setting, it will resend the previous request. The Max number of retries setting specifies the maximal number of resend before the TFTP client stops communicating with the TFTP server. The SMC2582W-B Installation CD includes a TFTP server program (TftpSrvr. exe) for firmware upgrade. Run this program on the computer that serves as a TFTP server. Fig. Get a computer that will be used as a TFTP server and as a managing computer to trigger the upgrade process. Connect the computer and one of the LAN Ethernet switch port with a normal Ethernet cable. Configure IP address of the computer so that the SMC2582W-B and the computer are in the same IP subnet. [. . . ] · Are the IP address of the client computer and the IP address of the SMC2582W-B in the same IP subnet?· Use WinIPCfg. exe or IPConfig. exe to see the current IP address of the client computer. Make sure the IP address of the client computer and the IP address of the SMC2582W-B are in the same IP subnet. · TIP: If you forget the current IP address of the SMC2582W-B, use Wireless Router/AP Browser to get the information (see Appendix B-3). · The default gateway of the client computer does not respond to ping from the client computer. 46 · Solve the preceding problem first. · Are the IP address of the SMC2582W-B and the IP address of the client computer in the same IP subnet? [. . . ]