At this point, there is usually no need for adding static routes. If the SCADA or other
control entity is in a different subnet than the ARM600 LAN, define a static route to
that subnet. Do not define static routes over dynamic VPN tunnels.
6.2
Ethernet interface setup parameters
Table 12:
Ethernet interface configuration parameters
Parameter
Description
DEVICE
Network interface device name
BOOTPROTO
“None” is used for static IP addressing; ”DHCP” is
used for dynamic addressing.
IPADDR
IP address allocated for this interface
NETMASK
Netmask in dotted notation, for example,
255.255.255.0
PREFIX
Netmask bits, for example, 24 (either NETMASK
or PREFIX needed)
GATEWAY
IP gateway’s address for this interface
DNS1, DNS2
Domain name servers for this interface
ONBOOT
Interface enabled/disabled in boot up
IPADDR0
First additional IP address associated to this
interface
PREFIX0
Number of netmask bits for the first additional IP
address
IPADDR1
Second additional IP address associated to this
interface
PREFIX1
Number of netmask bits for the second additional
IP address
IPADDR2
Third additional IP address associated to this
interface
PREFIX2
Number of netmask bits for the third additional IP
address
IPV6INIT
Enable/disable IPv6 for this interface
DEFROUTE
Use this interface as IPV4 default route
IPV4_FAILURE_FATAL
Consider interface failed if IPV4 configuration fails
IPV6_AUTOCONF
Control IPv6 autoconfiguration
IPV6_DEFROUTE
Use this interface as IPV6 default route
IPV6_FAILURE_FATAL
Consider interface failed if IPV6 configuration fails
IPV6_PEERDNS
Allow the resolv.conf to be modified according to
DHCP server
IPV6_PEERROUTES
Allow the default gateway to be modified
according to DHCP server
UUID
Universal unique identifier for the interface
TYPE
Interface type
NAME
Name of the interface as displayed in the Network
Connections
1MRS758861 A
Section 6
Network configuration
ARM600
29
User Manual
