ADSL Ethernet Router Series 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 Te c h n i c a l M a n u a l Version 1.
© Copyright, December 2001. All Rights Reserved. (P/N: 040-513447-151) (Ref: 9009000) • 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.
Product warranty does not apply to damage caused by lightning, power surges or wrong voltage usage. Safety Guidelines Adhere to the following safety guidelines when using your unit to reduce the risk of 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.
Contents Safety Guidelines ......................................................................... iii About This Manual ....................................................................... ix Conventions Used ........................................................................ x 1. 2. 3. Setting Up Local Management ................................................... 2-1 1.1 Setting up the Serial Link ................................................... 2-1 1.2 Configuring the Serial Link ...
4. 3.3.4 Configuring the Basics: Step 4 - Configuring the Routing Table ................ 4-12 3.3.5 Configuring the Basics: Step 5 - Enabling IP Forwarding ......................... 4-12 3.3.6 3.3.7 Configuring the Basics: Step 6 - Enabling NAT .... 4-12 Configuring the Basics: Step 7 - Saving the Configurations ...................... 4-12 3.4 Setting Up NAT Inbound Port Forwarding (Port Address Translation) ................................................... 4-13 3.5 Configuring DHCP Server .....
. Configuring PPTP (Point-to-Point Tunnelling Protocol) ........... 7-1 6.1 Running the Console Commands ......................................... 7-1 6.1.1 Step 1 - Configuring the LAN ............................. 7-1 6.1.2 6.1.3 6.2 Step 2 - Configuring PPP Client and PNS (PPTP Network Server) ................................................ 7-1 Step 3 - Binding to Ethernet Interface ................ 7-2 Setting Up Dial-Up Networking ........................................... 7-2 6.2.
Appendix A - Commonly Used Commands ......................................... A-1 A.1 A.2 TCP/IP Commands ............................................................. A-1 A.1.1 autoloop ........................................................... A-1 A.1.2 A.1.3 A.1.4 config ............................................................... A-2 device .............................................................. A-3 ip device .......................................................... A-4 A.1.5 A.1.6 A.1.
A.5 A.6 DHCP Server Commands .................................................... A-25 A.5.1 config ............................................................... A-25 A.5.2 dnsrelay config .................................................. A-27 A.5.3 A.5.4 A.5.5 dnsrelay retry .................................................... A-28 dnsrelay server .................................................. A-28 dnsrelay status .................................................. A-29 A.5.6 A.5.7 A.5.8 A.5.
About This Manual This manual is written for users who are familiar with console commands. It contains instructions on how to configure your router for different network configurations. Chapter 1 - Setting Up Local Management guides you on how to setup and establish a communication link between your router and PC. With this local mangement established, you can then start issuing console commands. Chapter 2 - Basic Commands on Running Local Management gives the basic commands to run the local management.
○ ○ ○ ○ ○ ADSL Ethernet Router Series Technical Manual Conventions Used Text that appears in this style are console commands. 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 from your System Administrator. Numerics in superscript denote further explanation for the text.
1. 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 1.1. Section 1.
○ ○ ○ ○ ○ 1 — Setting Up Local Management ii) iii) Enter any name for your new connection and click OK. 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.
1 — Setting Up 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.) 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.
2. Basic Commands on Running Local Management This section gives you the basic guidelines on console commands, how to check your router performances, router entries, to disconnect/connect your ADSL link and to toggle between modes. 2.1 Guidelines At the prompt for password, enter either 'stm' or 'password' (without the quotes). These are factory default passwords. (If you have changed the default password at the DSL Router Commander - SNMP option, enter your new password.
○ ○ ○ ○ ○ 2 — Basic Commands on Running Local Management 2.2 i) Checking Your Router Performances To check for line parameters: bsp line ii) To check for line performance: bsp perf iii) To check for line status: bsp mode iv) To check net data rate: bsp channel v) To monitor traffic: bun list channels 2.3 Checking Your Router Entries Messages displayed are the settings you have saved.
2 — Basic Commands on Running Local Management ○ ○ ○ ○ ○ 2.4 To Disconnect/Connect the ADSL Link i) To disconnect the ADSL link: bsp down (Upon issuing this command, ADSL Link will be disconnected unless the following command is issued.) ii) To re-connect (establish) the ADSL link: bsp up 2.5 To Toggle between Various Modes i) To set router to multimode (auto-detect G.dmt, G.Lite & ANSI TI.413): bsp multi ii) To force router into detecting G.
3. Configuring Your Router 3.1 Configuration Flow Chart Setup Your Serial Link (Chapter 1) Transparent Bridge ? Yes No (section 3.3.1) Reset Router Configurations (section 3.3.2) Configure Your LAN settings (section 3.3.3) Configure Your WAN settings RFC 2684 Ethernet Framing RFC 2684 IP Framing RFC 2225 IPoA RFC 2364 PPPoA RFC 2516 PPPoE Transparent Bridge [section 3.3.3, (i)] [section 3.3.3, (ii)] [section 3.3.3, (iii)] [section 3.3.3, (iv)] [section 3.3.
○ ○ ○ ○ ○ 3 — Configuring Your Router 3.2 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 ADSL Service Provider /System Administrator. 2. Console commands are case-sensitive. Punctuations (examples, '_' underscore, '-' hyphen, ' ' spacing, etc) must be adhered to strictly. 3.
3 — Configuring Your Router ○ ○ ○ ○ ○ 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 ADSL Service Provider 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 For PPPoA and PPPoE: 2. The WAN IP and WAN Gateway will be dynamically assigned by the PPP server.
○ ○ ○ ○ ○ 3 — Configuring Your Router 3.3 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.
3 — Configuring Your Router ○ ○ ○ ○ ○ 3.3.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 remember to clear all previous configurations in your router. To identify your current line protocol configured, type ip device. Check the type and dev file listing to identify the protocol.
○ ○ ○ ○ ○ 3 — Configuring Your Router 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.
3 — Configuring Your Router ○ ○ ○ ○ ○ 3.3.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 3.3.3 Configuring the Basics: Step 3 - Configuring the WAN Configure the WAN with IP address given by your ADSL Service Provider.
○ ○ ○ ○ ○ 3 — Configuring Your Router 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 ADSL Service Provider are 0/35 and 202.166.29.154 respectively: For LLC-SNAP encapsulation: ip device add wan ptp //bun/port=atm/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.
3 — Configuring Your Router ○ ○ ○ ○ ○ 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 ADSL Service Provider 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 atm configuration, assuming the PVC and WAN Gateway given by your ADSL Service Provider are 0/35 and 202.166.29.2 respectively: ip ipatm pvc add wan atm 0/35 remoteip 202.166.
○ ○ ○ ○ ○ 3 — Configuring Your Router iv) Configuring the WAN - For RFC 2364 PPPoA 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 ADSL Service Provider is 0/35. CHAP authentication is used in this example.
3 — Configuring Your Router ○ ○ ○ ○ ○ 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 ADSL Service Provider is 0/35.
○ ○ ○ ○ ○ 3 — Configuring Your Router 3.3.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 ADSL Service Provider is 202.166.29.2: ip route add default 0.0.0.0 202.166.29.
3 — Configuring Your Router ○ ○ ○ ○ ○ 3.4 Setting Up NAT Inbound Port Forwarding (Port Address Translation) When you have enabled NAT on the WAN interface, in order for people 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.
○ ○ ○ ○ ○ 3 — Configuring Your Router 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. iv) # Interface Port/Proto New IP address 1 2 wan wan 192.168.1.100 192.168.1.
3 — Configuring Your Router ○ ○ ○ ○ ○ 3.5 Configuring DHCP Server The following DHCP configuration information may be used with any one of the line protocols illustrated in Section 3.3.3, Step 3 - Configuring the WAN to produce a complete system. DHCP is not applicable to Transparent Bridge configuration. 3.5.
○ ○ ○ ○ ○ 3 — Configuring Your Router 3.5.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 / My Network Places 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.
3 — Configuring Your Router ○ ○ ○ ○ ○ 3.6 Configuring DNS Relay 3.6.1 To Enable DNS Relay (with fixed IP address from your ADSL Service Provider) dnsrelay server IP 3 config save restart For RFC 2364 / RFC 2516: To enable DNS Relay (with IP address obtained automatically from your ADSL Service Provider), 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.
○ ○ ○ ○ ○ 3 — Configuring Your Router 3.7 Setting Up SNMP 3.7.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.
3 — Configuring Your Router ○ ○ ○ ○ ○ 3.7.2 SNMP Trap i) To add a trap destination: snmp trap add [] 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.
○ ○ ○ ○ ○ 3 — Configuring Your Router 3.9 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.
4. Configuring Your Transparent Bridge 4.1 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 ADSL Service Provider / System Administrator. 2. Console commands are case-sensitive. Punctuations (examples, '_' underscore, '-' hyphen, ' ' spacing, etc) must be adhered to strictly. 3.
○ ○ ○ ○ ○ 4 — Configuring Your Transparent Bridge 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. 4.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.
4 — Configuring Your Transparent Bridge ○ ○ ○ ○ ○ 4.2.
5. Router Configuration Examples 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 ADSL Service Provider / System Administrator. For your better understanding, this section contains examples on configuring your router. Do not duplicate these examples for your configuration.
○ ○ ○ ○ ○ 5 — Router Configuration Examples vii) Enabling IP Forwarding: ip relay all vii) Enabling NAT: ip nat add wan viii) Save configurations: config save 5.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.
6. Configuring PPTP (Point-to-Point Tunnelling Protocol) 1. PPTP protocol is not supported in Windows® 95. 2. Ensure that you have already setup your local management as described in Chapter 1 - 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 ADSL Service Provider / System Administrator. 4. Console commands are case-sensitive.
○ ○ ○ ○ ○ 6 — Configuring PPTP (Point-to-Point Tunnelling Protocol) 6.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 6.2 Setting Up Dial-Up Networking i) From your Windows desktop, right-click on Network Neighborhood icon and select Properties.
6 — Configuring PPTP (Point-to-Point Tunnelling Protocol) ○ ○ ○ ○ ○ You should see Microsoft Virtual Private Networking Adapter listed in the components list as shown on your left. Click OK. vi) You may be prompted for your Windows 98 CD-ROM. Place the CD-ROM into your CD-ROM Drive and follow the instructions prompted. Restart your system when prompted. vii) 6.2.1 Creating Dial-Up Networking i) From your Windows desktop, right-click on Network Neighborhood icon and select Properties.
○ ○ ○ ○ ○ 6 — Configuring PPTP (Point-to-Point Tunnelling Protocol) v) 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.) vi) At the following prompt, enter any name for the computer you are dialing to.
6 — Configuring PPTP (Point-to-Point Tunnelling Protocol) ○ ○ ○ ○ ○ 6.2.2 Establishing Your Internet Connection i) From your Dial-Up Networking folder, double-click on your newly-created icon. ii) Enter the User name and Password given by your ADSL Service Provider and click Connect. Upon successful authentication from your ADSL Service Provider, you will be connected to the Internet.
Appendix A - Commonly Used Commands A.1 TCP/IP Commands A.1.1 autoloop Syntax: autoloop [on|off] Description: Displays or sets the autoloop setting. Configuration saving saves this information. 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 device ether ether //nice mtu 1500 device loop loop mtu 2048 > ip ping 127.0.0.1 ip: ping - reply received from 127.0.0.1 > ip ping 192.168.2.
○ ○ ○ ○ ○ A- Commonly Used Commands 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.
A- Commonly Used Commands ○ ○ ○ ○ ○ A.1.3 device Syntax: device device add [] [mtu ] [] device add wan ptp //bun/port=atm/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.
○ ○ ○ ○ ○ A- Commonly Used Commands Example: ip device add wan ptp //bun/port=atm/rfc1483=true/mode=llcrouted/ (all in one line) txvpi=0/txvci=35/rxvpi=0/rxvci=35 202.166.29.154 A.1.4 ip device Syntax ip device add [mtu ] [|dhcp] ip device Description The ip device add command adds an interface to the configuration of the IP stack. The last parameter of the command is normally the IP address of the interface.
A- Commonly Used Commands ○ ○ ○ ○ ○ A.1.5 ipatm pvc Syntax: ipatm ipatm ipatm ipatm pvc pvc add [] /[][/] pvc delete [] pvc flush Description: Lists configured PVCs for use by IP-over-ATM; configures another; deletes one; or deletes all. is the name of an interface configured for IP-over-ATM using PVCs. is the VCI to use for the PVC. The range of possible VCIs depends on the system.
○ ○ ○ ○ ○ A- Commonly Used Commands A.1.6 relay Syntax: relay relay all | [] [forward] Description: Displays or sets what forwarding TCP/IP will do between interfaces.
A- Commonly Used Commands ○ ○ ○ ○ ○ A.1.7 rip accept Syntax: rip accept [all | ] [none | ] 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 1 2).
○ ○ ○ ○ ○ A- Commonly Used Commands A.1.8 rip send Syntax: rip send [all | ] [none | ] Description: Controls which version or versions of RIP (RIP version 1, RFC 1058, or RIP version 2, RFC 1723) TCP/IP will use to broadcast routing information on each interface. If both versions are specified, routing information is broadcast in duplicate, once using each version. Specifying all affects all interfaces except the loopback interface (if any). Configuration saving saves this information.
A- Commonly Used Commands ○ ○ ○ ○ ○ A.1.9 route Syntax: route route add [ [ []]] route delete route flush Description: Lists routes; adds or deletes a static route; or deletes all routes. is an arbitrary name specified to route add that can be used to delete the route using route delete. is the IP address of the network being routed to (only those bits of corresponding to bits set in are relevant).
○ ○ ○ ○ ○ A- Commonly Used Commands The original time-out, if the route is not permanent; The name of the interface (if known) that will be used for the route; An asterisk (*) if the route was added recently and RIP has not yet processed the change (the asterisk should disappear within 30 seconds, when RIP next considers broadcasting routing information). Configuration saving saves this information. (Only the routes configured by the route command are saved or displayed by config .
A- Commonly Used Commands ○ ○ ○ ○ ○ A.2 Bridge Commands Console commands should be prefixed with bridge in order to direct them to the bridge process. A.2.1 device add Syntax: device add device add //bun/port=atm/rfc1483=true/mode=/ txvpi=/txvci=/rxvpi=/rxvci= (all in one line) Description: This command adds a device to the bridge configuration. Attempts to add the bridge itself or an existing device to the bridge are rejected.
○ ○ ○ ○ ○ A- Commonly Used Commands A.2.2 device delete Syntax: device delete Description: This command deletes a device from the bridge configuration. To make the changes permanent, the configuration needs to be saved. The syntax of the device name is the same as that for the device add command. Configuration saving saves this information. Example: device delete //bun/port=atm/rfc1483=true/mode=llcbridged/txvpi=0/ txvci=35 /rxvpi=0/rxvci=35 (all in one line) See also: device add (A.2.
A- Commonly Used Commands ○ ○ ○ ○ ○ A.2.4 device list Syntax: device list Description: This command lists all the devices that are currently attached to the bridge. It does not show the stored configuration (which can be seen with the config print command). Example: device list See also: ○ ○ ○ ○ device add (A.2.1), device delete (A.2.2), device flush (A.2.
○ ○ ○ ○ ○ A- Commonly Used Commands A.3 PPP Commands Console commands should be prefixed with ppp in order to direct them to the ppp process. A.3.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.
A- Commonly Used Commands ○ ○ ○ ○ ○ A.3.3 echo every Syntax: echo every 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.
○ ○ ○ ○ ○ A- Commonly Used Commands A.3.4 pppoe Syntax: pppoe [[] ] [ip] [acname ""][servicename ""] pppoe none Description: Attach an ATM PVC to the given PPP channel using the PPPoE encapsulated driver located on the lower layer. The port can be specified (only for a multi-port device), and the VPI (default is 0), and the VCI. This is used for the configuration of a PPPoE localized client only. No server support is offered.
A- Commonly Used Commands ○ ○ ○ ○ ○ Configuration saving saves this information. By default a channel has no connection information.
○ ○ ○ ○ ○ A- Commonly Used Commands A.3.5 pvc Syntax: pvc [[] ] [ip|mac] [listen] pvc none Description: Attach an ATM PVC to the given PPP channel. The port can be specified (only for a multi-port device), and the VPI (default is 0), and the VCI. The allowable range of port, VPI, VCI depends on the atm driver. Normal limits are 0 only for port, 0 only for VPI, 1..1023 for VCI. If a single argument none is supplied, any current connection is torn down.
A- Commonly Used Commands ○ ○ ○ ○ ○ A.3.6 welogin Syntax: welogin [pap|chap] welogin none Description: This command describes how we should log in to the far end when a connection is established. A name and password are supplied, and whether these should be used with the PAP or CHAP authentication protocol. CHAP is the default. To remove this information on a channel, call welogin with a single argument of none.
○ ○ ○ ○ ○ A- Commonly Used Commands A.4 NAT Commands This section describes console commands provided by the nat process. A.4.1 event Syntax: nat event [n] Description: This command displays or sets the current level of event tracing in the NAT process. Larger values of n result in more verbose trace output, for example: All trace messages are printed as background output, and therefore will not be displayed asynchronously on the console unless the event show command has been issued.
A- Commonly Used Commands ○ ○ ○ ○ ○ A.4.2 inbound / Port Address Translation / Port Mapping Syntax: nat nat nat nat inbound inbound inbound inbound list add / [quiet] delete <#> flush Description: This command enables the user to list or to set up a series of rules, to determine what happens to incoming traffic. By default all incoming packets, other that packets arriving in response to outgoing traffic, will be rejected.
○ ○ ○ ○ ○ A- Commonly Used Commands A.4.3 info Syntax: 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.
A- Commonly Used Commands ○ ○ ○ ○ ○ A.4.4 interfaces Syntax: nat interfaces Description: The nat interfaces command displays the IP router ports on which NAT is currently enabled. For each of these, a status and IP address is listed. The IP address is discovered automatically from the IP stack. The status shows the user whether NAT is currently operational on that interface (enabled), or whether NAT is still waiting to find out the interfaces IP address (not ready).
○ ○ ○ ○ ○ A- Commonly Used Commands A.4.6 sessions Syntax: nat sessions [all | summary] Description: The nat sessions command displays a list of currently active NAT sessions on the interface . 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.
A- Commonly Used Commands ○ ○ ○ ○ ○ A.5 DHCP Server Commands This section describes console commands provided by the dhcpser ver process. A.5.1 config Syntax: dhcpserver config [add |confirm|delete|flush] Description: This command displays or edits the current configuration of the DHCP server. To display current configuration, provide no arguments to the command. Use of the add argument adds the line to the configuration file.
○ ○ ○ ○ ○ A- Commonly Used Commands Range range [ dynamic-bootp ] low-address [ high-address ]; For any subnet on which addresses will be assigned dynamically, there must be at least one range statement. The range statement gives the lowest and highest IP addresses in a range. All IP addresses in the range should be in the subnet in which the range statement is declared.
A- Commonly Used Commands ○ ○ ○ ○ ○ subnet 192.168.219.0 netmask 255.255.255.0 { range 192.168.219.10 192.168.219.30; max-lease-time 5000; } > dhcpserver config flush Configuration file flushed. > dhcpserver config —Current DHCP server configuration (Issue dhcpserver config confirm followed by flashfs update to confirm new configuration) —> A.5.
○ ○ ○ ○ ○ A- Commonly Used Commands A.5.3 dnsrelay retry Syntax: dnsrelay retry Description: This command sets the maximum number of retries the DNS relay is allowed to perform in the event of connection or transmission failure. The retry value must be a number between 1 and 10. Example: > dnsrelay retry 4 Connection retry value set to 4. > A.5.4 dnsrelay server Syntax: dnsrelay server Description: This command tells the DNS relay which DNS server to contact.
A- Commonly Used Commands ○ ○ ○ ○ ○ A.5.5 dnsrelay status Syntax: dnsrelay status Description: This command displays the status of the DNS relay, including whether or not it knows which DNS server to try to contact and, if so, whether or not it has successfully connected to the server. Example: > dnsrelay status DNS relay status DNS server address discovery incomplete. > dnsrelay server 192.168.219.50 DNS server address set to 192.168.219.50. > dnsrelay status DNS relay status DNS server address : 192.
○ ○ ○ ○ ○ A- Commonly Used Commands A.5.6 dnsrelay trace/untrace Syntax: dnsrelay [trace options] Description: This command enables or disables tracing for the DNS relay. If no arguments are given the command lists the current tracing options enabled.
A- Commonly Used Commands ○ ○ ○ ○ ○ A.5.7 help Syntax: dhcpserver help Description: This command provides help on the various console commands provided by the DHCP server. Specifying a command name gives detailed help on the command. Specifying all gives detailed help on all available commands. Example: > dhcpserver help Help is available on the following commands: config A.5.
○ ○ ○ ○ ○ A- Commonly Used Commands A.5.9 version Syntax: dhcpserver version Description: This command displays the current version number of the DHCP software. Example: > dhcpserver version DHCP Version 1.
A- Commonly Used Commands ○ ○ ○ ○ ○ A.6 BUN Commands Command parsing is case insensitive. Whitespace may be used to separate distinct arguments. Any prefix of the string bun to the command line is ignored. A.6.1 bun list channels Syntax: list channels [] Description: List all open connections on the specified port. If no port is nominated, all channels on all ports will be displayed. The channels are shown with their identification number and a selection of useful attributes.
○ ○ ○ ○ ○ A- Commonly Used Commands A.7 PPTP Commands A.7.1 Console object types The PPTP process provides a number of PPTP connection tunnels. A tunnel consists of a control connection between the local PAC and a PNS, and a data connection (known as a call) through which a number of PPP connections or channels may be multiplexed. The current state of each tunnel is saved by config save. A.7.2 Console Examples These examples are for configuration of the PPTP Access Concentrator (PAC).
A- Commonly Used Commands ○ ○ ○ ○ ○ A.7.3 bind Syntax bind |any|none Description: Specify which local interface to bind a listener to for incoming control connections. If ipaddress is specified, PPTP will listen on port 1723 on that interface only for incoming control connections. Typically this will be the IP address of the local side network interface. If any is specified, PPTP will accept control connections on any interface.
○ ○ ○ ○ ○ A- Commonly Used Commands A.7.4 create Syntax create |listen Description Create a tunnel object. If ipaddress is specified, the tunnel is associated with a remote PNS (PPTP Network Server) at that IP address. The control connection is not actually established until the use of tunnel is requested by PPP, or an explicit connect is issued. If listen is specified, the tunnel is allocated for use by an incoming control connection from a remote PNS.
A- Commonly Used Commands ○ ○ ○ ○ ○ A.7.5 delete Syntax delete Description Delete a tunnel object (the opposite of create). If the tunnel is currently connected, any active data connections across the tunnel are terminated and the control connection is closed. Example To delete PPTP Tunnel 1, enter: pptp 1 delete See also create on section A.7.4 using the option. A.7.
Appendix B - Well-Known TCP/UDP Ports Service Port Number/Port Type File Transfer Protocol (FTP) Data 20/tcp FTP Commands 21/tcp Telnet 23/tcp Simple Mail Transfer Protocol (SMTP) Email 25/tcp Domain Name Server (DNS) 53/tcp and 53/udp Trivial File Transfer Protocol (TFTP) 69/udp finger 79/tcp World Wide Web (HTTP) 80/tcp POP3 Email 110/tcp SUN Remote Procedure Call (RPC) 111/udp Network News Transfer Protocol (NNTP) 119/tcp Network Time Protocol (NTP) 123/tcp and 123/udp News 14
