1.2 Features and Compatibility
The SAR series Router provides the following features: Multi-mode ADSL technology supports ITU-T G.hs, G.dmt, G.lite and ANSI T1.413 issue 2 to provide interoperability with most DSLAM equipment. ATM (Asynchronous Transfer Mode) protocol allows the QoS(Quality of Service) transmission over a network Support for text-based and Windows-GUI based console management over Telnet and serial connection Support for remote configuration by your network administrator via IP network. Support IEEE 802.1d transparent bridging with spanning tree algorithm. Bridge filtering allows a network administrator to control the flow of packets across the router NAT : let multiple users on the LAN share one Internet connection simultaneously SNMP agent: allows monitoring and configuration by a standard SNMP manager. BOOTP/TFTP enable the remote configuration Point-to-Point Protocol (PPP) RFC 1483 Link Protocol Password Authentication Protocol (PAP) and Challenge Handshake Authentication Protocol (CHAP) security under PPP protocol IP routing support includes the RIP(Routing Information Protocol) which allows the exchange of routing information on a TCP/IP network Flash memory for Software upgrade Status LEDs for easy monitoring and troubleshooting DNS relay: allows for automatic name resolution when no DNS information is configured by the user.
1.3 Whats in the package?
One ADSL Router One 12VDC Adapter One RJ-11 Telephone Cable One 10Base-T Ethernet straight-through Cable One 9-pin to 9-pin RS-232 Cable One Software CD containing the Users Guide and configuration software All packages have been checked carefully for their completeness and functionality before shipped. Please contact the place of purchase if any of the above listed items are missing or damaged.

1.4 Front Panel

The ADSL Router has five status LEDs for diagnostics. You can monitor the LEDs during operation. Following table shows the ADSL Router status LEDs and identifies what each LED light means. -7-

6. Port Forwading

The normal way of using your SAR router is in NAT mode (see setup above). Most users will use their router with NAT enabled because this allows them to share their internet connectivity across their whole network without needing a block of static IP addresses from the ISP i.e. the ISP sees the whole of your LAN as a single IP address and the router automatically sorts out traffic to the correct local clients:
However using NAT has its advantages and disadvantages. The advantages are it allows you to easily run multiple PCs through a single user ISP account and it acts as a natural firewall stopping unsolicited incoming traffic. However the disadvantage of NAT is - 15 -
that some software needs the IP address of the PC to be exposed to the outside world this is just what NAT stops! The normal way around this problem whilst still retaining the NAT mode is to use port forwarding. Port forwarding (also sometimes called pinholeing) tells the router to direct certain incoming traffic to specified local addresses. e.g. if you are wanting to run a local web server on address 192.168.0.10 and you want external internet users to be able to see your server then you need to instruct the router to forward all port 80 TCP requests (the port used by http) to your local server. To setup port forwarding connect your router to the com port of your PC start the ADSL Configuration programme and click on Properties:
Now click on the Setting Port Forwarding Rules link:
Enter the port rule and then click on Add A Rule: The Rule will show in the list (see opposite). When youve added all the rules you need click on Confirm. Then OK on the Properties screen and then Apply to send the new configuration across to the router. Now, whenever anyone tries to access your IP address (Thats the external IP address as allocated to you by your ISP) using port 80 the router will automatically forward the request to your local client at address 192.168.0.10.

7. Advanced PPP Settings

13.5.4. disable

disable [<i/f>]
Description: Disables all interfaces, or just a specified interface. Example:
DSL> ip disable vlane DSL> ip device # type dev file IP address device ether ether //nice mtu 1500 192.168.2.1 device vlane ether //lane mtu 1500 192.168.55.1 # DISABLED

13.5.5. enable

enable [<i/f> [mtu <size>] [<IP address>]]
Description: Enables all interfaces, or just a specified interface. Can also be used to set the MTU and IP address on an interface when enabling it (or change them on an interface that is already enabled); see the device command for details on these. Configuration saving saves the MTU and IP addresses, but not the disabled/enabled state. Example:
DSL> ip enable vlane 192.168.56.3 ip/vlane: IP address 192.168.56.3 DSL> ip device # type dev file IP address device ether ether //nice mtu 1500 192.168.2.1 device vlane ether //lane mtu 1500 192.168.56.3

- 39 -

13.5.6. get

get <file>

Description: Reads and executes commands from a file. The commands in the file are in the same format as those documented in this chapter, with no ip prefix. They can contain comments, introduced by the # character. The get command is hidden, not shown by ip help. Example:
DSL> ip get //isfs/cmdfile

13.5.7. ipatm abort

ipatm abort <n>
Description: Closes an IP-over-ATM SVC; the number <n> is as displayed by ipatm files. If there is still traffic being sent to the destination concerned, IP will soon open a new SVC to the destination. Example:
DSL> ip ipatm abort 14

13.5.8. ipatm arp

ipatm arp [list]
Description: Lists the cached mappings from IP addresses to ATM addresses; only relevant when using IP-over-ATM with SVCs. (The list parameter is optional and makes no difference to the behaviour.) Example:

DSL> ip ipatm arp

192.168.5.72 47.00.83.10.a2.b1.00.00.00.00.00.00.00.00.20.2b.01.00.07.00 192.168.5.33 47.00.83.10.a4.00.00.00.00.00.00.00.00.00.20.2b.01.00.19.00 192.168.5.111 47.00.83.10.e2.00.00.00.20.2b.01.01.a8.00.20.2b.01.01.a8.00

DSL> ip relay relay ether ether relay ether vlane relay vlane vlane DSL> ip norelay ether vlane forward relay ether ether relay vlane ether forward relay vlane vlane

13.5.15.ping

ping <IP address> [<ttl> [<size>]]
Description: Sends an ICMP Echo message to the specified IP address. <ttl> (default 30) is the TTL (time-to-live) to use. A crude traceroute functionality can be obtained by repeating the ping command with increasing TTL values, starting with 1. <size> (default 56) is the data size of the Echo message. This does not include the IP header (20 bytes) and the ICMP header (8 bytes). TCP/IP waits 10 seconds for a reply to the message; if none arrives, it reports the lack of a reply. A reply is an ICMP Echo Reply message, or an ICMP error message reporting destination unreachable, time exceeded, or (as should never happen) a parameter problem. ICMP redirect and source quench messages are reported, but TCP/IP continues to wait for a final reply or time-out. Example:
DSL> ip ping 192.168.4.ip: ping - 192.168.1.9 reports pkt #5834 to 192.168.4.13: time-to-live exceeded DSL> ip ping 192.168.4.ip: ping - reply received from 192.168.4.13 DSL> ip ping 192.168.77.77 ip: ping - no reply received

13.5.16.portname

portname add <name> <number>[/<protocol>] portname flush portname list portname read <file> portname help [all|<cmd>]
Description: Sets up a mapping between a UDP or TCP port and a symbolic name; deletes all such mappings; lists the mappings; reads the mappings from a file; or displays help on the portname command. The symbolic names can be used as - 43 -
values of the attributes LPORT and RPORT provided the protocol type (UDP or TCP) is appropriate. They are also displayed in place of port numbers, when a suitable mapping exists. <protocol> should be either UDP or TCP; it can be omitted, but that is not very useful. For portname read, the file is in the same format as //isfs/services, which is the same as the output from portname list. The portname command is hidden, not shown by ip help. Configuration saving saves this information. Example:
DSL> ip portname flush DSL> ip portname add someport 105/tcp DSL> ip portname list someport 105/TCP DSL> ip portname read //isfs/services DSL> ip portname list router 520/UDP snmp 161/UDP tftp 69/UDP telnet 23/TCP someport 105/TCP

13.5.17.relay

relay relay all | <i/f> [<i/f>] [forward]

Description: Displays or sets what forwarding TCP/IP will do between interfaces. The combinations of setting forwarding can be a bit confusing; they behave as follows: Command:
relay all relay if1 relay if1 forward
Enables forwarding: from every interface to every non-loopback interface from if1 to every non-loopback interface, and from every interface to if1 from if1 to every non-loopback interface

relay if1 if2

from if1 to if2 and from if2 to if1 from if1 to if2

relay if1 if2 forward

(Dont confuse the forward keyword, which indicates one-way relaying, with the term forwarding!) To disable forwarding, use the norelay command. Configuration saving saves this information. By default all forwarding is disabled. Example:
DSL> ip relay No relaying is being performed DSL> ip relay ether vlane forward relay ether vlane forward DSL> ip relay ether forward

- 44 -

relay ether ether relay ether vlane forward DSL> ip relay ether vlane relay ether ether relay ether vlane DSL> ip relay all relay ether ether relay ether vlane relay vlane vlane

13.5.18.rip accept

rip accept [all|<i/f>] [none|<version>*]
Description: Controls for which version or versions of RIP (RIP version 1, RFC 1058, or RIP version 2, RFC 1723) TCP/IP will accept incoming information on each interface. Configuration saving saves this information. By default both RIP versions are accepted on all interfaces ( rip accept all ). Example:
DSL> ip rip accept all DSL> ip rip accept ether 2 DSL> ip rip allowed rip send ether none rip send vlane none rip accept ether 2 rip accept vlane 1 2

13.5.19.rip allowed

rip allowed
Description: Displays the RIP versions that will be accepted and sent on each interface. Example:
DSL> ip rip allowed rip send ether 2 rip send vlane 2 rip accept ether rip accept vlane 1 2

13.5.20.rip boot

rip boot

Description: - 45 -

Broadcasts a request for RIP information from other machines. TCP/IP does this automatically when it first starts up, and the routing information should be kept up to date by regular broadcasts from the other machines, so this command is normally of little use. Example:

DSL> ip rip boot

13.5.21.rip hostroutes

rip hostroutes [off]

Description: Sets or clears the hostroutes flag; TCP/IP will accept RIP routes to individual hosts only if this flag is on. If the flag is off, then RIP version 1 routes that appear to be to individual hosts will be treated as if they were to the network containing the host; RIP version 2 routes to individual hosts will be ignored. (The reason for this difference is that RIP version 1 does not allow specification of subnet masks; a RIP version 1 route that appears to be to an individual host might in fact be to a subnet, and treating it as a route to the whole network may be the best way to make use of the information.) To see the state of the flag without changing it, the config command must be used. Configuration saving saves this information. By default the hostroutes flag is off. Example:

DSL> ip route add default 0.0.0.0 192.168.2.3 0:0:0:0 DSL> ip route add testnet1 192.168.101.0 192.168.2.34 DSL> ip route add testnet2 192.168.102.0 192.168.2.34 ff:ff:ff:60 DSL> ip route
route add testnet2 192.168.102.0 192.168.2.34 ff:ff:ff:# MAN 58s/1m via ether * route add testnet1 192.168.101.0 192.168.2.34 ff:ff:ff:# MAN via ether route add default 0.0.0.0 192.168.2.3 00:00:00:# MAN via ether

13.5.28.routeflush

routeflush [<i/f>] [all]
Description: Removes routes from the route table. If <i/f> is specified, only routes through the named interface are removed. If all is not specified, only host routes (those with a mask of ff:ff:ff:ff) are removed. The routeflush command is hidden, not shown by ip help. Configuration saving saves this information. Example:
DSL> ip routeflush ether all DSL> ip routeflush

- 48 -

13.5.29.routes

routes

Description: Lists routes. (The same as route, with no parameters.)

13.5.30.stats

stats arp|icmp|ip|tcp|udp [reset] stats help [<cmd>|all]
Description: Displays or clears a subset of IP statistics. Example:
DSL> ip stats udp ip: UDP receptions delivered to users: 0 ip: UDP receptions with no users: 170 ip: Otherwise discarded UDP receptions: 0 ip: Transmitted UDP packets: 35 DSL> ip stats udp reset DSL> ip stats udp ip: UDP receptions delivered to users: 0 ip: UDP receptions with no users: 0 ip: Otherwise discarded UDP receptions: 0 ip: Transmitted UDP packets: 0

13.5.31.subnet

subnet subnet add <name> <i/f> <IP address> <mask> subnet delete <name> subnet flush
Description: Lists defined subnets; defines a subnet; deletes a subnet definition; or deletes all subnet definitions. <name> is a label, that can be specified by subnet add and later used by subnet delete to delete the subnet. <i/f> is not used, but is present for historical reasons and must be specified as either. or a valid interface name. <IP address> is the IP address of the subnet being defined (only those bits of <dest> corresponding to bits set in <mask> are relevant). <mask> is the subnet mask of the subnet being defined, specified as four hexadecimal numbers separated by colons. A subnet is defined automatically for each interface, with a name formed by appending.home to the device name. The only significant use for the subnet command is to change the masks for these automatic subnets, if the default masks (see device command) are not correct. (Subnet definitions for other subnets can also be useful in conjunction with RIP version 1, which does not communicate subnet masks, but this is not very common.) Configuration saving saves this information. - 49 -
DSL> ip device # type dev file IP address device ether ether //nice mtu 1500 192.168.2.1 device vlane ether //lane mtu 1500 192.168.55.1 DSL> ip subnet subnet vlane.home. 192.168.55.0 ff:ff:ff:00 vlane subnet ether.home. 192.168.2.0 ff:ff:ff:00 ether DSL> ip subnet add vlane.home. 192.168.55.1 ff:ff:fc:0 DSL> ip subnet subnet vlane.home. 192.168.52.0 ff:ff:fc:00 vlane subnet ether.home. 192.168.2.0 ff:ff:ff:00 ether

> nat inbound add ppp_device 80/TCP 192.168.219.38 > nat inbound list # Interface Port/Proto New IP address 1 ppp_device 80/tcp 192.168.219.r1483 21/tcp 192.168.219.40 > nat inbound delete 2

13.6.4. nat info

nat info
Description: This command displays the values of various parameters, which are defined in the module file, for example the session table size and the session timeouts. NATs current memory usage is also displayed. Example:
> nat info Interface table size 1 (116 bytes) Session table size per interface: 128 (6656 bytes) Total: 6656 bytes Hash table size per interface: 128 (512 bytes) Total: 512 bytes Fragment table size per interface: 32 (640 bytes) Total: 640 bytes Max queued buffers: 16 Fragment timeout: 30 Support for incoming fragments: enabled

- 51 -

Support for outgoing fragments: enabled Session timeouts: ICMP query: 10 UDP: 30 TCP (established): 300 TCP (other): 15 Initial port number: 10000

13.6.5. nat protocol

nat protocols
Description: The nat protocols command lists the application level gateways (ALGs) provided in the current image in order to support particular higher-level protocols, and the port or ports, which each ALG monitors Example
> nat protocols Name Port/IP protocol ftp 21/tcp

13.6.6. nat sessions

nat sessions <i/f> [all | summary]
Description: The nat sessions command displays a list of currently active NAT sessions on the interface <i/f>. In this context, a session is a pair of source IP addresses and port numbers (and corresponding new port number) that NAT regards as one side of an active connection. For each TCP or UDP session active, the source and destination IP address and port number, and the local port number and the age of the session, are printed. The all option causes the sessions command to print out information on every session, including sessions, which have timed out. Normally the sessions command only shows active sessions (those which have not timed out). The summary command does not show detailed information on each session, but only prints out the total number of active, timed out and available sessions. Example:

> nat sessions ppp Proto Age NAT port Private address/port Public address/port TCP 192.168.219.38/3562 194.129.50.6/21 TCP 192.168.219.64/2135 185.45.30.30/80 Total: 2 sessions active 101 sessions timed out 126 sessions available

13.6.7. nat stats

Syntax: - 52 -
nat stats <i/f> [reset]
Description: This command displays various statistics gathered by NAT on the interface <i/f>. These are cumulative totals since power on, or since the reset keyword was given. The nat stats command does not provide the total number of packets or bytes transferred, as this information is normally available from the device driver on the interface which NAT is filtering. Example:
> nat stats ppp_device Outgoing TCP sessions created: 456 Outgoing UDP sessions created: 123 Outgoing ICMP query sessions: 12 Outgoing ICMP errors: 0 Incoming ICMP errors: 6 Incoming connections refused: 2 Sessions deleted early: 0 Fragments currently queued: 0

Commands for PPP process

13.7.1. Console object types
The ppp process presents its setup in terms of a number of distinct object types: The upper limit on the number of each of these objects permitted in a system is configured using the config
resource console command. The current state of each object is saved by config save.

Channels

The ppp process provides a number of PPP connection channels. A channel is a single PPP connection. Channels are numbered from 1. Many ppp console commands affect only a single channel. The command is prefixed with the channel number.
A user is a user name and password. All users must have distinct names. The user console command controls these.

Interfaces

An interface is an internal MAC (Ethernet) device. PPP channels must be associated with an interface to be involved with bridging or routing.
Interface 1 and Channel 1
Interface 1 has some special functions associated with it, allowing dynamic IP address assignment to be performed. Channel 1 is by default associated with Interface 1 These two should be used only for IP dial-out functions, and for this function should be attached to the router interface named ppp_device.
13.7.2. <channel> clear

<channel> clear

Description: Clear all aspects of this channel back to their default settings. If there is an active connection it is torn down.

- 53 -

13.7.3. <channel> disable

<channel> disable

Description: Clear the enable flag for a PPP channel. This is the default setting. Disabling does not remove other configured information about this channel. In the PPP state machine, this sets the PPP link to closed. If it is already closed, there is no effect. Configuration saving saves this information. By default all channels are disabled.

13.7.4. <channel> discard
<channel> discard [<size>]
Description: Discard is a PPP LCP packet type, which is like the Echo packet type but does not generate a return. This can be used for more careful tests of data transfer on the link, for instance at sizes near the negotiated MRU. This command sends an LCP Discard packet, of the specified size. If no size is given, a minimal sized packet is sent. Arrival of a Discard packet is logged locally as a level 2 event. The link must be up and operational in order to do the discard test.
13.7.5. <channel> echo
<channel> echo [<size>]
Description: Echo is an LCP packet, which is used to test an established PPP link. It solicits a ping-like reply from the far end. This command sends an LCP Echo packet, of the specified size. If no size is given, a minimal sized packet is sent. If a size greater than the remote Maximum Receive Unit size is specified, the value is reduced to the remote MRU before sending. The command waits for 1 second for a reply packet to arrive, and prints whether the reply arrived. If a reply arrives subsequent to this, it is logged as a level 2 event. The link must be up and operational in order to do the echo test. See also the discard test.
13.7.6. <channel> echo every
<channel> echo every <seconds>
Description: Echo is an LCP packet, which is used to test an established PPP link. It solicits a ping-like reply from the far end. This command sets a channel to confirm the continued presence of an open PPP connection by sending an LCP echo every few seconds, and requiring an echo reply. The number of seconds between echo requests is specified as a parameter. If 0 is specified, the function is disabled. Use the info all command to read the current state on a channel. Configuration saving saves this information. By default the function is disabled.
13.7.7. <channel> enable

<channel> enable

Description: Set the enable flag for a PPP channel. By default this is disabled. In the PPP state machine, this flag sets the PPP link to open. If it is already open, there is no effect. Configuration saving saves this information. By default all channels are disabled. - 54 -

13.7.8. <channel> hdlc
<channel> hdlc [1|0]
Description: If 1, use an HDLC header on the front of transmitted packets and require one on received ones. This consists of two bytes, FF-03, and assists in interoperability with some other (non-standard) implementations. If 0, disable this. Call with no argument to find the current setting. The default value is 0 (disabled). Configuration saving saves this information. If not set, and a packet is received with an HDLC header, the channel goes into a learned HDLC mode and sends packets with the HDLC header. Thus, interoperation with HDLC-using equipment should not normally require any configuration. Learning occurs in this direction only. Setting hdlc to 0 clears this learned state. Configuration saving does not save the learned state.
13.7.9. <channel> info
<channel> info [all]
Description: Provide information about the current settings of this channel. This includes all configured state, and also current protocol information. Specifying all prints out more information. info and status are synonyms.
13.7.10.<channel> interface
<channel> interface <n>
Description: Logically associate the specified channel with the specified interface. Interface 1 is always the router port. It should be used for any PPP channel over which IPCP communication with the local systems IP router is desired. Other interfaces can be created for bridging. A single PPP channel can only be associated with a single interface, or a single tunnel. Use info to find the current setting. Calling with n=0 removes any association. This is the default state. Configuration saving saves this information.
13.7.11.<channel> lcpmaxconfigure
<channel> lcpmaxconfigure [<n>]
Description: Set the Max-Configure parameter for LCP. This is the maximum number of Configure Requests that will be sent without reply, before assuming that the peer is unable to respond. Call with no argument to find the current setting. The default value is 10. Configuration saving saves this information
13.7.12.<channel> lcpmaxfailure
<channel> lcpmaxfailure [<n>]
Description: Set the Max-Failure parameter for LCP. This is the maximum number of consecutive Configure Naks that will be sent before assuming that parameter negotiation is not converging. Call with no argument to find the current setting. The default value is 5. Configuration saving saves this information.

B.4 Problems when accessing the Internet or remote network
Cants access the Internet or remote network There are four possibilities to causes this problem 1. The connection between the computer and the Modem 2. The connection between the Modem and your NSP 3. The connection between your NSP and your ISP 4. The connection between your ISP and the Internet To isolate the problem, you can verify IP connectivity with following steps by running a ping <IP address> command. For example, ping 192.168.254.254. 1. Ping the IP address of your PC. If you get a response back, proceed to next step directly. If you dont get a response back, check that: - The network adapter card is installed. - The TCP/IP protocol is installed. - 64 -
- The TCP/IP protocol is bound to the network adapter. 2. Ping the IP address of your Modem. If you get a response back, proceed to next step directly. If you dont get a response back, the problem lies between your PC and your Modem: - Check the cables. - Check the hub. - Make sure that your PC and your Modem belong to the same IP sub network. - Observe the TX and RX LEDs to see if data traffic flow appears to be normal 3. Ping the DNS server. If the Modem is configured to bridging mode - Be sure to reboot the Modem if you have made any changes with configuration. - All IP addresses must be in the same IP sub network. If the Modem is configured to routing mode - Check that IP Routing is enabled at the local and the remote end. - Make sure he IP addresses of the local and remote networks belong to different IP sub networks. - Make sure that there is an existing route to the remote network. - Make sure that there is a route back from the remote network. - Be sure to reboot the Modem if you have made any changes with configuration.

17. Appendix C

10Base-T

Glossary

IEEE 802.3 standard for the use of Ethernet LAN technology over unshielded twisted pair wiring, running at 10Mbps. ADSL Asymmetric Digital Subscriber Line - Technology that delivers high-speed data and voice connections over existing phone lines. Up to 8 Mbits/sec can be sent downstream and 640 Kbits/sec upstream. ANSI (American National Standards Institute) Devises and proposes recommendations for international communications standards. ARP Address Resolution Protocol. An Internet protocol used to bind an IP address to Ethernet/802.3 addresses. ASCII American Standard Code for Information Interchange. 8-bit code for character representation. ATM Asynchronous Transfer Mode - Cell-relay broadband technology for high-speed transmission of video, audio, data over LAN/WAN, making use of fixed-size cells (53-byte cells). Bridge A device that segments network traffic. A bridge maintains a list of each segments nodes and only traffic destined for a node on the adjacent segment is passed across the bridge. A bridge operates at Layer 2 of the OSI reference model. CHAP Challenge Handshake Authentication Protocol. A security protocol supported under Point-to-Point Protocol (PPP) used to prevent unauthorised access to devices and remote networks. Uses encryption of password, device names, and random number generation. Class A, B, and C networks:

Refers to a logical connection between end stations in an ADSL/ATM environment Virtual Path Refers to a bundle of virtual channels in a ADSL/ATM environment. VPI Virtual Path Identifier - Number that identifies the link formed by the virtual path in a ADSL/ATM environment. UDP User Datagram Protocol - A TCP/IP protocol describing how packets reach applications in destination nodes. Wall jack A small hardware component used to tap into telephone wall cable. An RJ-11 wall jack usually has four pins; an RJ-45 wall jack usually has eight pins. WAN Wide Area Network - A network that consists of nodes connected by long-distance transmission media, such as telephone lines. WANs can span a state, a country, or even the world.

18. Appendix D

Government compliance notices
European CTR 21 compliance
The equipment has been approved in accordance with Council Decision 98/482/EC for pan-European single terminal connection to the public switched telephone network (PSTN). However, due to differences between the individual PSTNs provided in different countries, the approval does not, of itself, give an unconditional assurance of successful operation on every PSTN network termination point. In the event of problem, you should contact your equipment supplier in the first instance. Note: The manufacturer should ensure that the vendor and user of the equipment is clearly informed of the above information by means of package and/or user manuals of the forms of user instructions.

- 69 -

Supplemental setup instructions for
Asus AAM6030VI Wireless ADSL Router
(read these notes whilst also referring to the manual supplied with the product)
Quick setup instructions for Asus AAM6030EV ADSL Router
(read these notes whilst also referring to the manual supplied with the product) 3 Supplemental.....4 Connecting to your network.....4 Configuration......4 3.1 Configuration with no WEP security....5 3.2 With WEP security.....7 3.2.1 Setup the Router......7 3.2.2 Client Setup for PCI.....8 3.2.3 Using a PCMCIA Wireless card.....10 3.3 WLAN Bridging Mode.....13

1 Supplemental

These setup notes cover the wireless setup for the Asus AAM6030VI Wireless ADSL router. They cover the additional wireless aspects of this product. For basic ethernet and ADSL setup please refer to the standard manual or additional Quick Setup guide.
2 Connecting to your network
Setup of the wireless features of this router can only be done using a web browser via the LAN. As such initial setup should be done via a standard wire type LAN connection. Connect your PC (or other computer) to one of the LAN ports on the VI router. After you have gone through wireless setup of the router (see below) and your computers wireless adapter you can then wirelessly connect to the router.

3 Configuration

It is assumed that you have correctly setup the TCP/IP settings of the router and your computers LAN card (see other notes). After checking your connections and TCP settings (see above) you are ready to run your browser in order to configure the router. Any browser can be used on any operating system: The configuration screens are the same. If you are using Explorer then click on your Explorer icon to start your browser. When your browser starts up enter the IP address of the router as the URL. The browser should then load the startup page from the router: Click in Enter to goto the configuration logon (or if you wait a few seconds this should happen automatically anyway).
(Dont worry that the example above shows the router address as 192.168.0.3 this is the address weve used on our network. If you left the addresses as default in the router then yours will show as 192.168.1.1). Now enter the default user name and password. Click OK and you should then goto the main configuration menu.
Now, to configure the 802.11b wireless setup click on the menu item labelled IEEE 802.11B:
There are two basic ways of running your wireless network: With WEP security and without WEP security. Its easiest to start without security.
Configuration with no WEP security

Click on IEEE/Basic:

Ensure that the Channel and ESSID (if used by your computers wireless adapter) match those used by your wireless clients. If you have to change any settings then click on submit and then on save to store the changes. Next click on Advanced:
Things to check on this screen are that the Fragmentation Threshold and RTS Threshold match those used on you wireless clients adapters. Check that the Authentication type is set to Open System; this means NO security. Check that Basic and Transfer Rates are both set to 1,2,5.5,11 (so that the router will accept connection from wireless clients at any standard 802.11b speed). As before, if you have to change any settings then click on submit and then on save to store the changes. Now click on WEP:
Since we are using NO security you must ensure that the WEP setting shows disabled. Remember to click on submit and then save if you change any setting. Finally click on Reset Modem to reboot the router. Then, after the router has restarted goto the IEEE/Status page:
Now you must check the settings of your wireless clients to ensure their setup exactly matches the router setup as youve just done above. One thing you must check is that your clients are set in Infrastructure mode. This means that the clients expect to communicate via the access point built into the router. The alternative setup is called Ad-hoc or sometimes peer-to-peer. With Peer-to-peer client setup each clients expects to talk to another client. If the clients are set this way they wont be able to communicate with the VI router (A good analogy to use for the different between Infrastructure and Peer-to-peer is to compare with using normal copper network cables to connect clients together. If the clients are connected via a network hub then a standard CAT5 LAN cable is required. But, if the connect direct i.e. a cable connected directly from the back of one PC to the other PC, then they need to use a crossover LAN cable; the normal LAN cable wont work).
Also check that the Preamble mode for your clients match the router. The default for the router is Long so your clients must also be set to Long -6-
If youve done this correctly then your wireless clients should now be able to see the router. You can test this by running a browser on your client and entering the IP address of the router: The router sign on screen should display. You should also be able to see your wireless clients from any LAN based clients connected via the LAN ports on the VI router (and vice-a-versa).

With WEP security

If you are really worried about network security (I cant imagine the average home user being all that bothered) you can configure the VI router to use 64 or 128 bit WEP security. This security relies upon both the router and your clients using an encryption key word on all transmitted and received data.

3.2.1 Setup the Router

To configure WEP security on the router first of all go to the IEEE/Advanced page:
Now select Shared Key as the Authentication Type. Remember submit and then save to store the changes. Now you need to setup a WEP encryption key. Click on WEP:
Now select 128 Bit for WEP (for this example well use 128 encryption). Now you need to enter an encryption key. The easiest way to make a key is enter a word in the Passphrase box and then click on Submit. TAKE CARE: the Create with Passphrase feature is case sensitive. So, in the example above WIRELESS (all caps.) gives a different key than wireless (lower case). Now click on Save to store the settings. After doing these changes the IEEE/Status page should look like this:
3.2.2 Client Setup for PCI
With WEP security it is especially important that you get the client setup exactly correct: Get it wrong and it just wont work! For the purposes of this example setup will be for the Pheenet PCI wireless network card. However the principles are the same and will apply equally to any other make or brand of wireless adapter. First of all install the drivers and setup utilities for your wireless card. Now goto to Control Panel (assuming a Windows PC) and click on Network. Next click on the Properties for your wireless network adapter:
Now check that the Channel number, Fragmentation Threshold, Preamble (Long), RTS Threshold, SSID (Wireless), and Transmission Rate match the router setup. Also check that the Network Type is Infrastructure. Now check that the Encryption is set to 128 Bit (to match the router):
You will now need to correctly setup the WEP security key for the clients. For the Pheenet PCI wireless card this means running a separate utility. So, exit the Properties setup for your adapter, saving any changes youve done (you may need to reboot your PC). Now setup the WEP security:

Ensure that the same security settings are used on your clients i.e. 128 Bit and use the same WEP key. The Pheenet setup utility allows you to create the key from a Passphrase. As with the router ensure that you correctly observe character case (i.e. lower or upper) when entering the passphrase. If your adapter key setup doesnt have this passphrase feature than you must manually copy the key numbers from the router setup (e.g. WIRELESS is cd 9a d2 b8a 75 7c c0c 39 c0). Now save the settings for your client (as before you may need to reboot your computer for the changes to take effect). If alls gone according to plan your wireless client should now be able to see the VI router:
If your wireless adapters have a signal strength utility then this can be used to check how good a signal you are getting from the VI router:
If your clients cannot see the router but they could with security off (see above) then the reason for it not working now will be because youve made a mistake with the security setup of either your router or client. Take great care typing in the security settings, particularly the WEP key. A single number wrong and it wont work! You probably wont even be able to use the signal strength utility to see the router.
3.2.3 Using a PCMCIA Wireless card
Setup for the PCMCIA Card (based upon the Pheenet WL-0011 PC card) follows the same guidelines as per using the PCI card i.e. ensure that all settings for VI router and the PCMCIA card are the same. Get any setting incorrect and the chances are it - 10 -
wont work! Also, try setting the configuration without security first of all. Once you have the connection working that way you can then go and add the security. First of all ensure the PCMCIA card is correctly installed with no resource/driver problems. Next goto Control Panel/Network: Next select the Properties of the PCMCIA card (PRISM2 IEEE.) and then go to Advanced: Now its just a case of ensuring that every setting of the card matches the router. First of all check the Fragmentation Threshold the default setting for the router is 2304 (check this on the IEEE 80211b/Advanced screen). Alter the card setting to match.
Next check the Network Type when using the VI router (or an access point) you need to use Infrastructure. The other possible setting is Peer-to-Peer which is the setting you use when configuring and clientto-client setup.
Next ensure that the Preamble is set the same as the router; normal setting is Long TX.

- 11 -

Next check the SSID string: It must be the same for both the router and the PCMCIA card. The default setting for the router is Wireless:
Finally turn Wep off (at least for this initial testing anyway):
Now check that the router settings are the same. So check the SSID matches the PCMCIA card (Wireless). The Channel setup doesnt matter for the PCMCIA card because the card driver will auto-scan until it finds the channel to use. If you do any changes you need to a Submit and then a Save to store the new values.
Next check the Fragmentation Threshold, and the RTS Threshold, and set the Authentication to Open. If you do any changes you need to a Submit and then a Save to store the new values. Finally Reset the modem to activate the new changes.

- 12 -

Now. after rebooting the wireless link should work:

WLAN Bridging Mode

Imagine there are three networks connected at the router: The external WAN network (to your ISP). The internal wired network (via the 4 LAN ports on the router). The internal wireless network (using 802.11b) The Quick Setup Wizard/WLAN configuration allows you to control the way the wired and wireless networks integrate.
The three options are: None this means that clients on the wired network can see the router but cant see any clients on the wireless network and vice-a-versa (wireless clients can see the router but not the wired clients). Bridged Mode This is the default mode and in this mode the wireless network forms an extension of the wired network forming a whole single network with the router hanging off it. In this setup you must ensure that the IP addresses for the - 13 -
wireless clients match and dont clash with the wired clients. e.g. if the router is 192.168.1.1 (as set in Quick Setup/Ethernet) and you have two wired clients with addresses 192.168.1.2 and 192.168.1.3 then typical addresses for wireless clients would be 192.168.1.4 and 192.168.1.5. BUT you could not use the addresses 192.168.0.2 and 192.168.0.3. This wouldnt work and the wireless clients wouldnt be able to see the router or the wired clients. Routed Mode in this mode the wireless segment forms a discrete, separate network from the wired section but IP routeing between the two networks is allowed. Since the wireless network is a separate network then the wireless point at the router needs to be given an IP address. e.g. the wired segment might have 192.168.1.1 for the router end and then clients could be 192.168.1.2 or 192.168.1.3 etc. Then you could tell the WLAN Configuration that the IP address of the wireless point at the router is 192.168.0.1 (with mask 255.255.255.0) and then use client addresses of 192.168.0.2 or 192.168.0.3 etc.

Remember to select Submit after doing any changes and then Reset the modem before using. If using Routed Mode and you want to use DHCP then remember to goto Network Service/DHCP Server and configure the WLAN server.

- 14 -