Aztech SDSL Bridge & Router User's & Technical Manual

User's & Technical Manual V e r s i o n 1 . 2 Protocols Discussed: RFC 2684 (RFC 1483) Ethernet Framing RFC 2684 (RFC 1483) IP Framing RFC 2225 (RFC 1577) IPoA RFC 2516 PPPoE RFC 2364 PPPoA Transparent Bridge

(P/N: 040-513436-121) (Ref: 330) • Virata is a registered trademark of Virata Corporation. • All other company or product names are trademarks or registered trademarks or service marks of their respective owners and are hereby recognized as such.

fire, electric shock and injury. Understand all instructions in the manual. Follow all instruction labels found on the unit. Except for the power adapter supplied, the unit should not be connected to other adapters/power supplies. Never spill liquid of any kind on the unit. Do not place the unit on an unstable stand or table. The unit may drop and become damaged. Do not expose the unit to direct sunlight. Do not put any heat generating devices close to the unit as it may degrade or cause damage to it. Do not stack the unit on top of each other. / Do not put any heavy object on top of the unit Do not use liquid cleaners or aerosol cleaners. Use a soft, dry cloth for cleaning. Product warranty does not apply to damage caused by lightning, power surges or wrong voltage usage.

About This Manual ...................................................................... ix 1. Documentation ........................................................................ 1-1 1.1 Conventions Used ............................................................. 1-2 2. Basics of the SDSL Bridge/Router ........................................... 2-1 2.1 Introduction ...................................................................... 2-1 2.2 System Requirements ........................................................ 2-1 2.3 Network Connections ........................................................ 2-2 2.3.1 Bridge Modem...................................................... 2-2 2.3.2 Router ................................................................. 2-2 2.4 LED Indicators .................................................................. 2-3 2.5 Connection ....................................................................... 2-4 3. Setting Up Local Management ................................................ 3-1 3.1 Setting up the Serial Link ................................................... 3-1 3.2 Configuring the Serial Link ................................................. 3-2 4. Basic Commands on Running Local Management................. 4-1 4.1 Guidelines ........................................................................ 4-1 4.2 Settings and Commands for the Modem .............................. 4-1 4.3 To Disconnect/Connect the SDSL Link ................................. 4-2 5. Configuring Your Router ......................................................... 5-1 5.1 Network Setup Overview .................................................... 5-1 5.2 Configuring the Basics ....................................................... 5-3 5.2.1 Configuring the Basics: Step 1 - Resetting your Router's Configuration ........ 5-4 5.2.2 Configuring the Basics: Step 2 - Configuring the LAN ................................ 5-6 5.2.3 Configuring the Basics: Step 3 - Configuring the WAN ............................... 5-6

(RFC 1483) Ethernet Framing .................. 5-6 ii) Configuring the WAN - For RFC 2684 (RFC 1483) IP Framing ........................... 5-7 iii) Configuring the WAN - For RFC 2225 (RFC 1577) IPoA .................................... 5-8 iv) Configuring the WAN - For RFC 2364 PPPoA .................................................... 5-8 v) Configuring the WAN - For RFC 2516 PPPoE .................................................... 5-10 5.2.4 Configuring the Basics: Step 4 - Configuring the Routing Table ................... 5-11 5.2.5 Configuring the Basics: Step 5 - Enabling IP Forwarding ............................ 5-11 5.2.6 Configuring the Basics: Step 6 - Enabling NAT ...... 5-12 5.2.7 Configuring the Basics: Step 7 - Saving the Configurations ........................ 5-12 5.3 Setting Up NAT Inbound Port Forwarding (Port Address Translation) .................................................. 5-13 5.4 Configuring DHCP Server ................................................... 5-15 5.4.1 Some useful commands for DHCP ......................... 5-15 5.4.2 DHCP Server Illustration ....................................... 5-16 5.5 Configuring DNS Relay ...................................................... 5-17 5.5.1 To Enable DNS Relay (with fixed IP address from your ISP) ..................... 5-17 5.5.2 To Check DNS Relay Server Status ........................ 5-17 5.5.3 To Disable DNS Relay ........................................... 5-17 5.6 Setting Up SNMP .............................................................. 5-18 5.6.1 Read/Write Access ............................................... 5-18 5.6.2 SNMP Trap .......................................................... 5-18 5.7 Setting up Telnet Access .................................................... 5-19 5.8 Configuring Autoloop for IP Interface ................................... 5-19 6. Configuring Your Transparent Bridge ..................................... 6-1 6.1 Network Setup Overview .................................................... 6-1

6.2.1 Step 1: Resetting your Router's Configuration ......... 6-2 6.2.2 Step 2: Configuring the LAN ................................. 6-3 6.2.3 Step 3: Saving the Configurations.......................... 6-3 7. Router Configuration Examples .............................................. 7-1 7.1 Example on RFC 2684 (RFC 1483) IP Framing ................... 7-1 7.2 Example on RFC 2364 PPPoA ........................................... 7-2 8. Configuring PPTP (Point-to-Point Tunnelling Protocol)...... 8-1 8.1 Running the Console Commands ........................................ 8-1 8.1.1 Step 1 - Configuring the LAN ................................ 8-1 8.1.2 Step 2 - Configuring PPP Client and PNS (PPTP Network Server) ......................................... 8-1 8.1.3 Step 3 - Binding to Ethernet Interface ................... 8-2 8.2 Setting Up Dial-Up Networking .......................................... 8-2 8.3 Establishing Your Internet Connection ................................. 8-5 9. Configuring Your Ethernet Card ............................................. 9-1 10. Running DSLTEST.................................................................. 10-1

A.1 TCP/IP Commands ............................................................ A-1 A.1.1 autoloop............................................................... A-1 A.1.2 config .................................................................. A-2 A.1.3 device ................................................................. A-3 A.1.4 ip device ............................................................. A-4 A.1.5 ipatm pvc ............................................................ A-5 A.1.6 relay ................................................................... A-6 A.1.7 rip accept ............................................................ A-6 A.1.8 rip send ............................................................... A-7 A.1.9 route ................................................................... A-8 A.1.10 snmp ................................................................... A-9 A.2 Bridge Commands ............................................................. A-10 A.2.1 device add ........................................................... A-10 A.2.2 device delete ....................................................... A-10 A.2.3 device flush ......................................................... A-11 A.2.4 device list ............................................................ A-11 A.3 PPP Commands ................................................................ A-12 A.3.1 Console object types ............................................. A-12 A.3.2 Console examples ................................................. A-12 A.3.3 echo every ......................................... A-13 A.3.4 pppoe ................................................ A-13 A.3.5 pvc .................................................... A-15 A.3.6 welogin .............................................. A-16 A.3.7 user .................................................................... A-16 A.4 NAT Commands ................................................................ A-17 A.4.1 event ................................................................... A-17 A.4.2 inbound / Port Address Translation / Port Mapping ... A-17 A.4.3 info ..................................................................... A-18 A.4.4 interfaces ............................................................ A-19 A.4.5 ip nat .................................................................. A-19 A.4.6 sessions .............................................................. A-20

A.5.1 config .................................................................. A-21 A.5.2 dnsrelay config ..................................................... A-23 A.5.3 dnsrelay retry ...................................................... A-24 A.5.4 dnsrelay server .................................................... A-24 A.5.5 dnsrelay status .................................................... A-25 A.5.6 dnsrelay trace/untrace .......................................... A-25 A.5.7 help .................................................................... A-26 A.5.8 status .................................................................. A-26 A.5.9 version ................................................................ A-27 A.6 BUN Commands ............................................................... A-28 A.6.1 bun list channels .................................................. A-28 A.7 PPTP Commands .............................................................. A-29 A.7.1 Console object types ............................................. A-29 A.7.2 Console Examples ................................................. A-29 A.7.3 bind .................................................................... A-30 A.7.4 create .................................................. A-31 A.7.5 delete .................................................. A-32 A.7.6 info ...................................................... A-32 A.7.7 list ...................................................................... A-32 A.8 SDSL Commands .............................................................. A-33 A.8.1 SDSL set ............................................................. A-33 A.8.2 SDSL config ......................................................... A-33 A.8.3 SDSL delete configuration line............................... A-34 A.8.4 SDSL watchdog .................................................... A-34 A.8.5 SDSL port configuration ........................................ A-35 Appendix B - Well-Known TCP/UDP Ports...................................... B-1 Appendix C - Quick Start for Router Configurations (Flow Chart) C-1 Appendix D - Frequently Asked Questions ....................................... D-1 Appendix E - Troubleshooting Guide................................................ E-1

This manual is written for users who are familiar with console commands. It contains instructions on how to configure your bridge/router for different network configurations. Chapter 1 - Documentation contains the list of manuals that comes with your bridge/router package and the conventions that are used in the manuals. Chapter 2 - Basics of the SDSL Bridge/Router gives you an introduction to the bridge/router, including basic setups and connections. Chapter 3 - Setting Up Local Management guides you on how to setup and establish a communication link between your bridge/router and PC. With this local mangement established, you can then start issuing console commands. Chapter 4 - Basic Commands on Running Local Management gives some examples of basic commands to run the local management. Chapter 5 - Configuring Your Router guides you on how to configure your bridge/ router for different network configurations. The line protocols discussed are RFC 2684 (RFC 1483) Ethernet Framing, RFC 2684 (RFC 1483) IP Framing, RFC 2225 (RFC 1577) IP over ATM, RFC 2364 PPPoA and RFC 2516 PPPoE. The configuring of NAT Inbound Port Forwarding, DHCP Server, DNS Relay and so on, can also be found in this chapter. Chapter 6 - Configuring Your Transparent Bridge guides you on how to configure your bridge/router for transparent bridge. Chapter 7 - Router Configuration Examples give you bridge/router configuration examples based on RFC 2684 (RFC 1483) IP Framing and RFC 2364 PPPoA. Chapter 8 - Configuring PPTP (Point-to-Point Tunnelling Protocol) guides you on the console commands and setting up of the dial-up networking for PPTP. Chapter 9 - Configuring Your Ethernet Card guides you to configure the IP address of your Ethernet card so that it can work with this router. Chapter 10 - Running DSLTEST tells you how to run the DSLTEST, which can check the Ethernet connection and SDSL line connection. You will be able to find detailed descriptions of the console commands at Appendix A - Commonly Used Commands and the commonly used TCP/UDP Ports at Appendix B - Well-Known TCP/UDP Ports. For an overview of bridge/router configurations, please refer to Appendix C - Quick Start for Router Configurations (Flow Chart). You may find some of your questions answered in Appendix D - Frequently Asked Questions and Appendix E - Troubleshooting Guide.

This User's & Technical Manual is a printed guide that is included with your router package. Please refer to this manual for setting up and connecting your router. It also contains console commands and advanced router configurations that are mostly intended for experienced users. The sections on Frequently Asked Questions and Troubleshooting Guide serve to provide some guidance when encountering problems. DSL Router Commander Software Manual 1 The software manual is a softcopy guide that contains information on DSL Router Commander, a user-friendly user interface that provides a simple way of configuring your network. A Glossary section is also included to describe the terms used in the manual. For queries or problems encountered, you may refer to the Frequently Asked Questions and Troubleshooting Guide found on the User's & Technical Manual. ATMOS Console Commands Reference Manual 1 The reference manual is a softcopy guide that contains the detailed description of the console commands. For advance configurations, you may refer to this manual for their descriptions. 1 These manuals can be found on your SDSL Bridge/Router CD-ROM that comes with your package.

1-2 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ 1.1 Conventions Used • Text that appears in this style are console commands. An example of console command: ip device add ppp_device ether //ppp/DEVICE=1 • Numbers in italics are to be replaced with values from your ISP / System Administrator. In the example: ppp 1 pvc 0 35 ip , you are to replace 1, 0 and 35 with actual values given by your System Administrator / Service Provider. • ISP is the acronym used for Internet Service Provider throughout the manual. • x Numerics in superscript denote further explanation for the text. Explanation can mostly be found at the bottom of the same page. Note boxes contain information that you need to pay special attention to.

2.1 Introduction Congratulations on your purchase of the SDSL Bridge / Router ! SDSL, which stands for Symmetric Digital Subscriber Line, featues the same high data transmission rates both upstream and downstream. It is ideal to business users as it enables them to take full advantage of applications (such as video conferencing, LAN-to-LAN VPN connections and large file transfers) that require high bandwidth in both directions. The SDSL Bridge / Router offers faster and uninterrupted Internet access and is capable of a data transmission rate up to 2.32 Mbps upstream and downstream. This product is an embedded solution that is OS independent. It can be connected to any computer with an Ethernet card. The Ethernet connection allows direct interface to any existing IEEE 802.3 LAN network, providing instant broadband Internet access to LAN networks with minimum hassle. SDSL service providers can offer SDSL services to a multi-user business environment with support for both Static and Dynamic IP Routing, Network Address Translation and Dynamic Host Configuration Protocol Server. This bridge/router features multiple data encapsulation formats for DSL transport over ATM PVCs, including the widely supported ATM protocols RFC 1483 (MPoA), RFC 1577 (IPoA) and RFC 2364 (PPPoA). Utilising Conexant ZipWire™ solution with 2B1Q line encoding used by major SDSL manufacturers, this bridge/router further guarantees interoperability with network providers worldwide. 2.2 System Requirements Hardware • Pentium MMX 233MHz (or above) with Ethernet card (installed with TCP/IP Protocol) • 32MB RAM

2-2 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ • 10MB of free hard disk space • A Serial Port • A CD-ROM Drive • For Multiple PCs - Ethernet Hub with Straight Ethernet cables For Single PC - Crossover Ethernet Cable Software - Operating System • Windows® 95, 98, 98 Second Edition, Me • Windows NT® 4.0 (with Service Pack 3.0 or above), Windows® 2000 2.3 Network Connections This product may operate as a Bridge modem or Router. 2.3.1 Bridge Modem Connection to single PC 2.3.2 Router Connection to multiple PCs in a LAN Router Hub multiple PCs with Ethernet Cards PC with Ethernet Card Ethernet Bridge

2-3 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ 2.4 LED Indicators Ethernet ACT Ethernet Activity: Lights up when the Ethernet is transmitting/receiving data. Ethernet Link Lights up when the Ethernet link is established. SDSL Link Lights up when the SDSL connection is established. SDSL ACT Lights up when the SDSL Line is transmitting/ receiving data. Power Lights up when Power switch is turned ON. When the Power Switch is on, the Power LED will light up. Once the bridge/router is initialized, the SDSL Link LED will start blinking, attempting to establish a connection. Upon successful connection, the SDSL Link LED will remain lit.

2-4 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ 2 For connection to an Ethernet card, please use a cross RJ-45 Ethernet cable. For connection to a Switch or Hub, you may use a normal (straight) RJ-45 Ethernet cable. Power off your computer and any connected devices before connecting your bridge/router ! to Ethernet Card, Switch or Hub 2 The Power Mains Telephone Wall Socket (SDSL line) Power Adaptor PC SDSL Bridge/ Router Line Jack Serial Management Console Ethernet MDI Port DC Power Jack Power Switch 2.5 Connection Switch or Hub

i) Connect one end of a serial cable to the COM Port (9-pin) of your PC and the other end to the Serial Port (9-pin) of your router. ii) Connect your router to the Power Mains via the Power adaptor (that comes with your package). You may refer to Section 2.5 for the illustrated connection. 3. Setting Up Local Management Local management refers to the process of managing and configuring the settings of your router for your network environment. It is done via a PC connected to your router. Before running local management, communication between your router and your PC has to be configured and established for them to 'understand each other'. You need to setup a physical link between your router and the PC via a serial cable as described in Section 3.1. Section 3.2 will show you how to configure the interface link to allow communication between your PC and your router. Setting up of local management needs only to be carried out once for the same PC. However if you are connecting your router to another PC, you will need to run section 3.1 and 3.2 again. Bridge / Router serial cable rear of PC DO NOT POWER ON YOUR ROUTER SWITCH YET !

3-2 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ii) Enter any name for your new connection and click OK. iii) From the Connect To dialog box, select the COM port that your router is connected to and click OK. iv) From the Port Settings, make the following selections for the fields: Bits per second: 9600 Data bits: 8 Parity: None Stop bits: 1 Flow control: None Click OK. This completes configuring the communication link between your router and the PC. 3.2 Configuring the Serial Link i) Run the HyperTerminal program from your PC. (You may also use other Serial Communication Programs. HyperTerminal program is used as an illustration here). For example, if you are running Windows® 98, from your Windows taskbar, click Start > Programs > Accessories > Communications > HyperTerminal. Double-click HyperTerminal.

3-3 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ This indicates successful serial link. (If the messages did not display, power off your router and check the connection of your serial cable. Make sure that the connection is firm and power on the router again.) You may now proceed with the following sections to run local management. v) Power on the Power Mains and the switch on your router. You should see similar messages as illustrated, on your HyperTerminal. (Actual messages vary with different system and firmware version.)

• Type home to return to the initial command prompt. • Type . to repeat previous command. • Press ñ key on your keyboard to display previous command line entered. • Console commands are case-sensitive. Punctuations (e.g. '_' underscore, '-' hyphen, ' ' spacing, etc) must be adhered to strictly. • For detailed description and syntax of console commands, you may refer to Appendix A - Commonly Used Commands on this manual or the ATMOS Console Commands Reference Manual found on the CD-ROM. 4. Basic Commands on Running Local Management This section gives you the basic guidelines on console commands, some settings and commands, and how to connect/disconnect your SDSL link. 4.1 Guidelines The commands in this manual are to be issued at initial command prompt. You may also choose to go to the respective directories and run the commands from there. (For example, upon sdsl> prompt, you need only to type sdsl config to view SDSL port attributes and BUN port declarations.) 4.2 Settings and Commands for the Modem i) To list current status of SDSL bun show port sdsl

4-2 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ii) To set line rate (has to be manually done on both sides CPE and DSLAM) sdsl set sdslphytargetlinerate=kbps config save restart where has to be one of the following values: 144, 160, 192, 208, 272, 384, 400, 416, 528, 768, 784, 1040, 1152, 1168, 1536, 1552, 1568, 2040 or 2320; and both CO (set by SDSL service provider) and CPE must be set to the same rate for connection to establish successfully. iii) To set modem as CO (HTU-C) in back-to-back configurations sdsl set sdslphyhtutype=htu-c config save restart iv) To set modem as CPE (HTU-R) [default] sdsl set sdslphyhtutype=htu-r config save restart v) To monitor traffic bun list channels vi) To view SDSL settings sdsl config 4.3 To Disconnect/Connect the SDSL Link i) To disconnect the SDSL link: bun set port sdsl/sdslactivateline=false (Upon issuing this command, SDSL Link will be disconnected unless the following command is issued.) ii) To re-connect (establish) the SDSL link: bun set port sdsl/sdslactivateline=true

1. Please refer to Appendix C - Quick Start for Router Configurations (Flow Chart) for an overview of the router configurations. 2. All IP addresses and PVC values stated in this manual serve only as examples for better understanding. You are required to replace these values with those given by your SDSL Service Provider/System Administrator. 3. Console commands are case-sensitive. Punctuations (examples: '_' underscore, '-' hyphen, ' ' spacing, etc) must be adhered to strictly. 4. For detailed description and syntax of console commands, you may refer to Appendix A - Commonly Used Commands on this manual or the ATMOS Console Commands Reference Manual found on the CD-ROM. 5.1 Network Setup Overview This section gives an overview of a typical network. The addresses indicated are used as examples throughout the whole manual. You are to replace them with values given by your System Administrator / ISP. PVC=0/35 WAN LAN PC X PC A PC B SDSL Your Router PCs with Ethernet cards WAN IP 202.166.29.154 LAN IP 192.168.1.1 (with NAT) 202.166.30.1 (without NAT) WAN Gateway = 202.166.29.2 Hub/Switch

5-2 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ 1. For configuration without NAT: The range of the IP address used in this example is from 202.166.30.1 to 202.166.30.6 as restricted by subnet mask defined. Network ID : 202.166.30.0 Broadcast ID :202.166.30.7 The ISP will have to create a static route: Network ID : 202.166.30.0 Subnet Mask :ff:ff:ff:f8 Next Hop Gateway : 202.166.29.154 2. For PPPoA and PPPoE: The WAN IP and WAN Gateway will be dynamically assigned by the PPP server. There is no need to specify the WAN IP nor to configure a default route to the WAN Gateway. Configuring the PCs: For PC A: (with NAT) (without NAT) IP = 192.168.1.11 = 202.166.30.2 Subnet mask = 255.255.255.0 = 255.255.255.248 Gateway = 192.168.1.1 = 202.166.30.1 For PC B: (with NAT) (without NAT) IP = 192.168.1.12 = 202.166.30.3 Subnet mask = 255.255.255.0 = 255.255.255.248 Gateway = 192.168.1.1 = 202.166.30.1 For PC X: (with NAT) (without NAT) IP = 192.168.1.23 = 202.166.30.6 Subnet mask = 255.255.255.0 = 255.255.255.248 Gateway = 192.168.1.1 = 202.166.30.1

5-3 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ 5.2 Configuring the Basics Please carry out the following necessary steps to configure your router. Details of each step can be found on the following pages. Step 1: Resetting your Router's Configuration Step 2: Configuring the LAN Step 3: Configuring the WAN Step 4: Configuring the Routing Table Step 5: Enabling IP Forwarding Step 6: Enabling NAT Step 7: Saving the Configurations With the basics configured, you may proceed also with the configurations on the following sections. 5.3 Setting Up NAT Inbound Port Forwarding 5.4 Configuring DHCP Server 5.5 Configuring DNS Relay 5.6 Configuring SNMP 5.7 Setting Up Telnet Access 5.8 Configuring Autoloop for IP Interface

5-4 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ 5.2.1 Configuring the Basics: Step 1 - Resetting your Router's Configuration Your router is set as Transparent Bridge by factory default. Before starting a new configuration, always clear all previous configurations in your router. The following gives the commands to clear: • For PPPoA or PPPoE configurations, enter: ppp 1 clear • For the rest of the configurations, follow the instructions below: a) To delete all the interfaces: (You may type ip device/bridge device to list existing interfaces.) ip device flush bridge device flush To identify your current line protocol configured, type ip device. Check the type and dev file listing to identify the protocol. type dev file Line Protocol ether //bridge OR //edd 2684 (1483) Ethernet Framing* Transparent Bridge* ptp //bun/port=sdsl/rfc1483.. 2684 (1483) IP Framing atm //bun 2225 (1577) IPoA ether //ppp/DEVICE=1 mtu 1500 2364 PPPoA ether //ppp/DEVICE=1 mtu 1492 2516 PPPoE * To further identify whether it is RFC 2684 (RFC 1483) Ethernet Framing or Transparent Bridge, type ip route. For Transparent Bridge, you will see 'Routing table empty' listed.

5-5 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ b) To delete all the subnet mask: (You may type ip subnet to list existing subnet mask.) ip subnet flush c) To delete the route table, if any: (You may type ip route to list existing routes.) ip route flush d) To remove NAT on a WAN interface, if any: (See illustration shown below) To list any existing NAT enabled WAN interface, ip nat If you have an existing NAT enabled WAN interface, you will see nat add To remove the NAT enabled WAN interface, ip nat delete

5-6 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ 5.2.2 Configuring the Basics: Step 2 - Configuring the LAN Configure the LAN with IP address given by your System Administrator. Assuming that the IP address given is 192.168.1.1: ip device add lan ether //edd 192.168.1.1 ip subnet add lan.home . 192.168.1.1 ff:ff:ff:0 5.2.3 Configuring the Basics: Step 3 - Configuring the WAN Configure the WAN with IP address given by your ISP. You may configure your router to one of the following line protocols supported: i) RFC 2684 (RFC 1483) Ethernet Framing ii) RFC 2684 (RFC 1483) IP Framing iii) RFC 2225 (RFC 1577) IPoA iv) RFC 2364 PPPoA v) RFC 2516 PPPoE i) Configuring the WAN - For RFC 2684 (RFC 1483) Ethernet Framing a) To add a bridge device, assuming the PVC given by your ISP is 0/35: For LLC-SNAP encapsulation: bridge device add //bun/port=sdsl/rfc1483=true/mode=llcbridged/ txvpi=0/txvci=35/rxvpi=0/rxvci=35 (all in one line) For VCMUX encapsulation: bridge device add //bun/port=sdsl/rfc1483=true/mode=vcmuxbridged/ txvpi=0/txvci=35/rxvpi=0/rxvci=35 (all in one line) For multiple PVCs, repeat the above commands with the different VPI and VCI values. b) To set the IP configuration of your WAN connection, assuming WAN IP given by your ISP is fixed at 202.166.29.154: ip device add wan ether //bridge 202.166.29.154 ip subnet add wan.home . 202.166.29.154 ff:ff:ff:0 OR To obtain WAN settings automatically from your ISP: ip device add wan ether //bridge dhcp

5-7 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ii) Configuring the WAN - For RFC 2684 (RFC 1483) IP Framing a) To set the IP configuration of your WAN connection, assuming the PVC and WAN IP given by your ISP are 0/35 and 202.166.29.154 respectively: For LLC-SNAP encapsulation: ip device add wan ptp //bun/port=sdsl/rfc1483=true/mode=llcrouted/ txvpi=0/txvci=35/rxvpi=0/rxvci=35 202.166.29.154 (all in one line) ip subnet add wan.home . 202.166.29.154 ff:ff:ff:0 For VCMUX encapsulation: ip device add wan ptp //bun/port=sdsl/rfc1483=true/ mode=vcmuxrouted/txvpi=0/txvci=35/rxvpi=0/rxvci=35 202.166.29.154 (all in one line) ip subnet add wan.home . 202.166.29.154 ff:ff:ff:0 For multiple PVCs, - Repeat (a) with different PVCs values. - Append wan with an underscore ('_') followed by a unique digit for each of the different PVC configured. - Issue a unique WAN IP for each of the different PVC configured Examples: For first PVC value (0/35) ip device add wan_1 ptp //bun/port=sdsl/rfc1483=true/ mode=llcrouted/txvpi=0/txvci=35/rxvpi=0/rxvci=35 202.166.29.154 (all in one line) ip subnet add wan_1.home . 202.166.29.154 ff:ff:ff:0 For second PVC value (0/100), ip device add wan_2 ptp //bun/port=sdsl/rfc1483=true/ mode=llcrouted/txvpi=0/txvci=100/rxvpi=0/rxvci=100 202.166.29.155 (all in one line) ip subnet add wan_2.home . 202.166.29.155 ff:ff:ff:0 append with a unique digit append with a unique digit unique WAN IP

5-8 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ iii) Configuring the WAN - For RFC 2225 (RFC 1577) IPoA a) To set the IP configuration of your WAN connection, assuming the WAN IP given by your ISP is 202.166.29.154: ip device add wan atm //atm 202.166.29.154 ip subnet add wan.home . 202.166.29.154 ff:ff:ff:0 b) To set the WAN configuration, assuming the PVC and WAN Gateway given by your ISP are 0/35 and 202.166.29.2 respectively: ip ipatm pvc add wan sdsl 0/35 remoteip 202.166.29.2 OR To obtain WAN settings automatically from your ISP: ip device add wan atm //atm dhcp ip ipatm pvc add wan sdsl 0/35 remoteip 202.166.29.2 iv) Configuring the WAN - For RFC 2364 PPPoA You can do back-to-back connection by setting up one router as CO and another as CPE. To set up your router as CPE, do the following a to c: a) To set the IP configuration of your WAN connection. The PPP module supports multiple simultaneously connections, so we explicitly specify Device 1 here. (This is required for PPP dial-out session): ip device add ppp_device ether //ppp/DEVICE=1 b) To set the PPP channel configuration, assuming the PVC given by your ISP is 0/35. CHAP authentication is used in this example. Replace CHAP with PAP if you are using PAP authentication. ISP will supply the myuserid and mypassword. ppp 1 pvc 0 35 ip ppp 1 welogin myuserid mypassword chap ppp 1 enable c) To check the PPP connection every 10 seconds. (This is to allow the PPP session to automatically re-establish itself after an SDSL link disruption and re-connection.): ppp 1 echo every 10

5-9 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ To set up your router as CO, do the following a to c: a) To set the IP configuration of your WAN connection. The PPP module supports multiple simultaneously connections, so we explicitly specify Device 2 here. (This is required for PPP dial-out session): ip device add ppp_device ether //ppp/DEVICE=2 b) To set the PPP channel configuration, assuming the PVC and CPE WAN IP given by your ISP are 0/35 and 202.166.29.154 respectively. CHAP authentication is used in this example. Replace CHAP with PAP if you are using PAP authentication. ISP will supply the myuserid and mypassword. ppp user add myuserid pwd mypassword chap ppp 2 pvc 0 35 ip listen ppp 2 interface 2 ppp 2 remoteip 202.166.29.154 ppp 2 theylogin chap ppp 2 enable c) To check the PPP connection every 10 seconds. (This is to allow the PPP session to automatically re-establish itself after an SDSL link disruption and re-connection.): ppp 2 echo every 10 d) For both CPE and CO: If you do not want to enable NAT, you may enable the PPP IP Unnumbered feature (availability will depend on your router package). PPP IP Unnumbered allows you to enable IP processing on a serial interface without assigning it an explicit IP address. The ip unnumbered interface can 'borrow' the IP address of another interface that is already configured on the router, thereby conserving network and address space. (Assuming your LAN Subnet mask is ff:ff:ff:f8.) ppp 1 disable ppp 1 unnumbered enable ppp 1 lansubnet ff:ff:ff:f8 ppp 1 enable config save

5-10 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ When the PPP link is established, you will notice that your LAN IP address actually changes to the address of the WAN IP obtained from the PPP Server. Your WAN IP address now becomes 0.0.0.1, a dummy IP address. To maintain IP connectivity to the router's LAN Port before and after establishing the PPP unnumbered link, you are advised to pre-configure the LAN IP to that of the given WAN IP. (You may refer to section 5.2, Step 2 - Configuring the LAN.) v) Configuring the WAN - For RFC 2516 PPPoE a) To set the IP configuration of your WAN connection. The PPP module supports multiple simultaneously connections, so we explicitly specify Device 1 here. The MTU (Maximum Transmit Unit) size for PPPoE must also be specified as being 1492: ip device add ppp_device ether //ppp/DEVICE=1 mtu 1492 b) To configure PPP device 1, assuming the PVC given by your ISP is 0/35. ppp 1 pppoe 0 35 c) CHAP authentication is used in this example. Replace CHAP with PAP if you are using PAP authentication. ISP will supply the myuserid and mypassword. ppp 1 welogin myuserid mypassword chap ppp 1 enable d) To check the PPP connection every 10 seconds. (This is to allow the PPP session to automatically re-establish itself after an SDSL link disruption and re-connection.): ppp 1 echo every 10 e) If you do not want to enable NAT, you may enable the PPP IP Unnumbered feature (availability will depend on your router package). PPP IP Unnumbered allows you to enable IP processing on a serial interface without assigning it an explicit IP address. The ip unnumbered interface can 'borrow' the IP address of another interface that is already configured on the router, thereby conserving network and address space. (Assuming your LAN Subnet mask is ff:ff:ff:f8.) ppp 1 disable ppp 1 unnumbered enable

5-11 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ppp 1 lansubnet ff:ff:ff:f8 ppp 1 enable config save When the PPP link is established, you will notice that your LAN IP address actually changes to the address of the WAN IP obtained from the PPP Server. Your WAN IP address now becomes 0.0.0.1, a dummy IP address. To maintain IP connectivity to the router's LAN Port before and after establishing the PPP unnumbered link, you are advised to pre-configure the LAN IP to that of the given WAN IP. (You may refer to section 5.2, Step 2 - Configuring the LAN.) 5.2.4 Configuring the Basics: Step 4 - Configuring the Routing Table i) Adding a Default route through a Gateway (No default route is required for PPPoA and PPPoE line protocols.) Assuming the WAN Gateway given by your ISP is 202.166.29.2: ip route add default 0.0.0.0 202.166.29.2 0:0:0:0 ii) Dynamic Routing If dynamic routing is not required, it is recommended to disable this feature to reduce unnecessary traffic: ip rip accept all none ip rip send all none 5.2.5 Configuring the Basics: Step 5 - Enabling IP Forwarding To enable IP forwarding between your LAN and WAN, ip relay all

5-12 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ 5.2.6 Configuring the Basics: Step 6 - Enabling NAT To enable NAT on a WAN interface, i) For RFC 2684 (RFC 1483) Ethernet Framing/1483 IP Framing/1577 IPoA Assuming the WAN interface name is wan: ip nat add wan ii) For RFC 2364 PPPoA / RFC 2516 PPPoE ip nat add ppp_device You may proceed to section 5.3 to set up your NAT Inbound Port Forwarding. 5.2.7 Configuring the Basics: Step 7 - Saving the Configurations config save

5-13 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ 5.3 Setting Up NAT Inbound Port Forwarding (Port Address Translation) When you have enabled NAT on the WAN interface, in order for others to reach your HTTP (Web) Server, FTP Server and so on at your LAN, you need to activate the NAT Inbound Port forwarding. The following gives an illustration of a Web Server (IP=192.168.1.100) and FTP Server (IP=192.168.1.101) connected to your router. For PC A: IP = 192.168.1.2 Subnet mask = 255.255.255.0 Gateway = 192.168.1.1 For PC B: IP = 192.168.1.3 Subnet mask = 255.255.255.0 Gateway = 192.168.1.1 NAT Inbound Port Forwarding is not applicable for Transparent Bridge configuration. For Web Server: IP = 192.168.1.100 Subnet mask = 255.255.255.0 Gateway = 192.168.1.1 For FTP Server: IP = 192.168.1.101 Subnet mask = 255.255.255.0 Gateway = 192.168.1.1 PVC=0/35 PC A PC B PCs with Ethernet cards Your Router LAN IP 192.168.1.1 SDSL Web Server FTP Server WAN LAN WAN Gateway = 202.166.29.2 WAN IP 202.166.29.154 Hub/Switch

5-14 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ i) To allow Web request to your HTTP (Web) Server (assuming the server is using default TCP Port 80): nat inbound add wan 80/tcp 192.168.1.100 ii) To allow FTP request to your FTP Server (assuming the server is using default TCP Port 21): nat inbound add wan 21/tcp 192.168.1.101 iii) To show the current IP forwarding rules: nat inbound list e.g. # Interface Port/Proto New IP address 1 wan 80/tcp 192.168.1.100 2 wan 21/tcp 192.168.1.101 iv) To remove a rule: nat inbound delete 1 where 1 refers to the '#' corresponding to the interface you want to remove. v) To remove all rules: nat inbound flush You may refer to Appendix B - Well-Known TCP/UDP Ports for most of the commonly used TCP/UDP Ports.

5-15 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ 5.4 Configuring DHCP Server The following DHCP configuration information may be used with any one of the line protocols illustrated in Section 5.2, Step 3 - Configuring the WAN to produce a complete system. DHCP is not applicable to Transparent Bridge configuration. 5.4.1 Some useful commands for DHCP i) To list down the configuration file: dhcpserver config ii) To delete the last command line: dhcpserver config delete iii) To remove all previous configuration lines: dhcpserver config flush iv) To show dhcpserver status: dhcpserver status v) To allow changes to take effect immediately: dhcpserver config confirm dhcpserver reset vi) To save changes permanently: config save Any changes to the dhcpserver configurations must be followed by dhcpserver config confirm, dhcpserver reset and config save.

5-16 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ 3 Replace with the LAN IP address of your router if you are using DNS relay. Else, replace with the DNS provided by your ISP 5.4.2 DHCP Server Illustration All the PCs IP addresses, subnet mask and Gateway are obtained from your router running the DHCP Server. i) For all PCs configuration: From the Network Properties (right-click on Network Neighborhood to select Properties) window of your Ethernet Card, set the IP Address option at the TCP/IP Properties to 'Obtain an IP address automatically' option. ii) Sample of DHCPSERVER Configurations: dhcpserver config add allow unknown-clients; config add subnet 192.168.1.0 netmask 255.255.255.0 config add { config add range 192.168.1.2 192.168.1.100; config add option subnet-mask 255.255.255.0; config add option routers 192.168.1.1; config add option domain-name-servers IP 3,IP 3; config add } config confirm iii) For changes to take effect immediately: dhcpserver reset iv) For permanent change: config save Upon typing config confirm, you should see messages similar to the one shown below: dhcpserver: Config changes confirmed, use “flashfs update” to commit. : Changes will not work correctly until restart - do this ASAP. If you are prompted with 'Bad configuration file' after entering config confirm, please refer to the Appendix E - Troubleshooting Guide - 'I am prompted with 'Bad configuration file, please review' error message after entering config confirm'.

5-17 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ 5.5 Configuring DNS Relay 5.5.1 To Enable DNS Relay (with fixed IP address from your ISP) dnsrelay server IP 4 config save restart For RFC 2364 / RFC 2516: To enable DNS Relay (with IP address obtained automatically from your ISP), assuming the PPP module device is 1. ppp 1 enableprimarydns relay config save restart Ensure that the DNS Server address of the DHCP Server is set to the LAN IP address of your router. Example, (section 5.4.2 - DHCP Server Illustration, step ii.) : : config add option domain-name-servers 192.168.1.1 : (assuming the IP address of your router is 192.168.1.1.) 5.5.2 To Check DNS Relay Server Status dnsrelay status 5.5.3 To Disable DNS Relay dnsrelay config reset 4 Replace with the DNS provided by your ISP.

5-18 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ 5.6 Setting Up SNMP 5.6.1 Read/Write Access The following illustrates the commands for write/read access. i) Add this command only when no IP has been assigned to the ether interface of your router. The IP should have the same subnet as the Ethernet card and must be unique in the network.: ip device add lan ether //edd 192.168.1.1 ip subnet add lan.home . 192.168.1.1 ff:ff:ff:0 For example, IP for Ethernet card : Dynamic IP obtained from far end server, range: 192.168.1.2 to 192.168.1.100 IP for router : Fixed at 192.168.1.1 ii) To enable SNMP read and write access: ip snmp access write stm 5 192.168.1.11 6 (Assuming the IP address of the PC that you want to enable SNMP from is 192.168.1.11.) OR To enable SNMP read access: ip snmp access read public 5 192.168.1.11 6 (Assuming the IP address of the PC that you want to enable SNMP from is 192.168.1.11.) iii) To save: config save restart 5.6.2 SNMP Trap i) To add a trap destination: snmp trap add [] 5 SNMP community names given by your System Administrator 6 Specifying this optional IP address will permit users to SNMP only from this specific PC with the correct password.

5-19 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ii) To delete a trap destination: snmp trap delete [] iii) To delete all traps destination: snmp trap flush iv) To list trap(s) destination: snmp trap list Example: >snmp trap add community_name 192.168.1.5 21 >snmp trap list trap add community_name 192.168.1.5 21 >snmp trap delete community_name 192.168.1.5 21 >snmp trap list No trap destinations set 5.7 Setting up Telnet Access (By factory default, Telnet Access is enabled. If the feature has been removed from your router, you may carry out the following steps to enable it.) Ensure that your router has SNMP write access enabled (see Section 5.6 - Setting Up SNMP) before you proceed with the Telnet Access setup. To enable Telnet to your router: ip portname add telnet 23/tcp config save The Telnet password will be your SNMP write access community name that you have entered during SNMP setup (section 5.6, step (ii)). 5.8 Configuring Autoloop for IP Interface ip device add loop loop 127.0.0.1 ip autoloop on config save By default, autoloop is disabled. Once the above commands are issued, you are able to ping to your router's LAN IP.

1. All IP addresses and PVC values stated in this manual serve only as examples for your better understanding. You are required to replace these values with those given by your SDSL Service Provider/System Administrator. 2. Console commands are case-sensitive. Punctuations (examples: '_' underscore, '-' hyphen, ' ' spacing, etc) must be adhered to strictly. 3. For description and syntax of the console commands, you may refer to Appendix A - Commonly Used Commands for the syntax and descriptions. 6.1 Network Setup Overview PC with Ethernet Card Bridge PVC=0/35 SDSL Your Router 6.2 Configuring the Basics Please carry out the following necessary steps to configure your bridge/router. Details of each step can be found on the following pages. Step 1: Resetting your Bridge/Router's Configuration Step 2: Configuring the LAN Step 3: Saving the Configurations

6-2 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ Your router is set as Transparent Bridge by factory default. In Transparent Bridge, only one of the PCs connected to your router can have access to the Internet at any one time. 6.2.1 Step 1: Resetting your Router's Configuration Before starting a new configuration for your router, always remember to clear all previous configurations in your router. The following shows the commands and explanations. • For PPPoA or PPPoE configurations, enter: ppp 1 clear • For the rest of the configurations, follow the instructions below: a) To delete all the interfaces: (You may type ip device/bridge device to list existing interfaces.) ip device flush bridge device flush b) To delete all the subnet mask: (You may type ip subnet to list existing subnet mask.) ip subnet flush c) To delete the route table, if any: (You may type ip route to list existing routes.) ip route flush d) To remove NAT on a WAN interface, if any: (See illustration following this list of commands) To list any existing NAT enabled WAN interface, ip nat If you have an existing NAT enabled WAN interface, you will see nat add To remove the NAT enabled WAN interface, ip nat delete

6-3 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ 6.2.2 Step 2: Configuring the LAN i) To add Ethernet device to the bridge: bridge device add edd ii) To add a bridge device, assuming the PVC given by your ISP is 0/35: For LLC-SNAP encapsulation: bridge device add //bun/port=sdsl/rfc1483=true/mode=llcbridged/ txvpi=0/txvci=35/rxvpi=0/rxvci=35 (all in one line) For VCMUX encapsulation: bridge device add //bun/port=sdsl/rfc1483=true/mode=vcmuxbridged/ txvpi=0/txvci=35/rxvpi=0/rxvci=35 (all in one line) For multiple PVCs, repeat the above commands with the different VPI and VCI values. iii) Set the IP address of your bridge/router ether port with the address given by your System Administrator. (This is required in order to run the DSL Router Commander.): ip device add bridge ether //bridge 192.168.1.1 ip subnet add bridge.home . 192.168.1.1 ff:ff:ff:0 6.2.3 Step 3: Saving the Configurations config save

All IP addresses and PVC values stated in this manual serve only as examples for your better understanding. You are required to replace these values with those given by your ISP / System Administrator. For better understanding, this section contains examples on configuring your router. Do not duplicate these examples for your configuration. Check with your ISP / System Administrator for actual IP addresses, PVC values and options to use. 7.1 Example on RFC 2684 (RFC 1483) IP Framing i) To reset all IP configurations: ppp 1 clear ip device flush bridge device flush ip subnet flush ip route flush ii) Configuring the LAN: ip device add lan ether //edd 192.168.1.1 ip subnet add lan.home . 192.168.1.1 ff:ff:ff:0 iii) Configuring the WAN (for LLC-SNAP encapsulation): ip device add wan ptp //bun/port=sdsl/rfc1483=true/mode=llcrouted/ txvpi=0/txvci=35/rxvpi=0/rxvci=35 202.166.29.154 (all in one line) ip subnet add wan.home . 202.166.29.154 ff:ff:ff:0 iv) Configuring the Routing Table: ip route add default 0.0.0.0 202.166.29.2 0:0:0:0 v) To disable dynamic routing: ip rip accept all none ip rip send all none vi) Enabling IP Forwarding: ip relay all

7-2 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ vii) Enabling NAT: ip nat add wan viii) Save configurations: config save 7.2 Example on RFC 2364 PPPoA i) To reset all IP configurations: ppp 1 clear ip device flush bridge device flush ip subnet flush ip route flush ii) Configuring the LAN: ip device add lan ether //edd 192.168.1.1 ip subnet add lan.home . 192.168.1.1 ff:ff:ff:0 iii) Configuring the WAN (for CHAP authentication): ip device add ppp_device ether //ppp/DEVICE=1 ppp 1 pvc 0 35 ip ppp 1 welogin myuserid mypassword chap ppp 1 enable ppp 1 echo every 10 iv) To disable dynamic routing: ip rip accept all none ip rip send all none v) Enabling IP Forwarding: ip relay all vi) Enabling NAT: ip nat add ppp_device vii) Save configurations: config save

8.1 Running the Console Commands 8.1.1 Step 1 - Configuring the LAN Configure the LAN with IP address given by your System Administrator. Assuming that the IP address given is 192.168.1.1: ip device add lan ether //edd 192.168.1.1 ip subnet add lan.home . 192.168.1.1 ff:ff:ff:0 8.1.2 Step 2 - Configuring PPP Client and PNS (PPTP Network Server) Assuming the values for channel and tunnel given by your System Administrator are 2 and 1 respectively, and the PVC values given by your ISP are 0/35: ppp 2 pvc 0 35 ip ppp 2 interface 0 ppp 2 tunnel 1 ppp 2 enable 1. PPTP protocol is not supported in Windows® 95. 2. Ensure that you have already setup your local management as described in Chapter 3 - Setting Up Local Management. 3. All IP addresses and PVC values stated in this manual serve only as examples for your better understanding. You are required to replace these values with those given by your SDSL Service Provider/System Administrator. 4. Console commands are case-sensitive. Punctuations (examples, '_' underscore, '-' hyphen, ' ' spacing, etc) must be adhered to strictly. 5. For detailed description and syntax of console commands, you may refer to Appendix A - Commonly Used Commands on this manual or the ATMOS Console Commands Reference Manual found on the CD-ROM.

8-2 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ 8.1.3 Step 3 - Binding to Ethernet Interface Configure the PPTP process to bind to an Ethernet interface and to setup tunnel 1 to listen (waiting for the PNS to initiate the connection). Assuming that the IP address given is 192.168.1.1. pptp bind 192.168.1.1 pptp 1 create listen config save 8.2 Setting Up Dial-Up Networking i) From your Windows desktop, right-click on Network Neighborhood icon and select Properties. ii) Click on Add. iii) Select Adapter and click Add. iv) From the Manufacturers list, scroll down and select Microsoft. From the Network Adapters list, select Dial-Up Adapter and click OK. (DO NOT remove the existing Dial-Up Adapter from the network component list.) You should see Dial-Up Adapter #2 (VPN Support) listed in the components list as shown. v) Repeat step(ii) and step(iii). From the Manufacturers list, scroll down and select Microsoft. From the Network Adapters list, select Microsoft Virtual Private Networking Adapter and click OK.

8-3 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ You should see Microsoft Virtual Private Networking Adapter listed in the components list as shown. Click OK. vi) Proceed to create a new dial-up icon. Locate your Dial-up Networking and double-click on Make New Connection. (For example, if you are using Windows® 98, from your Windows desktop, click on Start > Programs > Accessories > Communications > Dial-Up Networking. Double-click on Make New Connection.) vii) At the following prompt, enter any name for the computer you are dialing to. Select Microsoft VPN Adapter from the drop-down list and click Next.

8-4 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ viii) Enter the LAN address of your router and click Next. ix) Click Finish to complete the process.

8-5 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ 8.3 Establishing Your Internet Connection From your Dial-Up Networking folder, double-click on your newly-created icon. Enter the User name and Password given by your ISP and click Connect. Upon successful authentication from your ISP, you will be connected to the Internet.

Carry out the following procedures to configure the IP address of your Ethernet Card to work with your router, unless you are using your router as a bridge. You need to configure the IP address of your Ethernet card with the address given by your SDSL Service Provider or your System Administrator. i) Power on your computer. ii) From your Windows desktop, right-click on Network Neighborhood. Select Properties. iii) From the Configuration tab, select TCP/IP–>3Com EtherLink III ISA [3C509b-TPO] in PnP mode 7 and click Properties. (Re-install your Ethernet card if you are not able to locate your Ethernet protocol.) 7 This manual uses TCP/IP–>3Com EtherLink III ISA [3C509b-TPO] in PnP mode Ethernet card as an illustration. Please select the Ethernet card that is listed in your system. iv) Select the IP Address tab. Check with your SDSL Provider or your System Administrator on which IP option (Dynamic/Fixed IP address) to be used.

9-2 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ This completes your Ethernet card configurations. Your bridge/router is now ready. Select the option "Obtain an IP address automatically" and click OK. This completes your Ethernet Card configuration. (For DHCP users, your IP address changes every time when you log on to the Internet. It is important that you check your IP address assigned to you every time you log on, before proceeding to configure your router.) a) For Dynamic IP address (DHCP) b) For Fixed IP address Select the option "Specify an IP address". Enter the IP Address as given by your SDSL Service Provider or System Administrator. Enter the Subnet Mask as 255.255.255.0. Check with your SDSL Provider or your System Administrator on which IP address (Public/Private IP address) to be used.

9-3 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ Select the Gateway tab. Enter the gateway value as given by your SDSL Service Provider or System Administrator. Click Add followed by OK. This completes your Ethernet card configurations. Your bridge/router is now ready. Select the DNS Configuration tab. Click "Enable DNS" and enter your given DNS Server Search Order address. Click Add.

connection. i) Make sure the Ethernet and SDSL Lines are properly connected. From your Installation CD-ROM, navigate to \Tools\DSLTEST. Double-click on the file DSLTEST.exe. Alternatively, click Install DSLTest from the Menu when the SDSL Bridge/ Router CD-ROM is placed in your computer's CD-ROM drive. (It is highly recommended that you copy the entire Tools directory to your harddisk. This allows easy access to the utility.) You may do selective tests by clicking the box next to the corresponding test names. A tick in the box means that the particular test will be performed. Ethernet Interface Test: This is to test whether the driver for your Ethernet Card has been installed successfully. Modem Test: This is to test the physical SDSL line connection, that is the telephone cable connection between your router and your Telephone Wall Socket. At the same time, it will check the connection rate of your router, whether it falls below the performance level. If the first test failed, the next test will be skipped. Proceed to fix the problem first before running DSLTEST again.

10-2 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ii) Ensure that you have powered on your router and click Test. At the following prompt, click OK to proceed. (Please refer to the Troubleshooting Guide should your Modem Test fail.) See the following table for the possible test results. Result Description PASS The test is successful. FAIL You will be prompted on the error. Click OK, fix the error and click Test again. SKIP The test is not carried out as the previous test has failed. (Error messages will be prompted to highlight the area of the failure, if any. Please refer to the Troubleshooting Guide for details on the error messages.) To enable DSLTEST log file, you are recommended to copy the entire Tools directory from the Installation CD-ROM to your harddisk. From Tools\DSLTEST directory, double-click DSLTEST.exe. Click the SDSLTEST icon (at the top-left corner) of the DSL Test dialog box. Select Settings. Click on the square box beside Enabling Logging to create a log file. At LogFile text box, enter the path of your log file where you want it to be saved.

By default autoloop is disabled. The autoloop command is hidden, not shown by ip help. Example: > ip autoloop autoloop off > ip device # type dev file IP address device ether ether //nice mtu 1500 192.168.2.1 device loop loop - mtu 2048 127.0.0.1 > ip ping 127.0.0.1 ip: ping - reply received from 127.0.0.1 > ip ping 192.168.2.1 ip: ping - transmit error: Host is down (rc=62) > ip autoloop on > ip ping 192.168.2.1 ip: ping - reply received from 192.168.2.1 Appendix A - Commonly Used Commands

A-2 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ A.1.2 config Syntax: config [save] Description: Displays the IP configuration (not including the snmp configuration), or saves it in flash memory. The functionality of the config command is also accessible in the standard way through the config process (e.g. config print ip), if that process is present. However, when accessed through the config process, the snmp configuration is included. Example: > ip config device add ether ether //nice mtu 1500 192.168.2.1 device add vlane ether //lane mtu 1500 192.168.55.1 subnet add vlane.home . 192.168.55.0 ff:ff:ff:00 subnet add ether.home . 192.168.2.0 ff:ff:ff:00 rip send ether 2 rip send vlane 2 rip accept ether 1 2 rip accept vlane 1 2 autoloop on route add default 0.0.0.0 192.168.2.7 00:00:00:00 2 # MAN relay ether ether relay ether vlane relay vlane vlane ipatm lifetime 60 # IP host table: # Port table: router 520/UDP snmp 161/UDP tftp 69/UDP telnet 23/TCP > ip config save Updating flash filing system ... done ip: configuration saved

A-3 ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ ○ A.1.3 device Syntax: device device add [] [mtu ] [] device add wan ptp //bun/port=sdsl/rfc1483=true/mode=/txvpi=/txvci=/rxvpi=/rxvci= (all in one line) device delete device flush Description: Displays the interfaces that IP is configured to use, or adds an interface to the configuration, or deletes an interface, or all interfaces, from the configuration. The commands to change the configuration take effect immediately. However, it is necessary to save the configuration (e.g. with ip config save) to set the changes permanently. The options used with this command are described below: • is an arbitrary label for the interface, which is used in referring to it in subsequent commands. (It is often chosen to be the same as , though this is perhaps slightly confusing.) • specifies the class of interface: Ethernet-like, IP-over-ATM, or loopback. For an Ethernet-like or IP-over-ATM interface, specifies the file name that will be opened to access the underlying device (which must support the Emerald interface for an Ethernet-like interface, and the Blue interface, at least, for an IP-over-ATM interface). • For a loopback interface, is not used, and can just be specified as “-“ or omitted altogether. • specifies the MTU (maximum transmission unit); that is, the size of the largest datagram (excluding media-specific headers) that IP will attempt to send through the interface. If no MTU is specified, the default unit will be 1500. • is the IP address that this system uses on the interface. The supported values for are Class Applicable file(s) Ethernet ether //bridge //edd IP Framing ptp //bun IP-over-ATM atm //atm Loopback loop -