Asus AAM6000EV Specifications download pdf (Page 38)

(Other commands apply only to the devices in effect, rather than to those configured; when adding a device, for example,

one may need to issue the “device add” command, then the “config save” and reboot, then issue any other

configuration commands that depend on the existence of the device, and then “config save” again.)

“<i/f>” 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 “<type>”, though this is perhaps slightly confusing.)

“<type>” specifies the class of interface: Ethernet-like, IP-over-ATM, or loopback. For an Ethernet-like or IP-over-

ATM interface, “<file>” specifies the file name that will be opened to access the underlying device. For a loopback

interface, “<file>” is not used, and can just be specified as “-“ or omitted altogether.

Several different values of “<type>” specify the same class of interface; they differ in that each implies a different

default value for “<file>”. As a result, for the most common interface configurations, “<file>” can be omitted, and

one need only specify the appropriate value of “<type>”. The supported values for “<type>” are

Class <type> Default file

Ethernet

ether //nice

//ethernet

//edd

vlane //lane

flane //lec1

bridge //bridge

IP-over-ATM

atm //q93b

atmpvc //atm

Loopback

loop -

“<mtu>” 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. The value specified will be ignored if it is larger than

the maximum supported by the interface class, which is currently 1500 except for the loopback interface, unless the IP-

over-ATM MTU has been changed; normally there is no point in setting the MTU less than this, so the “<mtu>” option

is of little use.

“<IP address>” is the IP address that this system uses on the interface ; if it is not specified, the interface will be

disabled until an IP address is supplied with the “ip enable” command. For a loopback interface, the address should

be set to 127.0.0.1. (All addresses of the form 127.*.*.* will then be recognised as loopback addresses, as is normal

practice.) For non-loopback interfaces, the subnet mask for the local network will be assumed to be ff:ff:ff:00 (e.g. a

class C network); if the correct subnet mask is other than this then it will need to be set with the “subnet” command.

If there is no initialisation file //isfs/resolve (or //isfs/arptable) at all, then default interfaces are

configured as if by the “device” commands

device add ether ether //edd

device add ether ether //nice

(otherwise)

device add atm atm //q93b

but in each case only if the file concerned ( “//edd”, “//nice”, or “//q93b”) can be opened. Furthermore, if the IP

process is given a command line then each argument will be treated as a possible Ethernet-like file to open, given names

“ether1”, “ether2”, and so on. For example, if the IP process is defined in the system file as “Process ip is

tcp_ip/ip //bridge //lec1 ” (and “//bridge” and “//lec1” can be opened), then the equivalents of the

commands

device add ether1 ether //bridge

device add ether2 ether //lec1

will be processed, in addition to the others above.

Configuration saving saves the interface configuration.

Example:

DSL> ip device

- 38 -

1 ... 37 38 39 ... 69

Comments to this Manuals

No comments

Asus AAM6000EV Specifications Page 38

Comments to this Manuals

Related products and manuals for Networking Asus AAM6000EV