Instruction/ maintenance manual of the product A02-RA(Atmos)_ME01 Atlantis Land
Go to page of 112
I-Storm ADSL Router Console Commands Reference Manual (v1.01) A02-RA(Atmos)_ME01.
Contents 1. About this Guide 1.1 Introduction 1.2 Scope 1.3 Typographical conventions 2. ATMOS Console commands 2.1 General notes 2.2 event 2.3 restart 2.4 uptime 2.5 version 2.6 <process>, <process> <command> 2.7 . (history mechanism) 2.
3.4 ethertype 3.5 filter 3.6 filterage 3.7 flush 3.8 info 3.9 interface 3.10 portfilter 3.11 spanning 3.12 status 3.13 version 4. BUN Console commands 4.1 Introduction 4.2 help 4.3 version 4.4 build 4.5 config 4.6 list config 4.7 list devices 4.8 show device 4.
6.1 config 6.2 help 6.3 pool 6.4 reset 6.5 status 6.6 trace 6.7 version 7. NAT Console commands 91 7.1 event 7.2 help 7.3 interfaces 7.4 inbound 7.5 info 7.6 protocol 7.7 sessions 7.8 stats 7.9 version 7.10 dump 7.11 fragments 7.12 hashtable 8. PPP Console commands 8.
8.18 <channel> qos 8.19 <channel> remoteip 8.20 <channel> svc 8.21 <channel> theylogin 8.22 <channel> tunnel <n> <tunnel protocol> <dial direction> 8.23 <channel> welogin 8.24 bcp 8.25 interface <n> localip 8.
10.16 ipatm abort 10.17 ipatm arp 10.18 ipatm arpserver 10.19 ipatm files 10.20 ipatm help 10.21 ipatm lifetime 10.22 ipatm pvc 10.23 ipho stname 10.24 nat 10.25 noerrors 10.26 norelay 10.27 ping 10.28 portname 10.29 protocols 10.30 relay 10.31 restart 10.
10.54 ? 11. TFTP Console commands 11.1 connect 11.2 get 11.3 help 11.4 init 11.5 list 11.6 put 11.7 trace 11.8 version Index.
1. About this Guide 1.1 Introduction This document is a reference guide for prof essional user to handle ADSL modem well. It describes the command line interface (CLI) with examples. 1.2 Scope Commands for legacy drivers (eg. ATM and Ethernet drivers) are not included here.
equipment, including safety information..
2. Console and Telnet commands 2.1 General notes Apart from the chips commands, the commands are supported by the standard console. Example output is shown only to clarify the description of the commands; the actual output is not necessarily in exactly the same format.
2.4.1 Syntax uptime 2.4.2 Description Displays the time for which the system has been up. 2.5 version 2.5.1 Syntax version 2.5.2 Description Displays the system type and version. 2.6 <process>, <process> <command> 2.6.1 Syntax <process> <command> <process> home home <command> 2.
ls - list ISFS files rm <file> - remove file from ISFS cat <file> - show file contents version - displays version number Use “home” to return to “mymachine>” prompt mymachine is.
2.8 @ commands 2.8.1 Syntax @@<line> @ <line> @<process> <line> @<process> 2.8.2 Description Lines beginning with the @ character are intercepted by the console even when the console device is bound to a file.
2.10 list 2.10.1 Syntax list 2.10.2 Description The list command lists the active console devices (referred to as thread s) and files. For each console device, if it is bound to a file then the list shows which file it is bound to; if background o utput is enabled on that de vice then the list indicates the fact.
2.12.1 Syntax tell <process> <command> 2.12.2 Description Sends the command as a TELL message to a sp ecific process. Note that for many processes the tell can be omitted. 2.12.3 Example mymachine> tell hswctrl portinfo a1 port type vers flags A1 25Mbps 1QUA mast uni30 ilmi netside tx8khz manconfig 2.
2.16 bind <process>, unbind 2.16.1 Syntax bind <process> unbind 2.16.2 Description The former command binds this console device to the specified process – tha t is, binds this device to the fil e, if any, opened for read by that process, and binds every file opened by the process to this device.
Exits from ATMOS to the boot ROM. Note - This command is now deprecated and provides no useful output. 2.21 help 2.21.1 Syntax help ? help <command> 2.21.2 Description The help command lists all chips commands. ? is a synonym for this command; help <command> displays more detailed help on the specified command.
Reads the byte (r b), word (r w) or half-word (r h) at a specified address, or writes a specified value to the byte (w b), word (w w) or half-word (w h).
console tell command.).
3. Bridge Console commands 3.1 device add 3.1.1 Syntax device add <device> 3.1.2 Description This command adds a device to the bridge c onfiguration. Attempts to add the bridge itself or an existing device to the bridge are rejected. Attempts to add devices which don’t suppor t the Cyan interface are rejected.
attribute promiscuous selects the promiscuity behaviour of the dri ver. The driver requires, at configuration time, to be la yered with the BUN utopia and nec98408 devices, in order to be used.
This command lists all the devices that are cu rrently attached to the bridge. It does not show the stored configuratio n (which can be seen with the config print command). 3.3.3 Example device list 3.3.4 See also device add on page 36 and device delete on page 38.
started. Creation failures occur when there is no room left in the filter table for a new entry. 3.5.3 Example filter 3.6 filterage 3.6.1 Syntax filterage [<age>] 3.6.2 Description This command sets, or displays if no arguments are given, the filter table ageing time.
command is a synony m for this command. 3.8.3 Example info 3.9 interface 3.9.1 Syntax interface [sub-command] 3.9.2 Description This command accesses the ethernet support library sub-commands for the bridge itself, not for the devices which are attached to it.
If no arguments are given, the current settings for each port are displayed. 3.10.3 Example 1 portfilter 2 3 4 5 portfilter 3 1 3.10.4 Example 2: portfilter 2 all portfilter 3 all 3.11 spanning 3.11.1 Syntax spanning [sub-command] 3.11.2 Description The spanning tree commands are only availa ble if it has been compiled in to the bridge.
version.
4. BUN Console commands 4.1 Introduction 4.1.1 Scope A description is provided of the use of console commands. No information on implementing additional commands is given in this chapter: implementers of new BUN devices may provide access to diagnostic or status information by implementing attributes to handle these tasks.
explicit (ie.: from a device: configuration request). Device names may contain upper or lower case letters, but use case insensitive matching. portname The name of a port.
For example: set port atm/usercomment="This is a comment string" set port atm/usercommand=<An alternative syntax> Within either form of quoted section, the corresponding close quote character may be embedded by prefixing with a backslash.
4.4.1 Syntax build 4.4.2 Description Display information about compile-time build options. For example, if tracing or debug code has been compiled into the image. 4.4.3 Example build 4.5 config 4.5.1 Syntax config <configurationstring> 4.5.2 Description Issue a configuration request to BUN.
Each request is displayed together with any relevant information. In the cas e of failed requests, an error code is given and the point at which parsing of the configuration string failed is highlighted.
The device list shows which driver code is invoked by this device. For a compiled in device, this will just be the device itself. For a compound device, this will be the list of devices linked to form the compound driver. 4.8.3 Example show device utopia show device atm25 4.
4.12 show port 4.12.1 Syntax port <portname> 4.12.2 Description Display detailed information about a port. This command enumerates all attributes for a port and displays them on the console. It is useful to determine the properties of a port. 4.
4.15 list all open channels 4.15.1 Syntax list all open channels [<portname> ] 4.15.2 Description This command is similar to the list channels command. The list channels command shows channels which are either enabled or op e n. The list all open channels command only shows channels which are ope n.
effect of any changes will be device dependent. Use this command with extreme caution. The same warnings about an application closing and reopening a channel handle appl y as they do for the show channel command.
5. DHCP-client Console commands 5.1 config 5.1.1 Syntax dhcpclient config 5.1.2 Description This command displays the current configuration of the DHCP client, incl uding selected DHCP options. 5.1.3 Example bd3000> dhcpclient conf ig --- DHCP client configuration file: ‘//isfs/dhclient.
trace untrace 5.3 pool 5.3.1 Syntax dhcpclient pool [verbose] 5.3.2 Description This command displays the state of the memory pool being used by the DHCP client. Should the client ever run out of memory, use of this command is helpful in determining the optimum memory pool size for the client.
----------+-----------------+----------------+-----------------+----------- *ACTIVE* | 192.168.219.151 | 192.168.219.1 | 255.255.255.0 | 31 seconds --------------------------------------------------------------------------- 5.5 trace 5.5.1 Syntax dhcpclient trace <trace option> 5.
5.7.2 Description The ip device add command adds an interface to the configuration of the IP stack. The last parameter of the command would normally the IP address of the interface; use of the string dhcp causes the IP address to be discovered by the DHCP client software.
6. DHCP-server Console commands This chapter describes the DHCP-server Console commands..
6.1 config 6.1.1 Syntax dhcpserver config [add <text>|confirm|delete|flush] 6.1.2 Description This command displays or edits the current configuration of the DHCP server. To display current configuration, provide no argum ents to the command. • Use o f the add option adds the line <text> to the configuration file.
6.2 help 6.2.1 Syntax dhcpserver help <command|all> 6.2.2 Description This command provides help on the various console commands provided by the ATMOS DHCP server. Specifying a command name gives detailed help on the command. Specifying all gives detailed help on all available commands.
dhcpserver reset 6.4.2 Description This command prompts the server to do a warm reset of itself. This has the effect of bringing the server back up as if the system had been reboot ed, except that the lease database is preserved in SDRAM between resets.
192.168.219.8 | <unknown> | Expired 192.168.219.9 | <unknown> | Expired 192.168.219.10 | Foobarbozzle | Expired 6.6 trace 6.6.1 Syntax dhcpserver trace <trace option> 6.6.2 Description This command enables or disables tracing for the DHCP s erver.
7. NAT Console commands.
This chapter describes the NAT (Net work Address Translation) Console commands. 7.1 event 7.1.1 Syntax nat event [n].
7.1.2 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.
Name Status IP address Ethernet enabled 194.129.40.2 pppnot ready – 7.4 inbound 7.4.1 Syntax nat inbound list nat inbound add <i/f> <port>/<proto> <new IP> [quiet] nat inbound delete <#> nat inbound flush 7.
2 r1483 21/tcp 192.168.219.40 bd3000> nat inbound dele te 2 7.5 info 7.5.1 Syntax nat info 7.5.2 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.
7.6.3 Example bd3000> nat protocols Name Port/IP protocol ftp 21/tcp 7.7 sessions 7.7.1 Syntax nat sessions <i/f> [all | summary] 7.7.2 Description The nat sessions command displays a list of currently active NAT sessions on the interface <i/f >.
The nat stats command does not provide the total number of packets or bytes transferred, as this information is norma lly available from the device driver on the interface which NAT is filtering.
nat fragments <i/f name> 7.11.2 Description This command is only available in debug builds. nat fragments prints information on t he queues in which NAT holds fragmented IP datagrams, displaying the IP datagram identifier, the num ber of fragments queued and a NAT session pointer for each queue.
8.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 the se objects permitted in a system is configured using the config resource console command. • The current state of each object is saved by config sav e.
pvccreate a1 32 a1 33 (at the switch console, if it is a Virata Switch) ppp event 5 (at the console of the PPP ATMOS system ) ppp 1 pvc 32 ppp 2 pvc 33 ppp 1 enable ppp 2 enable (they shou ld now swap packets and synchronise) ppp 1 status This should show that the two ends are connected.
ppp 2 remoteip 192.168.200.2 ppp 2 enable (and the corresponding setup for each of the channels 3 to 8 as well) Clients can now dial in to this server, be allocated IP addresses and traffic will be sent to and from the router.
8.5.1 Syntax <channel> discard [<size>] 8.5.2 Description Discard is a PPP LCP packet type, which is like the Echo packet type but does not generate a return. This can be used for more careful tests of data tra nsfer on the link, for instance at sizes near the negotiated MRU.
8.8 <channel> enable 8.8.1 Syntax <channel> enable 8.8.2 Description Set the enable flag for a PPP channel. By default, this is disabled. In the PPP state machine, this flag sets the PPP link to ope n. If it is already open, there is no effect.
Learning occurs in this direction only. Setting hdlc to 0 clears this learned state. Configuration saving does not save the learned state. 8.11 <channel> info 8.11.1 Syntax <channel> info [all] 8.11.2 Description Provide information about the current settings of this channel.
8.14.1 Syntax <channel> lcpmaxfailure [<n>] 8.14.2 Description Set the Max-Failure parameter for LCP, as described in Section 4.6 of RFC166 1. This is the maximum number of consecutive Configure Naks that will be sent before assuming that parameter negotiation is not converging.
8.17 <channel> pvc 8.17.1 Syntax <channel> pvc [[<port>] <vpi>] <vci> [ip|mac] [listen] <channel> pvc none 8.17.2 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.
8.18 <channel> qos 8.18.1 Syntax <channel> qos [cbr|ubr] [pcr <pcr-tx> [<pcr-rx>]] 8.18.2 Description Specify that the VC for a PPP channel shoul d be Constant Bit Rate or Unspecified Bit Rate, and (optionally for UBR) give a Peak Cell Rate for the connection.
Specify that the VC for a PPP channel should be an SVC (i.e. created by signalling). This can either be by listening for an incoming call, or by making an out going call to a specified ATM address. The outgoing call or listen occurs immediatel y. If the call fails it will be retried after a few seconds.
This command specifies that when using this channel, the user must log on using the specified protocol, and that they must provide any name/password com bination which has been defined for that protocol, using the user command. To remove this information on a channel, call theylogin with a single argum ent of non e.
8.24.1 Syntax bcp stp|nostp 8.24.2 Description This command describes parameters for BCP, the Bri dge Control Protocol, which is used to transport MAC (Ethernet) packet s over the PPP link.
can be attached to the bridge or router, like other Ethernet devices in ATMOS. It also provides an ifEntry to SNMP pro viding basic information about traffic through t he interface. This command shows the basic information about byte and packet traffic through the interface, in SNMP terms.
9.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 a nd a PNS, and a data connection (known as a call) through which a number of PPP connecti ons or channels may be m ultiplexed.
The rest of this section details the individual console commands provided. 9.2 bind 9.2.1 Syntax: bind <ipaddress>|any|none 9.2.2 Description: Specify which local interface to bind a list ener to for incoming control connections. If ipaddress is specified, PPTP will listen on port 1723 on that interface only for incoming control connections.
produce an error message. 9.4 <tunnel> create 9.4.1 Syntax <tunnel> create <ipaddress>|listen 9.4.2 Description: Create a tunnel object.
9.6.2 Description Explicitly disconnect a tunnel (the opposite of conne c t). All data connections across the tunnel are terminated and the control connection is closed.
9.9.1 Syntax list 9.9.2 Description Lists all currently created tunnel objects and the IP address of the rem ote PNS associated with each one. 9.10 version 9.10.1 Syntax version 9.10.2 Description Provide the version number for the source of the pptp process.
The table below shows the commands that can be issued to the IP process in TELL messages or on the console to its stdin stream (after typing @i p, for example). It shows which are mentioned in the ip help outpu t, and which set some configuration that is saved in flash memory.
uptime version ● ? ● The key for the above table is shown below: Symbol Description ● Yes — May be inserted explicitly in //isfs/resolve (Eg. for debugging purpos es), but not saved by ipconfig sav e.
mymachine> ip abort 3 10.3 arp 10.3.1 Syntax arp add <i/f> <IP address> <MAC address> arp delete <i/f> <IP address> arp flush arp [list] arp help [all|<cmd>] 10.
arp add ether 192.168.50.1 08:00:20:19:9a:d9 # forever arp add ether 192.168.50.5 7 00:20:af:2e:fa:3c # 3m13s mymachine> ip arp flush mymachine> ip arp # flane ARP table is empty # ether ARP table is empty mymachine> ip arp arp add flane 192.
device ether ether //edd mtu 1500 192.168.2.1 device loop loop - mtu 2048 127.0.0.1 mymachine> ip ping 127.0.0.1 ip: ping - reply received from 127.0.0.1 mymachine> ip ping 192.168.2.1 ip: ping - transmit error: Host is down (rc=62) mymachine> ip autoloop on mymachine> ip ping 192.
snmp 161/UDP tftp 69/UDP telnet 23/TCP mymachine> ip config save Updating flash filing system ... done ip: configuration saved 10.7 device 10.7.1 Syntax device [list] device add <i/f> <type> [<file>] [mtu <size>] [<IP address>] device delete <i/f> device flush 10.
config.h ETHERNET_DEVICE_NAME “s//edd” If a default file is not defined, the name ether is not supported. However, it is still possible to define devices of type ether with an explicit filename.
setting means that the IP address should be learned by DHCP. For exam ple: ip device add ether ether dhcp Note that DHCP is not supported on all interface types.
device ether ether //edd mtu 1500 192.168.2.1 device flane ether //lec1 mtu 1500 192.168.55.1 # DISABLED 10.9 enable 10.9.1 Syntax enable [<i/f> [mtu <size>] [<IP address>]] 10.9.2 Description Enables all interfaces, or just a specified interface.
The etherfiles command is hidde n, not shown by ip hel p. 10.11.3Example mymachine> ip etherfiles ether: //edd flane: //lec1 atm: (no ethernet device) 10.12 files 10.12.1Syntax files [full] files <assoc> 10.12.2Description Lists the files (associations) that other app lications (or, internally, RIP) have opened on //i p.
//ip/TYPE=UDP/LPORT=69/TIMEOUT_CONX=1000/TIMEOUT_LISTEN=0/TIMEOUT_IDLE=0/RETRY_CONX=2/TOS =routine/DELAY=normal/THROUGHPUT=normal/RELIABILITY=normal/BUFFERRX=off/BUFFER_TXSIZE=-1/ BUFFER_RXSIZE=-1/FRAGMENT=on/TTL=60/OPTIONS=off/CHECKSUM=on/TIMEOUT_USER=540000 10.
Commands are: ? arp config device disable enable help ipatm nat norelay ping relay rip route routes snmp stats subnet version ‘.’ repeats the last command Type "ip help all" or "ip .
10.18.1Syntax ipatm arpserver [<i/f> [<ATM address>|here]] 10.18.2Description Displays or sets the ATMARP server used for an interface, which must be an IP-over-ATM interface using SVCs. The interface name is optional when displaying: if omitted, the ATMARP servers for all su ch interfaces are listed.
6: on atm Idle 7: on atm Idle 8: on atm Idle 9: on atm Idle 10: on atm Idle 10.20 ipatm help 10.20.1Syntax ipatm help [<cmd>|all] 10.20.2Description Displays help on ipatm subcommands.
mymachine> ip ipatm lifetime 90 Idle lifetime for connections: 1m30s 10.22 ipatm pvc 10.22.1Syntax ipatm pvc ipatm pvc add <i/f> <port> [<vpi>/]<vci> [pcr <pcr>] [remoteip <IP address>] ipatm pvc delete <port> [<vpi>/]<vci> ipatm pvc flush 10.
myswitch> ip ipatm pvc add ipoa b1 61 pcr 50000 myswitch> ip ipatm pvc add ipoa b1 62 remoteip 192.168.4.32 myswitch> ip ipatm pvc ipatm pvc ipoa a3 0/60 pcr 60000 ipatm pvc ipoa b1 0/61 pcr 50000 ipatm pvc ipoa b1 0/62 pcr 60000 remoteip 192.
nat: Interface “ether” now enabled nat: Interface “ether” IP address is 192.168.200.90 bd3000>ip nat delete ether nat: Interface “ether” deleted by IP 10.25 noerrors 10.25.1Syntax noerrors 10.25.2Description Undoes the effect of the errors command; equivalent to untrace error s.
10.27.2Description Sends an ICMP Echo message to the specified IP address. • <ttl> (default 30) is the TTL (time-to-live) to use. A crude traceroute functionality can be obtained by repeating the pin g. command with increasing TTL values, starting with 1.
provided the protocol t y pe (UDP or TCP) is appropriate. They are also displa y ed in place of port numbers, when a suitable mapping exists. The Damson interface (described in the ATMOS TCP/IP Functional Specification, DO-007285-P S) allows other processes to query the mapping.
10.30 relay 10.30.1Syntax relay relay all | <i/f> [<i/f>] [forward] 10.30.2Description Displays or sets what forwarding ATMOS TCP/IP will do between interfaces.
10.31.1Syntax restart 10.31.2Description Reboots the system. This command is deprecated. To reboot the sy stem, use the restart command from the ATMOS console. 10.31.3Example mymachine> ip restart 10.32 rip accept 10.32.1Syntax rip accept [all|<i/f>] [none|<version>*] 10.
mymachine> ip rip allowed rip send ether 2 rip send flane 2 rip accept ether 1 2 rip accept flane 1 2 10.34 rip boot 10.34.1Syntax rip boot 10.34.2Description Broadcasts a request for RIP informati on from other machines.
10.36 rip hostroutes 10.36.1Syntax rip hostroutes [off] 10.36.2Description Sets or clears the hostroutes flag; ATMOS TCP/IP will accept RIP routes to individual hosts onl y if this flag is o n.
mymachine> ip rip poison 10.39 rip relay 10.39.1Syntax rip relay <RIP version> <name> [<i/f> [<timeout>]] 10.39.2Description Configures a RIP relay.
rip send [all|<i/f>] [none|<version>*] 10.42.2Description Controls which version or versions of RIP (RIP version 1, RFC 1058, or RIP version 2, RFC 1723) ATMOS TCP/IP will use to broadcast routing information on each interface. If both versions are specified, rou ting information is broadcast in duplicate, once using each version.
• <name> is an arbitrary name specified to route add that can be used to delete the route using route delet e. • <dest> is the IP address of the network being routed to (only those bits of <dest> corresponding to bits set in <mask> are relevant).
mymachine> ip route add default 0.0.0.0 192 .168.2.3 0: 0:0:0 mymachine> ip route add testnet1 192.168 .101.0 192.168.2.34 mymachine> ip route add testnet2 192.168 .102 .0 192.168.2.34 ff:ff:ff:0 1 60 mymachine> ip route route add testnet2 192.
10.47.1Syntax snmp access [read|write|delete|flush] <parameters> snmp config [save] snmp help [<cmd>|all] snmp trap [add|delete|flush|list] <parameters> snmp version 10.47.2Description Manages the list of SNMP community na mes (also used as passwords by other applications, such as telne t) and the list of SNMP trap destinations.
ip: Transmitted UDP packets: 0 10.49 subnet 10.49.1Syntax subnet subnet add <name> <i/f> <IP address> <mask> subnet delete <name> subnet flush 10.49.2Description Lists defined subnets; defines a subnet; dele tes a subnet definition; or deletes all subnet definitions.
subnet ether.home . 192.168.2.0 ff:ff:ff:00 ether 10.50 trace 10.50.1Syntax trace [<option>] 10.50.2Description Turns on an IP tracing option, or lists the available options. Note that tracing messages are written to background output, so with the standard console one must use the event commands to see them.
untrace [<option>] 10.51.2Description Turns off IP tracing options. The syntax is the same as for trac e; in particular, untrace all turns off all tracing. The trace command is hidde n, not shown by ip hel p. 10.52 uptime 10.52.1Syntax uptime 10.
10.54.2Description The ? command is simply a synonym for the help co mmand, and behaves in the same way..
11.TFTP Console commands 11.1 connect 11.1.1 Syntax connect <node_name> || <ipaddr> 11.1.2 Scope: Client mode only. 11.1.3 Description The connect command is used to specify the remote host name or IP address that will be used in subsequent client mode transfers.
11.2.4 Example get ipaddresses 11.3 help 11.3.1 Syntax help 11.3.2 Description The help command displays the help text which lists the (commonly used) TFTP commands. The init command is not listed in the help text. The trace command has a large number of optiona l parameters and detail on this command may be displayed by typing trace hel p.
11.6.1 Syntax put [local_file] <remote_file> 11.6.2 Scope: Client mode only. 11.6.3 Description The put command requests TFTP to transmit a file to the remote host previously specified using the connect command. By default, the file is named remotely as the local filename but by specifying a second filename, an implicit rename is perform ed.
Index Symbols . (history mechanism 13 <process>, <process> <command> 11 ? (IP) 218 @ commands 14 A abort (IP) 155 Adobe Acrobat 4 arp (IP) 156 arprouting (IP) 158 autoloop (IP) 159 B.
<channel> qos (PPP) 126 <channel> remoteip (PPP) 127 <channel> svc (PPP) 128 <channel> theylogin (PPP) 130 <channel> tunnel <n> <tunnel protocol> <dial dir.
Feedback 4 files (IP) 170 filter (Bridge) 41 filterage (Bridge) 42 flush (Bridge) 43 flush (IP) 171 fragments (Nat) 103 G get (IP) 172 get (TFTP) 221 H hashtable (Nat) 104 help 28 help (Bun) 55 help (.
ipatm help (IP) 178 ipatm lifetime (IP) 179 ipatm pvc (IP) 180 iphostname (IP) 182 L list 17 list (PPTP) 149 list (TFTP) 224 list all open channels (Bun) 68 list channels (Bun) 67 list classes (Bun) 6.
rb 31 relay (IP) 190 reset (DHCPServer) 86 reset port (Bun) 71 restart 8 restart (IP) 192 rh 31 rip accept (IP) 193 rip allowed (IP) 194 rip boot (IP) 195 rip help (IP) 196 rip hostroutes (IP) 197 rip.
status (DHCPServer) 87 steal 32 subnet (IP) 211 Symbols, used in this guide 3 T tell 33 tell <process> 19 trace (DHCPClient) 78 trace (DHCPServer) 88 trace (IP) 213 trace (TFTP) 226 <tunnel&g.
Warning symbol 3 wb 31 wh 31 ww 31.
An important point after buying a device Atlantis Land A02-RA(Atmos)_ME01 (or even before the purchase) is to read its user manual. We should do this for several simple reasons:
If you have not bought Atlantis Land A02-RA(Atmos)_ME01 yet, this is a good time to familiarize yourself with the basic data on the product. First of all view first pages of the manual, you can find above. You should find there the most important technical data Atlantis Land A02-RA(Atmos)_ME01 - thus you can check whether the hardware meets your expectations. When delving into next pages of the user manual, Atlantis Land A02-RA(Atmos)_ME01 you will learn all the available features of the product, as well as information on its operation. The information that you get Atlantis Land A02-RA(Atmos)_ME01 will certainly help you make a decision on the purchase.
If you already are a holder of Atlantis Land A02-RA(Atmos)_ME01, but have not read the manual yet, you should do it for the reasons described above. You will learn then if you properly used the available features, and whether you have not made any mistakes, which can shorten the lifetime Atlantis Land A02-RA(Atmos)_ME01.
However, one of the most important roles played by the user manual is to help in solving problems with Atlantis Land A02-RA(Atmos)_ME01. Almost always you will find there Troubleshooting, which are the most frequently occurring failures and malfunctions of the device Atlantis Land A02-RA(Atmos)_ME01 along with tips on how to solve them. Even if you fail to solve the problem, the manual will show you a further procedure – contact to the customer service center or the nearest service center
