Atlantis Land A02-RA(Atmos)_ME01 manual Ethernet IP-over-ATM PTP Loopback

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.

The class IP-over-ATMincludes both SVC-based and PVC-based IP-over-ATM; the decision whether to use SVCs or PVCs is made at initialization, by testing the interface colors of the file if it supports the Indigo interface, then SVCs are used, and otherwise PVCs.

•<file> specifies the file name that will be opened to access the underlying device. The device can be any of the following:

•Ethernet •IP-over-ATM •PTP

• Loopback

The device must provide the colored interface appropriate for that type of device. For a loopback interface, <file> is not used, and can just be specified as “-” or omitted altogether.

Note that 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>.

•<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, unless the IP-over-ATM MTU value has been changed in the TCP/IP build-time configuration system file. 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 recognized 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 (eg. a class C network); if the correct subnet mask is other than this then it will need to be set with the subnet command (see subnet on page 211).

If there is a DHCP client in the system, the address can be set to DHCP. This