Intellinet 520638 User Manual

Download

Wireless Broadband (Switch) Router

Standard/Pro/Advanced/Advanced+

User’s Guide

Version: 2.10

Last Updated: 01/17/2003

Federal Communication Commission Interference Statement

This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiated radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one of the following measures:

Reorient or relocate the receiving antenna. 



Increase the separation between the equipment and receiver.



Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.



Consult the dealer or an experienced radio/TV technician for help.

FCC Caution: To assure continued compliance, (example – use only shielded interface cables when connecting to computer or peripheral devices). Any changes or modifications not expressly approved by the party responsible for compliance could void the user’s authority to operate this equipment.

FCC Radiation Exposure Statement

This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with minimum distance 20 cm between the radiator & your body.

This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.

R&TTE Compliance Statement

This equipment complies with all the requirements of DIRECTIVE 1999/5/CE OF THE EUROPEAN PARLIAMENT AND THE COUNCIL OF 9 March 1999 on radio equipment and telecommunication terminal equipment and the mutual recognition of their conformity (R&TTE).

The R&TTE Directive repeals and replaces in the directive 98/13/EEC (Telecommunications Terminal Equipment and Satellite Earth Station Equipment) as of April 8,2000.

Safety

This equipment is designed with the utmost care for the safety of those who install and use it. However, special attention must be paid to the dangers of electric shock and static electricity when working with electrical equipment. All guidelines of this and of the computer manufacture must therefore be allowed at all times to ensure the safe use of the equipment.

EU Countries Intended for Use

The ETSI version of this device is intended for home and office use in Austria, Belgium, Denmark, Finland, France (with Frequency channel restrictions), Germany, Greece, Ireland, Italy, Luxembourg, Portugal, Spain, Sweden, The Netherlands, and United Kingdom.

The ETSI version of this device is also authorized for use in EFTA member states Norway and Switzerland.

EU Countries Not Intended for Use

None.

Potential Restrictive Use

France: only channels 10, 11, 12, and 13.

Table of Contents

1. Introduction ......................................................................................................................... 1

1.1. Overview...................................................................................................................1

1.2. Features.................................................................................................................... 1

1.3. Feature Comparison ................................................................................................. 4

2. First-Time Installation and Configuration ............................................................................ 5

2.1. Inserting the Accompanying PCMCIA WLAN Card .................................................. 5

2.2. Selecting a Power Supply Method............................................................................ 5

2.3. Mounting the Wireless Broadband Router on a Wall................................................ 5

2.4. Preparing for Configuration....................................................................................... 6

2.4.1. Connecting the Managing Computer and the Wireless Broadband (Switch)

Router....................................................................................................................... 7

2.4.2. Changing the TCP/IP Settings of the Managing Computer ............................ 8

2.5. Configuring the Wireless Broadband (Switch) Router .............................................. 8

2.5.1. Entering the User Name and Password ......................................................... 8

2.5.2. ConfigWizard Step 1: Selecting an Operational Mode ................................. 10

2.5.3. ConfigWizard Step 2: Configuring TCP/IP Settings...................................... 11

2.5.4. ConfigWizard Step 3: Configuring IEEE 802.11 Settings ............................. 13

2.5.5. ConfigWizard Step 4: Reviewing and Applying Settings .............................. 14

2.6. Deploying the Wireless Broadband (Switch) Router............................................... 15

2.6.1. Connecting the Wireless Broadband (Switch) Router to Ethernet Client

Computers .............................................................................................................. 15

2.6.2. Connecting the Wireless Broadband (Switch) Router to a Modem .............. 15

2.7. Setting up Client Computers................................................................................... 16

2.7.1. Configuring IEEE 802.11b-Related Settings ................................................ 16

2.7.2. Configuring TCP/IP-Related Settings ........................................................... 16

2.8. Confirming the Settings of the Wireless Broadband (Switch) Router and Client

Computers ..................................................................................................................... 17

2.8.1. Checking if the IEEE 802.11b-Related Settings Work.................................. 17

2.8.2. Checking if the TCP/IP-Related Settings Work ............................................ 17

2.9. Installing the Print Client Components (Switch Router).......................................... 18

3. Using Web-Based Network Manager................................................................................ 19

3.1. Overview................................................................................................................. 19

3.1.1. Menu Structure ............................................................................................. 19

3.1.2. Save, Save & Restart, and Cancel Commands............................................ 20

3.1.3. Home and Refresh Commands .................................................................... 21

3.2. Seeing Status ......................................................................................................... 21

3.2.1. Associated Wireless Clients ......................................................................... 21

3.2.2. Current DHCP Mappings.............................................................................. 22

3.2.3. System Log................................................................................................... 22

3.3. General Operations ................................................................................................ 23

3.3.1. Specifying Operational Mode ....................................................................... 23

3.3.2. Changing Password ..................................................................................... 24

3.3.3. Managing Firmware...................................................................................... 24

3.4. Configuring TCP/IP Related Settings ..................................................................... 27

3.4.1. Addressing.................................................................................................... 27

3.4.2. DNS Proxy.................................................................................................... 31

3.4.3. NAT Server................................................................................................... 32

3.4.4. DHCP Server................................................................................................ 35

3.5. Configuring IEEE 802.11b-Related Settings........................................................... 36

3.5.1. Communication............................................................................................. 36

3.5.2. Security......................................................................................................... 38

3.5.3. IEEE 802.1x/RADIUS ................................................................................... 40

iii

3.6. Configuring Advanced Settings .............................................................................. 42

3.6.1. Filters and Firewall ....................................................................................... 42

3.6.2. Management................................................................................................. 44

Appendix A............................................................................................................................ 46

A-1: Default Settings...................................................................................................... 46

A-2: LED Definitions ...................................................................................................... 47

Appendix B: Troubleshooting................................................................................................ 49

B-1: Wireless Settings Problems ................................................................................... 49

B-2: TCP/IP Settings Problems ..................................................................................... 50

B-3: Unknown Problems ................................................................................................ 52

1. Introduction

1.1. Overview

The wireless broadband (switch) router enables IEEE 802.11b and Ethernet client computers to share an Internet connection provided by an Internet service provider (ISP). The Internet connection can be DSL, cable, V.90, or ISDN-based. In addition, it also serves as a wireless access point, so that the wireless client computers and the Ethernet client computers can reach one another.

There are 4 different model variations, Standard, Pro, Advanced, and Advanced+, which are classified in terms of features. The Standard edition provides the fewest features while the Advanced+ edition provides the most. With the sleek Web-based user interface and Windows-based user interface (Wireless Network Manager), a network administrator can easily and clearly manage the wireless broadband (switch) router.

Since the wireless broadband (switch) router provides rich TCP/IP and WLAN (Wireless Local Area Network) functionality, a basic understanding of the inner workings of TCP/IP and IEEE 802.11b is necessary. Essential TCP/IP concepts include IP addressing, IP routing, IP name resolution, DHCP (Dynamic Host Configuration Protocol), and PPP (Point-to-Point Protocol). Essential IEEE 802.11b concepts include channel numbers and WEP (Wired Equivalent Privacy).

In Chapter 2, we describe the steps to install and configure a newly acquired wireless broadband (switch) router. Following the steps, the wireless broadband (switch) router can be quickly set up to work. In Chapter 3, detailed explanations of each Web management page are given for the user to understand how to fine-tune the settings of a wireless broadband router to meet his or her specific needs. In the remainder of this guide, a wireless broadband (switch) router is often referred to as a WIASA (Wireless Internet Access Server Appliance) for short.

1.2. Features



Configuration Reset. Resetting the configuration settings to factory-set values.



IEEE 802.11b



Access point. Bridging packets between the wireless IEEE 802.11b network interface and the wired Ethernet LAN interface.



64-bit and 128-bit WEP (Wired Equivalent Privacy). For authentication and data encryption.



Enabling/disabling SSID broadcasts. The administrator can enable or disable the SSID broadcasts functionality for security reasons. When the SSID broadcasts functionality is disabled, a client computer cannot connect to the wireless router with an “any” network name (SSID, Service Set ID); the correct SSID has to be specified on client computers.



MAC-address-based access control. Blocking unauthorized wireless client computers based on MAC (Media Access Control) addresses.



IEEE 802.1x/RADIUS. User authentication and dynamic encryption key distribution can be achieved by IEEE 802.1x Port-Based Network Access Control and RADIUS (Remote Authentication Dial-In User Service).

Repeater. A wireless router can communicate with other wireless APs/routers via WDS



(Wireless Distribution System). Therefore, a wireless router can wirelessly forward packets from wireless clients to another wireless AP/router, and then the later AP/router forwards the packets to the Ethernet network.



Wireless client isolation. Wireless-to-wireless traffic can be blocked so that the wireless clients cannot see each other. This capability can be used in hotspots applications to prevent wireless hackers from attacking other wireless users’ computers.



AP load balancing. Several wireless APs/routers can form a load-balancing group. Within a group, wireless client associations and traffic load can be shared among the wireless APs/routers.



Transmit power control. Transmit power of the wireless router’s RF module can be adjusted to change RF coverage of the wireless router.



Replaceable antennas. The factory-mounted antennas can be replaced with high-gain antennas for different purposes.



Showing associated wireless clients. Showing the status of all wireless clients that are associated with the wireless router.



Internet Connection Sharing



DNS proxy. The wireless router can forward DNS (Domain Name System) requests from client computers to DNS servers on the Internet. And DNS responses from the DNS servers can be forwarded back to the client computers.

Static DNS mappings. The administrator can specify static FQDN (Fully Quali-



fied Domain Name) to IP address mappings. Therefore, a host on the internal network can access a server also on the intranet by a registered FQDN.



DHCP server. The wireless router can automatically assign IP addresses to client computers by DHCP (Dynamic Host Configuration Protocol).



Static DHCP mappings. The administrator can specify static IP address to MAC address mappings so that the specified IP addresses are always assigned to the hosts with the specified MAC addresses.



Showing current DHCP mappings. Showing which IP address is assigned to which host identified by an MAC address.



NAT server. Client computers can share a public IP address provided by an ISP (Internet Service Provider) by NAT (Network Address Translation). And our NAT server functionality supports the following:



Virtual server. Exposing servers on the intranet to the Internet.



PPTP, IPSec, and L2TP passthrough. Passing VPN (Virtual Private Network) packets through the intranet-Internet boundary. PPTP means Point-to-Point Tunneling Protocol, IPSec means IP Security, and L2TP means Layer 2 Tunneling Protocol.



DMZ (DeMilitarized Zone). All unrecognized IP packets from the Internet can be forwarded to a specific computer on the intranet.

Multiple public IP addresses support. An ISP may provide several public IP



addresses to a customer. The wireless router can map each of the public IP addresses to a host with a private IP address on the intranet.



H.323 passthrough. Passing H.323 packets through the intranet-Internet boundary so that users on the intranet can use VoIP (Voice over IP) applications.



MSN Messenger support. Supporting Microsoft MSN Messenger for chat, file transfer, and real-time communication applications.

  DSL/Cable Modem Support. Supporting dynamic IP address assignment by PPPoE

(Point-to-Point Protocol over Ethernet) or DHCP and static IP address assignment.

Telstra BigPond support. Supporting Telstra BigPond (http://www.bigpond.com user authentication on the cable-based Internet connection service.



V.90/ISDN Modem Support. Supporting PPP (Point-to-Point Protocol) dial-up networking over RS232.



Auto-dial. When the wireless router detects outgoing packets to the Internet, it dials up to the ISP automatically. This functionality applies to PPP and PPPoE.



Network Security



Packet address and port filtering. Filtering outgoing packets based on IP address and port number. (Incoming packet filtering is performed by NAT.)



URL filtering. Preventing users from accessing unwelcome Web sites. The HTTP (HeperText Transfer Protocol) traffic to the specified Web sites identified by URLs (Universal Resource Locators) is blocked.



WAN ICMP requests blocking. Some DoS (Denial of Service) attacks are based on ICMP requests with large payloads. Such kind of attacks can be blocked.



Stateful Packet Inspection (SPI). Analyzing incoming and outgoing packets based on a set of criteria for abnormal content. Therefore, SPI can detect hacker attacks, and can summarily reject an attack if the packet fits a suspicious profile.

) for



Printer Sharing. The wireless broadband switch router can serve as a print server for Windows 9x/2000 client computers.



Changeable MAC Address of the Ethernet WAN Interface. Some ADSL modems work only with Ethernet cards provided by the ISP. If a wireless router is used in such an environment, the MAC address of the WAN interface of the router has to be changed to the MAC address of the ISP-provided Ethernet network card.



Firmware Tools



Firmware upgrade. The firmware of the wireless router can be upgraded, so that more features can be added in the future.



Xmodem-based. Upgrading firmware over RS232.



TFTP-based. Upgrading firmware by TFTP (Trivial File Transfer Protocol).



Configuration backup. The configuration settings of the wireless router can be backed



Management



up to a file via TFTP for later restoring.

Windows-based Wireless Network Manager for configuring, monitoring, and diagnosing the local computer and neighboring wireless APs/routers. The management protocol is MAC-based.

Web-based Network Manager for configuring and monitoring wireless broadband routers. The management protocol is HTTP (HeperText Transfer Protocol)-based.

Remote Web-based management. The wireless router can be managed from the Internet using a Web browser.

SNMP. SNMP (Simple Network Management Protocol) MIB I, MIB II, IEEE 802.1d, IEEE 802.1x, and Private Enterprise MIB are supported.

UPnP. The wireless router responds to UPnP discovery messages so that a Windows XP user can locate the wireless router in My Network Places and use a Web browser to configure it.



Telnet. The user is enabled to manage the wireless router by using Telnet.



Local system log. System events can be logged and viewed using a Web browser for troubleshooting purposes.



4-Port Ethernet Switch. The wireless broadband switch router provides a 4-port Ethernet switch so that a stand-alone Ethernet hub/switch is not necessary for connecting Ethernet client computers to the router.



Power over Ethernet (optional). Supplying power to a wireless broadband router over an Ethernet cable using PowerDsine (http://www.powerdsine.com pliant in the future). This feature facilitates large-scale wireless LAN deployment.

Hardware Watchdog Timer. If the firmware gets stuck in an invalid state, the hardware



watchdog timer will detect this situation and restart the wireless router. Accordingly, the wireless router can provide continuous services.

) technology (IEEE 802.3af com-

1.3. Feature Comparison

Repeater (Wireless Distribution System) Multiple public IP addresses support Static DNS mappings Telnet IEEE 802.1x/RADIUS SNMP IEEE 802.1x MIB Wireless client isolation AP load balancing

Standard Pro Advanced Advanced+

  

     

 PoE is optional on the wireless broadband router.

Ethernet switching and printer sharing are available only on the wireless broadband switch



router.

2. First-Time Installation and Configuration

2.1. Inserting the Accompanying PCMCIA WLAN Card

For some models, the wireless interface of a WIASA is a WLAN PCMCIA card inserted into the PCMCIA socket labeled Wireless LAN Card. Since a WIASA and its accompanying WLAN PCMCIA card are placed separately within a package, you have to insert the PCMCIA card to the socket of the WIASA after they are taken out of the package. And then, plug the connector of the power adapter to the power jack of the WIASA to power it on.

NOTE: Unless a WIASA is to be packed and moved to a distant place, don’t pluck out the PCMCIA

card from the socket.

2.2. Selecting a Power Supply Method

Optionally, the wireless broadband router can be powered by the supplied power adapter or PoE (Power over Ethernet). The wireless broadband router automatically selects the suitable one depending on your decision.

To power the wireless broadband (switch) router by the supplied power adapter:

1. Plug the power adapter to an AC socket.

2. Plug the connector of the power adapter to the power jack of the wireless broadband (switch)

router.

NOTE: This product is intended to be power-supplied by a Listed Power Unit, marked “Class 2” or

“LPS” and output rated “5V DC, 1 A minimum” or equivalent statement.

To power the wireless broadband router by PoE:

1. Plug one connector of an Ethernet cable to an available port of a PoE hub.

2. Plug the other connector of the Ethernet cable to the LAN/CONFIG port of the wireless broad-

band router.

NOTE: The PoE capability of the bridge is PowerDsine-compatible. Please visit the Web site of Pow-

erDsine for more information (http://www.powerdsine.com).

2.3. Mounting the Wireless Broadband Router on a Wall

If necessary, the wireless broadband router can be mounted on a wall.

1. Stick the accessorial sticker for wall-mounting.

2. Use a φ7.0mm driller to drill a 25mm-deep hole at each of the cross marks.

3. Plug in an accessorial plastic conical anchor in each hole.

4. Screw an accessorial screw in each plastic conical anchor for a proper depth so that the wireless

broadband router can be hung on the screws.

5. Hang the wireless broadband router on the screws.

Fig. 1. Mounting the wireless broadband router on a wall.

2.4. Preparing for Configuration

For you to configure a WIASA, a managing computer with a Web browser is needed. For first-time configuration of a WIASA, an Ethernet network interface card (NIC) should have been installed in the managing computer. For maintenance-configuration of a deployed WIASA, either a wireless computer or a wired computer can be employed as the managing computer.

NOTE: If you are using the browser, Opera, to configure a WIASA, click the menu item File, click

Preferences..., click File types, and edit the MIME type, text/html, to add a file extension “.sht” so

that Opera can work properly with the Web management pages of the WIASA.

Since the configuration/management protocol is HTTP-based, we have to make sure that the IP ad-

dress of the managing computer and the IP address of the managed WIASA are in the same IP subnet. By default (see Appendix A-1, “Default Settings”), the DHCP server functionality of a WI-

ASA is enabled, so that if the managing computer is set to automatically obtain an IP address by DHCP, the condition can be satisfied easily.

2.4.1. Connecting the Managing Computer and the Wireless Broadband (Switch) Router

2.4.1.1. Router

To connect the Ethernet managing computer and the managed router for first-time configuration, you have two choices as illustrated in Fig. 3.

Cross-over

Ethernet

cable

Managing Computer

Normal

Ethernet

cable

Ethernet

Hub/Switch

Normal

Ethernet

cable

Managed

WIASA

Fig. 2. Connecting a managing computer and a wireless broadband router via Ethernet.

You can use either a cross-over Ethernet cable (we have included one in the package) or a switch/hub with 2 normal Ethernet cables. Since the DHCP server functionality is factory-set to be enabled, it’s recommended that there are no other computers connected to the switch/hub, so that you can be 100-percent sure that the WIASA will be the DHCP server of the managing computer.

NOTE: One connector of the Ethernet cable must be plugged into the LAN/CONFIG Ethernet jack

of the WIASA for configuration.

2.4.1.2. Switch Router

Connect the Ethernet managing computer to anyone of the LAN switch ports of the managed WIASA with a normal Ethernet cable (see Fig. 3).

NOTE: There are two types of Ethernet cables—normal and crossover.

Normal

Ethernet

cable

LAN 1-4

Port

Fig. 3. Connecting a managing computer and a wireless broadband switch router via Ethernet.

Since the DHCP server functionality is factory-set to be enabled, it’s recommended that there are no other computers connected to the other Ethernet switch ports of the WIASA, so that you can be

100-percent sure that the WIASA will be the DHCP server of the managing computer.

2.4.2. Changing the TCP/IP Settings of the Managing Computer

Use the Windows Network Control Panel Applet to change the TCP/IP settings of the managing computer, so that the IP address of the computer and the IP address of the WIASA are in the same IP subnet. If the managing computer is originally set a static IP address, you can either change the IP address to 192.168.0.xxx (the default IP address of a WIASA is 192.168.0.1) and the subnet mask to

255.255.255.0 or select an automatically-obtain-an-IP-address option.

NOTE: For some versions of Windows, the computer needs to be restarted for the changes of TCP/IP

settings to take effect.

TIP: After you have connected the managing computer and the WIASA via Ethernet, you can install

Wireless Network Manager on the managing computer and use it to configure the WIASA without being concerned about the TCP/IP settings of the managing computer. Refer to on-line help of Wireless Network Manager for more information.

If the computer is already set to obtain an IP address automatically, you can use the Windows-provided tool, WinIPCfg.exe (on Windows 9x/Me) or IPConfig.exe (on Windows 2000/XP), to re-obtain an IP address from the WIASA. WinIPCfg.exe is a GUI program, and has command buttons for releasing the current IP address and re-obtaining an IP address. IPConfig.exe is a command-line program, and the /release option releases the current IP address and the /renew option triggers the Windows DHCP client subsystem to re-obtain an IP address.

NOTE: By default, the first assignable IP address of the DHCP server on the WIASA is 192.168.0.2.

2.5. Configuring the Wireless Broadband (Switch) Router

After the IP addressing issue is resolved, launch a Web browser on the managing computer. Then, go to “http://192.168.0.1” to access the Web-based Network Manager start page.

NOTE: If you are using the browser, Opera (from Opera Software), to configure a WIASA, click the

menu item File, click Preferences..., click File types, and edit the MIME type, text/html, to add a file extension “.sht” so that Opera can work properly with the Web management pages of the WIASA.

TIP: For maintenance configuration of a WIASA, the WIASA can be reached by its host name using

a Web browser. For example, if the WIASA is named “wiasa”, you can use the URL “http://wiasa” to access the Web-based Network Manager of the WIASA.

2.5.1. Entering the User Name and Password

Before the start page is shown, you will be prompted to enter the user name and password to gain the right to access the Web-based Network Manager. For first-time configuration, use the default user name “root” and default password “root”, respectively.

Fig. 4. Entering the user name and password.

NOTE: It is strongly recommended that the password be changed to other value for security reasons.

On the start page, click the General, Password link to change the value of the password (see Section

3.3.2 for more information).

TIP: Since the start page shows the current settings and status of the WIASA, it can be saved or

printed within the Web browser for future reference.

On the start page, click the ConfigWizard link to use a configuration wizard to quickly change the configuration of the WIASA.

Fig. 5. The Start page.

The first page of the configuration wizard is a welcome page. This page gives a brief description of the configuration process. Click Next to continue. We’ll explain what to do step-by-step in the following subsections.

2.5.2. ConfigWizard Step 1: Selecting an Operational Mode

Fig. 6. Operational modes.

If the WIASA is to be used simply as a wireless-to-Ethernet access point, select Simple Access



Point. In this mode, the Ethernet WAN interface is disabled.



If the WIASA is to be used with a DSL or cable modem and the IP address assignment for the Ethernet WAN interface is achieved by PPPoE, select Router with a PPPoE-Based DSL/Cable Connection.



If the WIASA is to be used with a DSL or cable modem and the IP address assignment for the Ethernet WAN interface is achieved by DHCP, select Router with a DHCP-Based DSL/Cable Connection.



If the WIASA is to be used with a DSL or cable modem and the IP address of the Ethernet WAN interface has to be manually set, select Router with a Static-IP DSL/Cable Connection.



If the WIASA is to be used with a V.90 modem or ISDN TA, select Router with a Dial-up Connection.

NOTE: The LAN interfaces include the IEEE 802.11b wireless LAN interface and the Ethernet LAN

interfaces. These two interfaces share a LAN IP address.

2.5.3. ConfigWizard Step 2: Configuring TCP/IP Settings

2.5.3.1. Simple Access Point

Fig. 7. TCP/IP settings for Simple Access Point mode.

If the WIASA was set to be in Simple Access Point mode, one IP address is needed. This IP address can be manually set or automatically assigned by a DHCP server on the LAN. If you are manually setting the IP address, Subnet mask, and Default gateway settings, set them appropriately, so that they comply with your LAN environment. In addition, you can specify the Host name of the WIASA.

2.5.3.2. Router with a PPPoE-Based DSL/Cable Connection

Fig. 8. TCP/IP settings for Router with a PPPoE-Based DSL/Cable Connection mode.

If the WIASA was set to be in Router with a PPPoE-Based DSL/Cable Connection mode, two IP addresses are needed—one for the Ethernet/wireless LAN interfaces and the other for the WAN interface. The IEEE 802.11b interface and the Ethernet LAN interface share the LAN IP address. The LAN IP address must be set manually to a private IP address, say 192.168.0.xxx. The default LAN IP address is 192.168.0.1 and the default subnet mask is 255.255.255.0. In most cases, these default set- tings need no change.

As for the WAN IP address, it is obtained automatically by PPPoE from the ISP. Consult your ISP for the correct User name, Password, and Service name settings.

The WIASA automatically disconnects the PPPoE connection after there has been no traffic to the Internet for a period specified by Idle disconnect time.

NOTE: If Idle disconnect time is set to 0, the PPPoE connection will not be disconnected.

2.5.3.3. Router with a DHCP-Based DSL/Cable Connection

Fig. 9. TCP/IP settings for Router with a DHCP-Based DSL/Cable Connection mode.

If the WIASA was set to be in Router with a DHCP-Based DSL/Cable Connection mode, two IP addresses are needed—one for the Ethernet/wireless LAN interfaces and the other for the WAN interface. The IEEE 802.11b interface and the Ethernet LAN interface share the LAN IP address. The LAN IP address must be set manually to a private IP address, say 192.168.0.xxx. The default LAN IP address is 192.168.0.1 and the default subnet mask is 255.255.255.0. In most cases, these default set- tings need no change.

As for the WAN IP address, it is obtained automatically by DHCP from the ISP. If you are using Telstra BigPond cable-based Internet service, select the Connect with BigPond Cable check box and specify the User name, Password, and the IP address of your Login server, which is provided by your ISP.

2.5.3.4. Router with a Static-IP DSL/Cable Connection

Fig. 10. TCP/IP settings for Router with a Static-IP DSL/Cable Connection mode.

If the WIASA was set to be in Router with a Static-IP DSL/Cable Connection mode, two IP addresses are needed—one for the Ethernet/wireless LAN interfaces and the other for the WAN interface. The IEEE 802.11b interface and the Ethernet LAN interface share the LAN IP address. The LAN IP address must be set manually to a private IP address, say 192.168.0.xxx. The default LAN IP address is 192.168.0.1 and the default subnet mask is 255.255.255.0. In most cases, these default set-

tings need no change.

As for the WAN IP address, it must be manually set. Consult your ISP for the correct IP address, Default gateway, Subnet mask, Primary DNS server, and Secondary DNS server settings.

2.5.3.5. Router with a Dial-up Connection

Fig. 11. TCP/IP settings for Router with a Dial-up Connection mode.

If the WIASA was set to be in Router with a Dial-up Connection mode, two IP addresses are needed—one for the Ethernet/wireless LAN interfaces and the other for the WAN interface. The IEEE

802.11b interface and the Ethernet LAN interface share the LAN IP address. The LAN IP address

must be set manually to a private IP address, say 192.168.0.xxx. The default IP address is 192.168.0.1 and the default subnet mask is 255.255.255.0. In most cases, these default settings need no change.

As for the WAN IP address, it is obtained automatically by PPP from the ISP. Consult your ISP for the correct User name, Password, and Telephone number settings.

The WIASA automatically disconnects the PPP dial-up connection after there has been no traffic to the Internet for a period specified by Idle disconnect time.

NOTE: If Idle disconnect time is set to 0, the PPP dial-up connection will not be disconnected.

2.5.4. ConfigWizard Step 3: Configuring IEEE 802.11 Settings

IEEE 802.11b-related communication settings include Regulatory domain, Channel number, and Network name (SSID).

Fig. 12. IEEE 802.11b communication settings.

The number of available RF channels depends on local regulations; therefore you have to choose an appropriate regulatory domain to comply with local regulations. The SSID of a wireless client computer and the SSID of the WIASA must be identical for them to communicate with each other.

2.5.5. ConfigWizard Step 4: Reviewing and Applying Settings

Fig. 13. Settings changes are highlighted in red.

Fig. 14. Settings review.

On the final page, you can review all the settings you have made. Changes are highlighted in red. If they are OK, click Save & Restart to apply the new settings. Or you can go back to previous pages to

make modifications. Or you can click Cancel to leave the configuration process without any changes.

NOTE: About 7 seconds are needed for the WIASA to complete its restart process.

2.6. Deploying the Wireless Broadband (Switch) Router

After the settings have been configured, deploy the WIASA to the field application environment. Connect Ethernet client computers to the Ethernet switch ports of the WIASA. If the WIASA is configured as a router, also connect a DSL modem, cable modem, V.90 modem, or ISDN TA to the WIASA.

2.6.1. Connecting the Wireless Broadband (Switch) Router to Ethernet Client Computers

2.6.1.1. Router

To connect the router with Ethernet client computers:

1. Plug one connector of a normal Ethernet cable to the LAN/CONFIG Ethernet jack of the WI-

ASA.

2. Plug the other connector of this cable to a free Ethernet port of the switch/hub, to which all the

Ethernet client computers have been connected.

2.6.1.2. Switch Router

To connect the switch router with Ethernet client computers:

1. Plug one connector of a normal (not crossover) Ethernet cable to a LAN Ethernet switch port of

the WIASA, and the other connector to the Ethernet jack of the Ethernet NIC of a client computer.

2. If necessary, use a normal Ethernet cable to connect the WIASA to another Ethernet switch/hub

via the UP-LINK port.

2.6.2. Connecting the Wireless Broadband (Switch) Router to a Modem

To connect the WIASA with a DSL or cable modem:

1. Plug one connector of a crossover Ethernet cable to the Ethernet WAN jack of the WIASA.

2. Plug the other connector of this cable to the Ethernet jack of the DSL or cable modem. Refer to

the user’s manual of the modem if necessary.

TIP: If the WIASA has been connected to the DSL or cable modem successfully, the WAN LED in-

dicator on the housing lights up when both devices are powered on. If not, flip the Normal/Crossover

switch on the side plate of the WIASA (if it exists), flip the switch until the WAN LED indicator lights on.

To connect the WIASA with a V.90 modem or ISDN TA:

1. Plug one connector of a normal RS232 cable to the RS232 (COM) port of the WIASA.

2. Plug the other connector of this cable to the RS232 port of the V.90 modem or ISDN TA. Refer

to the user’s manual of the modem or TA if necessary.

2.7. Setting up Client Computers

Before the client computers can use the services provided by the WIASA, their TCP/IP settings must be configured adequately to match those of the WIASA. Furthermore, for wireless client computers, their IEEE 802.11b-related settings must also match those of the WIASA.

2.7.1. Configuring IEEE 802.11b-Related Settings

Before the TCP/IP networking system of a wireless client computer can communicate with other hosts, the underlying wireless link must be established between this wireless computer and a WIASA.

To establish a wireless link to a WIASA:

1. Launch the configuration/monitoring utility provided by the vendor of the installed WLAN NIC.

2. Use the utility to make appropriate Operating Mode, SSID and WEP settings.

NOTE: A client must be in infrastructure mode, so that it can associate with a wireless access point

or broadband router.

NOTE: The SSID of the wireless client computer and the SSID of the WIASA must be identical. Or,

in case the SSID broadcasts capability of the WIASA is enabled (by default), the SSID of the wire- less client computer could be set to “any”.

NOTE: Both the wireless client computer and the WIASA must have the same WEP settings for them

to communicate with each other.

NOTE: For better wireless security, IEEE 802.1x capability of the WIASA must be enabled so that

only authenticated wireless users can access the wireless network. Refer to the IEEE 802.1x-related white papers on the accompanying CD-ROM for more information about deploying secure WLANs with IEEE 802.1x support.

2.7.2. Configuring TCP/IP-Related Settings

Use Windows Network Control Panel Applet to change the TCP/IP settings of the client computers, so that the IP addresses of the client computers and the IP address of the WIASA are in the same IP subnet.

If a client computer is originally set a static IP address, you can either change its IP address to match the IP address of the WIASA, or select an automatically-obtain-an-IP-address option if the DHCP server functionality of the WIASA is enabled.

NOTE: For some versions of Windows, the computer needs to be restarted for the changes of TCP/IP

settings to take effect.

If the computer is already set to obtain an IP address automatically, you can use the Windows-provided tool, WinIPCfg.exe (on Windows 9x) or IPConfig.exe (on Windows 2000), to re-obtain an IP address from the WIASA. WinIPCfg.exe is a GUI program, and has command buttons for releasing the current IP address and re-obtaining an IP address. IPConfig.exe is a command-line program, and the /release option releases the current IP address and the /renew option triggers the Windows DHCP client subsystem to re-obtain an IP address.

2.8. Confirming the Settings of the Wireless Broadband (Switch) Router and Client Computers

After you have completed deploying the WIASA and setting up client computers, you have to make sure the settings you have made are correct.

2.8.1. Checking if the IEEE 802.11b-Related Settings Work

To check if a wireless client computer can associate with the WIASA:

1. Launch the configuration/monitoring utility provided by the vendor of the installed WLAN NIC.

2. Check if the client computer is associated to an access point, and the access point is the WIASA.

If the check fails, see Appendix B-1, “Wireless Settings Problems” for troubleshooting.

2.8.2. Checking if the TCP/IP-Related Settings Work

To check if a client computer can access the Internet:

1. Open a Windows Command Prompt window on the client computer.

2. Type “ping wiasa”, where wiasa is a placeholder for the IP address of the WIASA. Replace it

with your real IP address—for example, 192.168.0.1. Then press Enter.

If the WIASA responds, go to the next step; else, see Appendix B-2, “TCP/IP Settings Problems” for troubleshooting.

3. Type “ping default_gateway”, where default_gateway is a placeholder for the IP address of the

default gateway of the client computer. Then press Enter.

NOTE: If the WIASA is set to be in router mode, the default gateway of the client computer

should be the WIASA. You can skip this step in this case.

If the gateway responds, go to the next step; else, see Appendix B-2, “TCP/IP Settings Problems” for troubleshooting.

4. Type “ping wiasa_default_gateway”, where wiasa_default_gateway is a placeholder for the IP

address of the default gateway of the WIASA. Then press Enter.

If this gateway responds, go to the next step; else, see Appendix B-2, “TCP/IP Settings Problems” for troubleshooting.

TIP: You can view the default gateway of the WIASA on the start page of the Web-based Net-

work Manager.

NOTE: If the WIASA is set to be in Router with a PPPoE-Based DSL/Cable Connection or

Router with a Dial-up Connection, it needs some time to establish a PPPoE or PPP link to the

ISP. Therefore, this step will fail but the WIASA will be triggered to establish a link to the ISP. Wait for a few seconds, and then try again.

5. Type “ping wiasa_1st_dns_server”, where wiasa_1st_dns_server is a placeholder for the IP ad-

dress of the primary DNS server of the WIASA. Then press Enter.

If this DNS server responds, go to the next step; else, see Appendix B-2, “TCP/IP Settings Problems” for troubleshooting.

TIP: You can view the primary and secondary DNS servers of the WIASA on the start page of

the Web-based Network Manager.

6. Type “ping wiasa_2nd_dns_server”, where wiasa_2nd_dns_server is a placeholder for the IP

address of the secondary DNS server of the WIASA. Then press Enter.

If this DNS server responds the client should have no problem with TCP/IP networking; else, see Appendix B-2, “TCP/IP Settings Problems” for troubleshooting.

2.9. Installing the Print Client Components (Switch Router)

The print server components on the WIASA work in conjunction with the print client components on a client computer, and they communicate through TCP/IP. The print client components expose a vir- tual communication port on the client computer, so that, on the client computer, the driver of the printer must be configured to print to this virtual port. When an application on the client computer is printing, the print data is sent through the virtual port by the print client components to the WIASA. And then, the print data is directed to the printer, which is connected to the parallel port of the WIASA, by the print server components.

To install the print client components on a client computer:

1. Connect the printer to the Printer port of the WIASA with a parallel cable.

2. Insert the companion CD-ROM disk of the WIASA into drive D of the client computer, where

“D” is the name of the CD-ROM drive; substitute the real name of your CD-ROM drive for “D” if necessary.

3. Run “D:\PrntClnt\Setup.exe” on the client computer.

4. Specify the IP address of the WIASA’s LAN interfaces when prompted by the setup program.

5. Restart Windows as prompted by the setup program.

6. Add a new local printer using “Start, Settings, Printers, Add Printer” and select the WIASA

Print Client port for the local printer within the Add New Printer Wizard.

7. Print a test page to check if the client computer can print to the printer that is connected to the

WIASA.

3. Using Web-Based Network Manager

In this chapter, we’ll explain each Web management page of the Web-based Network Manager.

3.1. Overview

Fig. 15. The Start page.

3.1.1. Menu Structure

The left side of the start page contains a menu for you to carry out commands. Here is a brief description of the hyperlinks on the menu:



Home. For going back to the start page.



ConfigWizard. For you to quickly set up the WIASA.



Status. Status information.



Wireless Clients. The status of the wireless clients currently associated with the WIASA.



DHCP Mappings. Current IP-MAC address mappings.



System Log. System events log.



General. Global operations.



Operational Mode. Operational mode of the WIASA based on the type of the Internet connection provided by the ISP.



Password. For gaining right to change the settings of the WIASA.



Firmware Tools. For upgrading the firmware of the WIASA and backing up and restoring configuration settings of the WIASA.



TCP/IP. TCP/IP-related settings.



Addressing. IP addressing settings for the WIASA to work in the TCP/IP networking world, or user name and password provided by the ISP.



DNS Proxy. DNS (Domain Name System) proxy settings.



NAT Server. Settings for the NAT (Network Address Translation) server on the WIASA.



DHCP Server. Settings for the DHCP (Dynamic Host Configuration Protocol) server on the WIASA.



IEEE 802.11. IEEE 802.11b-related settings.



Communication. Basic settings for the IEEE 802.11b interface of the WIASA to work properly with wireless clients.



Security. Security settings for authenticating wireless users and encrypting wireless data.



IEEE 802.1x/RADIUS. IEEE 802.1x Port-Based Network Access Control and RADIUS (Remote Authentication Dial-In User Service) settings for better wireless security.



Advanced. Advanced settings of the WIASA.



Filters & Firewall. Packet filtering and firewall settings for user access control and protection from hacker attacks from the Internet, respectivel



Management. Remote Web-based management, UPnP and SNMP settings.

3.1.2. Save, Save & Restart, and Cancel Commands

Fig. 16. Save, Save & Restart, and Cancel.

At the bottom of each page that contains settings you can configure, there are up to three buttons—Save, Save & Restart, and Cancel. Clicking Save stores the settings changes to the memory of the WIASA and brings you back to the start page. Clicking Save & Restart stores the settings changes to the memory of the WIASA and restarts the WIASA immediately for the settings changes to take effect. Clicking Cancel discards any settings changes and brings you back to the start page.

If you click Save, the start page will reflect the fact that the configuration settings have been changed by showing two buttons—Restart and Cancel. In addition, changes are highlighted in red. Clicking Cancel discards all the changes. Clicking Restart restarts the WIASA for the settings changes to take

effect.

Fig. 17. Settings have been changed.

3.1.3. Home and Refresh Commands

Fig. 18. Home and Refresh.

At the bottom of each status page that shows read-only information, there are two buttons—Home and Refresh. Clicking Home brings you back to the start page. Clicking Refresh updates the shown status information.

3.2. Seeing Status

3.2.1. Associated Wireless Clients

Fig. 19. Status of associated wireless clients.

On this page, the status information of each associated client, including its MAC address, IP address, user name (if the client has been IEEE 802.1x authenticated), number of bytes it has send, number of

bytes it has received, and the time of its last activity, is shown.

3.2.2. Current DHCP Mappings

Fig. 20. Current DHCP mappings.

On this page, all the current static or dynamic DHCP mappings are shown. A DHCP mapping is a correspondence relationship between an IP address assigned by the DHCP server and a computer or device that obtains the IP address. A computer or device that acts as a DHCP client is identified by its MAC address.

A static mapping indicates that the DHCP client always obtains the specified IP address from the DHCP server. You can set static DHCP mappings in the Static DHCP Mappings section of the DHCP Server configuration page (see Section 3.4.4). A dynamic mapping indicates that the DHCP server chooses an IP address from the IP address pool specified by the First allocateable IP address and Allocateable IP address count settings on the DHCP Server configuration page.

3.2.3. System Log

Fig. 21. System log.

System events such as PPPoE dialup results are recorded in the memory of the WIASA. The logged information is useful for troubleshooting purposes.

3.3. General Operations

3.3.1. Specifying Operational Mode

Fig. 22. Operational modes.

On this page, you can specify the operational mode for the WIASA. Currently, 5 modes are available:

Simple Access Point. In this mode, the Ethernet WAN interface is disabled. The WIASA



acts as a bridge between the Ethernet LAN interface and the IEEE 802.11b wireless LAN interface.



Router with a PPPoE-based DSL/Cable Connection. In this mode, the WIASA assumes that a DSL or cable modem is connected to its Ethernet WAN interface. The client computers can therefore share this DSL/cable-based Internet connection by the NAT server functionality. The IP address of the Ethernet WAN interface is obtained automatically by PPPoE from the ISP.



Router with a DHCP-based DSL/Cable Connection. In this mode, the WIASA assumes that a DSL or cable modem is connected to its Ethernet WAN interface. The client computers can therefore share this DSL/cable-based Internet connection by the NAT server functionality. The IP address of the Ethernet WAN interface is obtained automatically by DHCP from the ISP.



Router with a Static-IP DSL/Cable Connection. In this mode, the WIASA assumes that a DSL or cable modem is connected to its Ethernet WAN interface. The client computers can therefore share this DSL/cable-based Internet connection by the NAT server functionality. The IP address of the Ethernet WAN interface must be manually set.



Router with a Dial-up Connection. In this mode, the WIASA assumes that a V.90 modem or ISDN TA is connected to its RS232 (COM) port. The client computers can therefore share this V.90/ISDN-based Internet connection by the NAT server functionality.

TIP: When you have selected the operational mode of the WIASA, go to the TCP/IP, Addressing

section of the management UI (see Section 3.4.1) to configure the addressing settings of the WAN and LAN interfaces.

3.3.2. Changing Password

Fig. 23. Password.

On this page, you can change the user name and password for the right to modify the configuration of the WIASA. The new password must be typed twice for confirmation.

3.3.3. Managing Firmware

3.3.3.1. Upgrading Firmware

Fig. 24. Firmware Upgrade.

The WIASA can be triggered to download updated firmware from a specified TFTP server. On this page, you specify the IP address of the intended TFTP server, and then trigger the WIASA to begin downloading.

Within the folder “Utilities” on the companion CD-ROM disk, we offered a TFTP server program (TftpSrvr.exe) for firmware upgrade. Run this program on the computer that is to serve as a TFTP server.

To upgrade the firmware of WIASA:

1. Get a computer that will be used as a TFTP server and as a managing computer to trigger the

upgrade process.

2. For a wireless broadband router, connect the computer and the LAN/CONFIG Ethernet port

with a crossover Ethernet cable. For a wireless broadband switch router, connect the computer and one of the LAN Ethernet switch port with a normal Ethernet cable.

3. Configure the IP address of the computer so that the computer and the WIASA are in the same

IP subnet.

4. On the computer, run the TFTP Server utility. And specify the folder in which the firmware files

reside.

5. On the computer, run a Web browser and click the General, Firmware Tools hyperlink.

6. Specify the IP address of the computer, which acts as a TFTP server. If you don’t know the IP

address of the computer, open a Command Prompt, and type IpConfig, then press the Enter key.

7. Trigger the firmware upgrade process by clicking Upgrade.

Fig. 25. TFTP Server.

TIP: It’s more convenient to use the Firmware Upgrade Wizard of Wireless Network Manager to up-

grade the firmware of a WIASA.

NOTE: After the dialog box of the TFTP server program appears, be sure to specify the working

folder within which the downloaded firmware files reside.

NOTE: Make sure the Accept read requests check box of TFTP Server is selected.

NOTE: The LAN IP address of the WIASA and the IP address of the TFTP server must be in the

same IP subnet for TFTP to work.

NOTE: Due to the unreliable nature of wireless media, it’s highly recommended that the TFTP server

and the to-be-upgraded WIASA be connected by Ethernet, and on the same LAN, so that the upgrade process would be smooth.

NOTE: After the firmware is upgraded, be sure to delete the contents of the Web browser cache, so

that the Web management pages can be shown correctly.

NOTE: A failed upgrade may corrupt the firmware and make the WIASA unstartable. When this oc-

curs, call for technical support.

3.3.3.2. Backing up and Restoring Configuration Settings

Fig. 26. Configuration backup/restoring.

The WIASA can be triggered to put its configuration settings to a TFTP server so that the configura-

tion is backed up to a file. And then, the file can be restored back to the WIASA by a TFTP server. See the previous section for more information about using the TFTP Server utility bundled with the WIASA.

To back up the configuration of WIASA:

1. Get a computer that will be used as a TFTP server and as a managing computer to trigger the

backup process.

2. For a wireless broadband router, connect the computer and the LAN/CONFIG Ethernet port

with a crossover Ethernet cable. For a wireless broadband switch router, connect the computer and one of the LAN Ethernet switch port with a normal Ethernet cable.

3. Configure the IP address of the computer so that the computer and the WIASA are in the same

IP subnet.

4. On the computer, run the TFTP Server utility. Select the Accept write requests check box, and

specify the folder to which the configuration settings of WIASA will be saved.

5. On the computer, run a Web browser and click the General, Firmware Tools hyperlink.

6. Within the Configuration Backup/Restoring section, specify the IP address of the computer,

which acts as a TFTP server. If you don’t know the IP address of the computer, open a Command Prompt, and type IpConfig, then press the Enter key.

7. Trigger the backup process by clicking Back up. The WIASA’s configuration settings will be

saved as “AaBbCcDdEeFf.hex” by the TFTP server, where “AaBbCcDdEeFf” is the WIASA’s MAC address. For example, if the WIASA’s MAC address is 00-01-02-33-44-55, the configuration backup file will be “000102334455.hex”.

NOTE: Remember to select the Accept write requests check box of TFTP Server.

To restore the configuration of WIASA:

1. Get a computer that will be used as a TFTP server and as a managing computer to trigger the

restoring process.

2. For a wireless broadband router, connect the computer and the LAN/CONFIG Ethernet port

with a crossover Ethernet cable. For a wireless broadband switch router, connect the computer and one of the LAN Ethernet switch port with a normal Ethernet cable.

3. Configure the IP address of the computer so that the computer and the WIASA are in the same

IP subnet.

4. On the computer, run the TFTP Server utility. And specify the folder in which the configuration

backup file resides. A configuration back file is normally named by the WIASA’s MAC address. For example, if the WIASA’s MAC address is 00-01-02-33-44-55, the configuration backup file should be “000102334455.hex”.

5. On the computer, run a Web browser and click the General, Firmware Tools hyperlink.

6. Within the Configuration Backup/Restoring section, specify the IP address of the computer,

which acts as a TFTP server. If you don’t know the IP address of the computer, open a Command Prompt, and type IpConfig, then press the Enter key.

7. Trigger the restoring process by clicking Restore. The WIASA will then download the configu-

ration backup file from the TFTP server.

NOTE: Make sure the file is a valid configuration backup file for the WIASA.

3.4. Configuring TCP/IP Related Settings

3.4.1. Addressing

The addressing settings depend on the operational mode of the WIASA. Each operational mode requires different addressing settings.

3.4.1.1. Simple Access Point

Fig. 27. TCP/IP settings for Simple Access Point mode.

3.4.1.2. Router with a PPPoE-Based DSL/Cable Connection

Fig. 28. TCP/IP settings for Router with a PPPoE-Based DSL/Cable Connection mode.

As for the WAN IP address, it is obtained automatically by PPPoE from the ISP. Consult your ISP for the correct User name, Password, and Service name settings.

Custom MAC Address of WAN Interface enables you to change the MAC address of the Ethernet WAN interface. Therefore, if the ISP-provided DSL or cable modem works only with the ISP-provided Ethernet card for a computer, the WAN interface of the WIASA can mimic the ISP-provided Ethernet card by changing its MAC address to the Ethernet card’s MAC address.

The WIASA automatically disconnects the PPPoE connection after there has been no traffic to the Internet for a period specified by Idle disconnect time.

NOTE: If Idle disconnect time is set to 0, the PPPoE connection will not be disconnected.

3.4.1.3. Router with a DHCP-Based DSL/Cable Connection

Fig. 29. TCP/IP settings for Router with a DHCP-Based DSL/Cable Connection mode.

3.4.1.4. Router with a Static-IP DSL/Cable Connection

Fig. 30. TCP/IP settings for Router with a Static-IP DSL/Cable Connection mode.

If the WIASA was set to be in Router with a Static-IP DSL/Cable Connection mode, two IP addresses are needed—one for the Ethernet/wireless LAN interfaces and the other for the WAN interface. The IEEE 802.11b interface and the Ethernet LAN interface share the LAN IP address. The LAN IP address must be set manually to a private IP address, say 192.168.0.xxx. The default LAN IP address is 192.168.0.1 and the default subnet mask is 255.255.255.0. In most cases, these default set- tings need no change.

As for the WAN IP address, it must be manually set. Consult your ISP for the correct IP address,

Default gateway, Subnet mask, Primary DNS server, and Secondary DNS server settings.

Custom MAC Address of WAN Interface enables you to change the MAC address of the Ethernet

WAN interface. Therefore, if the ISP-provided DSL or cable modem works only with the ISP-provided Ethernet card for a computer, the WAN interface of the WIASA can mimic the ISP-provided Ethernet card by changing its MAC address to the Ethernet card’s MAC address.

3.4.1.5. Router with a Dial-up Connection

Fig. 31. TCP/IP settings for Router with a Dial-up Connection mode.

If the WIASA was set to be in Router with a Dial-up Connection mode, two IP addresses are needed—one for the Ethernet/wireless LAN interfaces and the other for the WAN interface. The IEEE

802.11b interface and the Ethernet LAN interface share the LAN IP address. The LAN IP address

As for the WAN IP address, it is obtained automatically by PPP from the ISP. Consult your ISP for the correct User name, Password, and Telephone number settings.

The WIASA automatically disconnects the PPP dial-up connection after there has been no traffic to the Internet for a period specified by Idle disconnect time.

NOTE: If Idle disconnect time is set to 0, the PPP dial-up connection will not be disconnected.

The AT commands settings are for modem compatibility. The default AT commands for dial-up and hang-up are suitable for most modems. However, if your modem or TA needs special AT commands for these purposes, set them in the corresponding fields. You may need to consult the manual of the modem or TA for proper AT commands.

3.4.2. DNS Proxy

The DNS Proxy component of the WIASA forwards DNS requests and reply messages between client computers and DNS servers. To client computers, the WIASA acts like a DNS server; to DNS servers, the WIASA acts like a client.

3.4.2.1. Basic

Fig. 32. Basic DNS proxy settings.

In this section of the page, you can specify the IP addresses of the DNS servers, when the WIASA is in Router with a Static-IP DSL/Cable Connection mode. In other modes, the WIASA obtains the DNS server information automatically from the ISP.

3.4.2.2. Static DNS Mappings

Fig. 33. Static DNS mappings.

By Static DNS Mappings, an internal server can be given a domain name, so that other hosts on the intranet can access the server by its domain name instead of by its IP address. For example, an internal Web server for the intranet, say 192.168.0.2, may be associated with the domain name, www.wiasa.com.

To give an internal server a domain name:

1. Specify the domain name and the private IP address of the internal server.

2. Select the corresponding Enabled check box for the internal server.

3.4.3. NAT Server

3.4.3.1. Basic

Fig. 34. Basic NAT server settings.

When the WIASA is in Router with a Static-IP DSL/Cable Connection mode, the NAT server functionality can be enabled or disabled.

A DMZ (DeMilitarized Zone) host receives all unrecognized TCP/IP packets from the NAT server on the WIASA; therefore TCP/IP networking applications running on the DMZ host would have better compatibility with NAT.

To specify the DMZ host:

Enter the private IP address of the computer to be used as a DMZ host, and select the corre-



sponding check box.

3.4.3.2. Static NAT Mappings

Fig. 35. Static NAT mappings.

An ISP may provide more than one public IP address to its customer. A customer could use each of the public IP addresses for one type of server to be accessed from the Internet. This requirement can be satisfied by Static NAT Mappings. This functionality can be enabled only when the WIASA is in Router with a Static-IP DSL/Cable Connection mode.

For example, say an ISP provides 5 public IP addresses, 61.16.33.114 to 61.16.33.118 inclusive, to its customer, WIASA Technology. The network administrator of WIASA Technology decides to use

61.16.33.114 for the wireless broadband router, 61.16.33.115 for their public Web server, and

61.16.33.116 for their public POP3 server. And the administrator has registered with InterNIC (Inter-

net Network Information Center) some domain name-to-IP address mappings—www.wiasa.com to

61.16.33.115 and pop3.wiasa.com to 61.16.33.116. However, the public Web server and POP3 server

for WIASA Technology sit on the intranet and use private IP addresses, 192.168.0.2 and 192.168.0.3, respectively. To expose the servers in this situation, the network administrator needs two static NAT mappings to associate 61.16.33.115 with 192.168.0.2 and 61.16.33.116 with 192.168.0.3, respectively.

To associate a public IP address with a private IP address:

1. Specify the public IP address and the private IP address for the association.

2. Select the corresponding Enabled check box.

3.4.3.3. Virtual Server Mappings

Fig. 36. Virtual server mappings.

The WIASA enables you to expose internal servers on the intranet through NAT to the Internet for public use. The exposed internal servers are called virtual servers because from perspective of hosts on the Internet, these servers are invisible in terms of TCP/IP.

To expose “preset” internal servers:

1. Select the corresponding Enabled check boxes for the kinds of servers (FTP, IMAP4, SMTP,

POP3, TELNET, and HTTP) you want to expose.

2. Specify the private IP addresses of the internal servers.

To expose other internal servers:

1. Specify the Service Name, Private IP Address, Port Number, and whether the service is

TCP-based or UDP-based for a non-preset internal server you want to expose.

2. Select the corresponding Enabled check box for the internal server.

3. Repeat Steps 1 to 2 for other non-preset internal servers.

3.4.4. DHCP Server

3.4.4.1. Basic

Fig. 37. Basic DHCP server settings.

The WIASA can automatically assign IP addresses to client computers by DHCP. In this section of the management page, you can specify the Default gateway, Subnet mask, Primary DNS server, and Secondary DNS server settings that will be sent to a client at its request. Additionally, you can specify the first IP address that will be assigned to the clients and the number of allocateable IP addresses.

In most cases, Default gateway and Primary DNS server should be set to the IP address of the WIASA’s LAN interfaces (e.g., the default LAN IP address is 192.168.0.1), and Subnet mask is set to

255.255.255.0.

NOTE: There should be only one DHCP server on the LAN; otherwise, DHCP would not work prop-

erly. If there is already a DHCP server on the LAN, disable the DHCP server functionality of the WIASA.

3.4.4.2. Static DHCP Mappings

Fig. 38. Static DHCP mappings.

IP addresses of servers are often static so that clients could always locate the servers by the static IP addresses. By Static DHCP Mappings, you can ensure that a host will get the same IP address when

it requests one from the DHCP server. Therefore, instead of configuring the IP address of an intranet server manually, you can configure the server to obtain an IP address by DHCP and it is always assigned the same IP address.

To always assign a static IP address to a specific DHCP client:

1. Specify the MAC address of the DHCP client and the IP address to be assigned to it. Then, give

a description for this mapping.

2. Select the corresponding Enabled check box.

3.5. Configuring IEEE 802.11b-Related Settings

3.5.1. Communication

3.5.1.1. Basic

IEEE 802.11b-related communication settings include AP functionality, Regulatory domain, Channel number, and Network name (SSID), and Transmit power.

Fig. 39. IEEE 802.11b communication settings.

For specific needs such as configuring the WIASA as a wireless LAN-to-LAN bridge, the AP functionality can be disabled, so that no wireless client can associate with the WIASA.

The transmit power of the RF module of the WIASA can be adjusted so that the RF coverage of the WIASA can be changed.

3.5.1.2. AP Load Balancing

Fig. 40. AP load balancing settings.

Several WIASAs and APs can form a load-balancing group if they are set the same Group ID. The load-balancing policy can be by Number of Users or by Traffic Load.

If the by-number-of-users policy is selected, a new wireless user can only associate with an AP that has the smallest number of associated wireless users in the group. On the other hand, if the by-traffic-load policy is selected, a new wireless user can only associate with an AP that has the less traffic load in the group.

3.5.1.3. Wireless Distribution System

Notebook Computer

WDS

LAN

AP 2

Fig. 41. Wireless Distribution System.

Traditionally, access points are connected by Ethernet. By Wireless Distribution System (WDS), APs can communicate with one another wirelessly. For example, in Fig. 41, AP 2 acts as an access point for the notebook computers and it forwards packets sent from the notebook computers to AP 1 through WDS. Then, AP 1 forwards the packets to the Ethernet LAN. Packets destined for the notebook computers follow a reverse path from the Ethernet LAN through the APs to the notebook computers. In this way, AP 2 plays a role of “AP repeater”.

NOTE: A WIASA can have up to 6 WDS links to other WIASAs, APs, or wireless bridges.

AP 1

Fig. 42. Wireless Distribution System settings.

To enable a WDS link:

1. Specify the MAC address of the AP or wireless bridge at the other end of the WDS link.

2. Select the corresponding Enabled check box.

For example, assume you want a WIASA and an AP with MAC addresses 00-02-65-01-62-C5 and 00-02-65-01-62-C6, respectively, to establish a WDS link between them. On WIASA

00-02-65-01-62-C5, set the peer MAC address of port 1 to 00-02-65-01-62-C6 and on AP 00-02-65-01-62-C6, set the peer MAC address of port 1 to 00-02-65-01-C5.

TIP: Plan your wireless network and draw a diagram, so that you know how a WIASA is connected

to other peer WIASAs, APs, or wireless bridges by WDS.

3.5.2. Security

Fig. 43. IEEE 802.11b basic security settings.

IEEE 802.11b security settings include SSID broadcasts, Wireless client isolation, Security mode, IEEE 802.11 Authentication algorithm, WEP keys, MAC-Address-Based Access Control.

For security reasons, it’s highly recommended that the security mode be set to options other than Open System. When the security mode is set to Open System, no authentication and data encryption will be performed. Additionally, you can disable the SSID broadcasts functionality so that a wireless client computer with an “any” SSID cannot associate with the WIASA.

When the Wireless client isolation setting is set to This AP only, wireless clients of this WIASA as an AP cannot see each other, and wireless-to-wireless traffic is blocked. When the setting is set to All APs in this subnet, traffic among wireless users of different APs in the same IP subnet is blocked. This feature is useful for WLANs deployed in public places. In this way, hackers have no chance to attack other wireless users in a hotspot.

There are up to 9 security modes depending on WIASA model variations:

Open System. No authentication, no data encryption. 



64-bit WEP. Authentication and data encryption based on 64-bit WEP (Wired Equivalent Privacy).



128-bit WEP. Authentication and data encryption based on 128-bit WEP (Wired Equivalent Privacy), and 128-bit keys are used.



802.1x EAP-MD5. The IEEE 802.1x functionality is enabled and the username/password-based EAP-MD5 authentication is used. No data encryption.



802.1x EAP-MD5 + 64-bit WEP. The IEEE 802.1x functionality is enabled and the username/password-based EAP-MD5 authentication is used. Data encryption is achieved by 64-bit WEP.

802.1x EAP-MD5 + 128-bit WEP. The IEEE 802.1x functionality is enabled and the user-



name/password-based EAP-MD5 authentication is used. Data encryption is achieved by 128-bit WEP.



802.1x EAP-TLS; no encryption. The IEEE 802.1x functionality is enabled and the digital certificate-based EAP-TLS user authentication. No data encryption is used.



802.1x EAP-TLS 64-bit key. The IEEE 802.1x functionality is enabled and the digital certificate-based EAP-TLS (Transport Layer Security) user authentication and data encryption is used. Session keys are 64-bit.



802.1x EAP-TLS 128-bit key. The IEEE 802.1x functionality is enabled and the digital certificate-based EAP-TLS user authentication and data encryption is used. Session keys are 128-bit.

According to the IEEE 802.11 standard, WEP can be used for authentication and data encryption. Normally, Shared Key authentication is used if WEP data encryption is enabled. In rare cases, Open System authentication may be used when WEP data encryption is enabled. The Authentication algo- rithm setting is provided for better compatibility with wireless clients with various WLAN network adapters. There are three options available, including Open System, Shared Key, and Auto.

See Section 3.5.3 for more information about IEEE 802.1x.

NOTE: Each field of a WEP key setting is a hex-decimal number from 00 to FF. For example, when

the security mode is set to 64-bit WEP, you could set Key 1 to “00 01 2E 3A DF”.

Fig. 44. MAC-address-based access control settings.

With MAC-Address-Based Access Control, you can specify the wireless client computers that are permitted or not permitted to associate with the WIASA. When the table type is set to inclusive, entries in the table are permitted to associate with the WIASA. When the table type is set to exclusive, entries in the table are not permitted to associate with the WIASA.

To deny wireless clients’ access to the wireless network:

1. Select Enabled from the Functionality drop-down list.

2. Set the Access control type to exclusive.

3. Specify the MAC address of a wireless client to be denied access, and then click Add.

4. Repeat Steps 3 for other wireless clients.

To grant wireless clients’ access to the wireless network:

1. Select Enabled from the Functionality drop-down list.

2. Set the Access control type to exclusive.

3. Specify the MAC address of a wireless client to be denied access, and then click Add.

4. Repeat Steps 3 for other wireless clients.

To delete an entry in the access control table:

Click Delete next to the entry. 

3.5.3. IEEE 802.1x/RADIUS

IEEE 802.1x Port-Based Network Access Control is a new standard for solving some security issues associated with IEEE 802.11, such as lack of user-based authentication and dynamic encryption key distribution. With IEEE 802.1x and the help of a RADIUS (Remote Authentication Dial-In User Service) server and a user account database, an enterprise or ISP (Internet Service Provider) can manage its mobile users’ access to its wireless LANs. Before granted access to a wireless LAN supporting IEEE 802.1x, a user has to issue his or her user name and password or digital certificate to the backend RADIUS server by EAPOL (Extensible Authentication Protocol Over LAN). The RADIUS server can record accounting information such as when a user logs on to the wireless LAN and logs off from the wireless LAN for monitoring or billing purposes.

The IEEE 802.1x functionality of the WIASA is controlled by the security mode (see Section 3.5.1.1). So far, the WIASA supports two authentication mechanisms—EAP-MD5 (Message Digest version 5) and EAP-TLS (Transport Layer Security). If EAP-MD5 is used, the user has to give his or her user name and password for authentication. If EAP-TLS is used, the wireless client computer automatically gives the user’s digital certificate that is stored in the computer hard disk or a smart card for authentication. And after a successful EAP-TLS authentication, a session key is automatically generated for wireless packets encryption between the wireless client computer and its associated WIASA. To sum up, EAP-MD5 supports only user authentication, while EAP-TLS supports user authentication as well as dynamic encryption key distribution.

Fig. 45. IEEE 802.1x and RADIUS.

A WIASA supporting IEEE 802.1x can be configured to communicate with two RADIUS servers. When the primary RADIUS server fails to respond, the WIASA will try to communicate with the secondary RADIUS server. You can specify the length of timeout and the number of retries before communicating with the secondary RADIUS server after failing to communicate with the primary RADIUS server.

An IEEE 802.1x-capable WIASA and its RADIUS server(s) share a secret key so that they can authenticate each other. In addition to its IP address, a WIASA can identify itself by an NAS (Network Access Server) identifier. Each IEEE 802.1x-capable WIASA must have a unique NAS identifier.

Fig. 46. IEEE 802.1x/RADIUS settings.

TIP: Refer to the IEEE 802.1x-related white papers on the accompanying CD-ROM for more infor-

mation about deploying secure WLANs with IEEE 802.1x support.

3.6. Configuring Advanced Settings

3.6.1. Filters and Firewall

3.6.1.1. Packet Filters

Fig. 47. Packet filters settings.

You can specify rules for the firewall component of WIASA to check incoming and outgoing packets. Packets that meet the rules can be permitted or denied. The protocol field, source IP address field, destination IP address field, and destination port field of a packet’s IP header are inspected to see if it meets a rule. A packet that meets a rule can be dropped (Block) or accepted (Accept) as specified in the Action setting of the rule. Packets that do not meet any rules can be dropped (Discard) or accepted (Pass) as specified in the Policy setting.

A rule is composed of 5 parts:

What to do if a packet meets this rule (Action) 



Protocol type

All 



ICMP



TCP



UDP



Source IP address range (Source IP Address AND Source Subnet Mask)



Destination IP address range (Destination IP Address AND Destination Subnet Mask)



Port ranges

A source (destination) IP address range is determined by performing an AND operation on the source (destination) IP address field and the source (destination) subnet mask field. For example, if the source IP address field is 192.168.0.1 and the source subnet mask field is 255.255.255.0, the resultant source IP address range is 192.168.0.0 to 192.168.0.255.

Up to 5 port ranges can be specified in a rule, and these ranges must be separated by commas. For example, “21,80,85-89,140,200-230” in the destination port field signifies 5 port ranges.

To set a rule for packet filtering:

1. Specify the protocol type, source IP address, source IP mask, destination IP address, desti-

nation IP mask, and destination port for the rule. Then specify in the Action setting how to

deal with a packet that meets the rule.

2. Select the corresponding Enabled check box.

NOTE: Set the rules with great care since incorrect rules would make the WIASA inaccessible. The

last resort to restore the WIASA to service may be resetting its configuration to factory-set values by pressing the Default (or SF-Reset) switch on the housing of the WIASA. However, Wireless Network Manager can always be used to configure the WIASA even if the filtering rules are incorrect.

3.6.1.2. Firewall

Fig. 48. Packet filters and firewall settings.

SPI analyzes incoming and outgoing packets based on a set of criteria for abnormal content. Therefore, SPI can detect hacker attacks, and can summarily reject an attack if the packet fits a suspicious profile. To enable SPI, select the Enable SPI (Stateful Packet Inspection) check box.

Some DoS (Denial of Service) attacks are based on sending invalid ICMP request packets to hosts. The WIASA can be set to not accept any ICMP requests on the Ethernet WAN interface to defense against attacks of this kind. Enable this capability by selecting the Block ICMP PING from Internet check box.

NOTE: Because some of the WIASA’s CPU resources are spent in checking packets for these secu-

rity features, you may feel networking performance degradation if the security functions are enabled.

3.6.1.3. URL Filters

Fig. 49. URL filters settings.

The WIASA is capable of blocking HTTP traffic from the intranet to specified unwelcome Web sites.

To block HTTP traffic to an unwelcome Web site:

1. Specify the URL (ex. www.xxx.com) of the unwelcome Web site.

2. Select the corresponding Enabled check box.

NOTE: Do not type “http://” when specifying a URL. Just type the domain name.

3.6.2. Management

3.6.2.1. Remote Web-Based Management

Fig. 50. Remote Web-based management setting.

The WIASA can also be managed from the Internet using a Web browser. To enable this capability, select the Enable remote Web-based management check box. To manage the WIASA from the Internet, connect to the WIASA within a Web browser, but be sure to specify the port 8080. For example, if the WAN interface of a WIASA is configured to be 61.16.33.113, the URL for managing this WIASA is “http://61.16.33.113:8080”.

3.6.2.2. UPnP

Fig. 51. UPnP settings.

UPnP (Universal Plug and Play) enables a Windows XP user to automatically discover peripheral devices by HTTP. When the UPnP functionality is enabled, you can see the WIASA in My Network Places of Windows XP. The WIASA can be given a friend name that will be shown in My Network Places. Double-clicking the icon in Network Neighborhood that stands for the WIASA will launch the default Web browser for you to configure the WIASA.

3.6.2.3. SNMP

Fig. 52. SNMP settings.

The WIASA can be managed by SNMP (Simple Network Management Protocol), and the SNMP

management functionality can be disabled. You can specify the name (used as a password) of the read-only and read-write community. In addition, up to 5 SNMP trap targets can be set in the SNMP

Trap Table. So far, the WIASA issues the following types of traps—Cold Start, Warm Start, Link Up, Link Down and SNMP Authentication Failure.

NOTE: SNMP Authentication Failure is issued when using an incorrect community string to manage

the WIASA via SNMP and the SNMP MIB II OID, snmpEnableAuthenTraps, is enabled (disabled by default).

To specify a trap target:

1. Type the IP address of the target host.

2. Type the Community for the host.

3. Select the corresponding check box next to the IP address text box.

Appendix A

A-1: Default Settings

TIP: Press the Default (or SF-Reset) switch on the housing of a powered-on WIASA to reset the

configuration settings to factory-set values.

Setting Name Default Value

Global

User Name root Password root Operational Mode Router with a Static-IP DSL/Cable Con-

IEEE 802.11b

Regulatory Domain FCC (U.S.) Channel Number 11 SSID wireless SSID Broadcasts Enabled Transmission Rate 11Mbps Transmit Power High MAC Address See the label on the accompanying

Security Mode Open System Selected WEP Key Key #1 WEP Key #1 00-00-00-00-00 WEP Key #2 00-00-00-00-00 WEP Key #3 00-00-00-00-00 WEP Key #4 00-00-00-00-00 MAC-Address-Based Access

Control Access Control Table Type Inclusive Wireless Client Isolation Disabled AP Load balancing Disabled

WAN Interface

Type Static-IP DSL/Cable Changeable MAC Address IEEE 802.11b MAC address IP Address 192.168.100.1 Subnet Mask 255.255.255.0 Default Gateway 0.0.0.0 Primary DNS Server 0.0.0.0 Secondary DNS Server 0.0.0.0 Host Name router Domain (DNS suffix) Not set PPP User Name username Password Not set Telephone Number Not set PPPoE User Name username Password Not set

nection

PCMCIA card or the label on the housing of the WIASA.

Disabled

Service Name servicename

LAN Interface

Method of obtaining an IP Address Set manually

IP Address 192.168.0.1 Subnet Mask 255.255.255.0 Default Gateway 0.0.0.0

DHCP Server

Functionality Enabled Default Gateway 192.168.0.1 Subnet Mask 255.255.255.0 Primary DNS Server 192.168.0.1 Secondary DNS Server 0.0.0.0 First Allocateable IP Address 192.168.0.2

Allocateable IP Address Count 20

NAT Server

Functionality Enabled Virtual Server Mappings Disabled DMZ Host Not set Static NAT Mappings Not set

DNS Proxy

Static DNS Mappings Not set

Filters/Firewall

Packet Filters Not set URL Filters Not set WAN ICMP Request Blocking Disabled State Packet Inspection (SPI) Disabled

Management

Remote Web-Based Management Disabled UPnP Enabled SNMP Enabled SNMP read community public SNMP write community private Telnet Enabled

A-2: LED Definitions

There are several LED indicators on the housing of a WIASA. They are defined as follows:

Wireless Broadband Router



PPP: PPP/PPPoE. Lights up when a PPP or PPPoE link has been established.



ALV: Alive. Blinks when the WIASA is working normally.



RF: IEEE 802.11b interface



LAN: Ethernet LAN interface



WAN: Ethernet WAN interface



PWR: Power

Wireless Broadband Switch Router



PWR: Power



RF: IEEE 802.11b interface



LNK: Link. Lights up when the IEEE 802.11b interface is initialized successfully.



ACT: Active. Lights up when the IEEE 802.11b interface is transmitting or receiving data.



PPP: PPP/PPPoE. Lights up when a PPP or PPPoE link has been established.



ALV: Alive. Blinks when the WIASA is working normally.



ST1-ST2: Status 1 to 2 for status indication



WAN: Ethernet WAN interface



LNK: Link. Lights up when the Ethernet WAN interface is initialized successfully.



ACT: Active. Lights up when the Ethernet WAN interface is transmitting or receiving data.



100/10 1-4: 10/100 Ethernet LAN switch ports



LNK: Link. Lights up when an Ethernet cable is connected firmly to this Ethernet port.



ACT: Active. Lights up when this Ethernet port is transmitting or receiving data.

Appendix B: Troubleshooting

Check the following first:



Make sure that the power of the WIASA is on and the Ethernet cables are connected firmly to the RJ-45 jacks of the WIASA.



Make sure that the LED ALV of the WIASA is blinking to indicate the WIASA is working.



Make sure the types of the Ethernet cables are correct. Recall that there are two types—normal and crossover.



Make sure that the DSL, cable, V.90, or ISDN modem connected with the WIASA is powered on.

B-1: Wireless Settings Problems



The wireless client computer cannot associate with an access point.



Is the wireless client set in infrastructure mode?

Check the operating mode of the WLAN NIC. 



Is the SSID of the WLAN NIC identical to that of the prospective access point or WIASA?



Check the SSID setting of the WLAN NIC and of the WIASA.



Is the WEP functionality of the prospective access point or WIASA enabled?



Make appropriate WEP settings of the client computer to match those of the access point or WIASA.



Is the prospective access point or WIASA within range of wireless communication?



Check the signal strength and link quality sensed by the WLAN NIC.

B-2: TCP/IP Settings Problems

Client

Computer

IEEE 802.11b

Ethernet/

RS232

Ethernet LAN

Stage A State B Stage C

WIASA

ADSL/Cable/

V.90/ISDN

Modem

Phone/

CATV

Network

Stage D

Default Gateway

of WIASA

Correspondent

Host

Internet

DNS Server

of WIASA

Fig. 53. Communication stages for a client to reach its correspondent host.

For a client computer to communicate with a correspondent host on the Internet by the host’s domain name (e.g. http://www.wi-fi.com

), it first sends a DNS request to a DNS server on the Internet. The DNS request travels first to the WIASA, then the WIASA relays this request to the default gateway of the WIASA through a modem. Finally, this request is forwarded by the gateway to the DNS server on the Internet. The DNS reply issued by the DNS server is transmitted back to the client computer following a reverse path. When the client computer receives the DNS reply, it knows the IP address of the correspondent host and sends further packets to this IP address.

As illustrated in Fig. 53, the communication path could be broken at some of the stages. The OS-provided network diagnostic tool, ping.exe, can be employed to find out TCP/IP-related communication problems.

NOTE: If two or more NICs are installed and operating on a client computer, TCP/IP may not work

properly due to incorrect entries in the routing table. Use the OS-provided command-line network tool, route.exe, to add or delete entries from the routing table. Or, use Windows-provided Device Manager to disable unnecessary NICs.

Solve the following problems in order:



The WIASA does not respond to ping from the client computer.



Are two or more NICs installed on the client computer?

Use the OS-provided command-line network tool, route.exe, to modify the contents



of the routing table.

 Use Windows-provided Device Manager to disable unnecessary NICs.



Is the underlying link (Ethernet or IEEE 802.11b) established?

Make sure the Ethernet link is OK. 



Make sure the wireless settings of the wireless client computer and of the WIASA match.

Are the IP address of the client computer and the IP address of the WIASA 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 WIASA are in the same IP subnet.



TIP: If you forget the current IP address of the WIASA, use Wireless Router/AP

Browser to get the information (see Appendix B-3).



The default gateway of the WIASA does not respond to ping from the client computer.



Solve the preceding problem first.



Is the modem working?



You may find out the answer by directly connecting the modem to a computer. Refer to the manual of the modem if necessary.



Are the IP address of the WIASA and the IP address of the gateway in the same IP subnet?



Find out the answer on the start page of the Web-Based Network Manager.



Is the NAT server functionality of the WIASA enabled?



Find out the answer on the start page of the Web-Based Network Manager.



If you cannot find any incorrect settings of the WIASA, the default gateway of the WIASA may be really down or there are other communication problems on the network backbone.



The DNS server(s) of the WIASA do not respond to ping from the client computer.



Solve the preceding problems first.



If you cannot find any incorrect settings of the WIASA, the default gateway of the WIASA may be really down or there are other communication problems on the network backbone.



Cannot access the Internet.



Solve the preceding problems first.



Make sure there are no incorrect packet filter settings that would block the traffic from the local computer to the Internet. In case you are not sure, the last resort may be resetting the configuration settings of the WIASA to default values by press the Default or SF-Reset switch.

B-3: Unknown Problems



The router has been set to be in Simple Access Point mode and to obtain an IP address automatically by DHCP. How can I know its acquired IP address so that I can manage it using a Web browser?



Use the utility, Wireless Router/AP Browser (WLBrwsr.exe), in the “Utilities” folder on the companion CD-ROM disc. This utility can discover nearby WIASAs and show their MAC addresses and IP addresses. In addition, it can launch the default Web browser on your computer.

Fig. 54. Wireless Router/AP Browser.



The WIASA stops working and does not respond to Web management requests.



The firmware of the WIASA may be stuck in an incorrect state.

Press the Reset button on the housing of the WIASA or unplug the power connector



from the power jack, and then re-plug the connector to restart the WIASA.



Contact our technical support representatives to report this problem, so that the bugs can be static in future firmware versions.



If the WIASA still does not work after restarting, there may be hardware component failures in the WIASA.



Contact our technical support representatives for repair.

Intellinet 520638 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Fig. 7. TCP/IP settings for Simple Access Point mode.

Fig. 8. TCP/IP settings for Router with a PPPoE-Based DSL/Cable Connection mode.

Fig. 9. TCP/IP settings for Router with a DHCP-Based DSL/Cable Connection mode.

If the WIASA was set to be in Router with a Dial-up Connection mode, two IP addresses are needed—one for the Ethernet/wireless LAN interfaces and the other for the WAN interface. The IEEE

Fig. 27. TCP/IP settings for Simple Access Point mode.

Fig. 28. TCP/IP settings for Router with a PPPoE-Based DSL/Cable Connection mode.

Fig. 29. TCP/IP settings for Router with a DHCP-Based DSL/Cable Connection mode.

Fig. 31. TCP/IP settings for Router with a Dial-up Connection mode.