Auto Install for Mandrake Linux | ||
---|---|---|
Prev | Next |
This section is being provided because there were just too many variations for the 'intf' and 'netc' options as a result of their interactions. And providing isolated examples in each section made it difficult to see their relationship to one another.
NOTE: For examples using DHCP, if the DHCP server does not provide all the necessary information, then just add the missing parts (to netc) yourself.
Static IP: Generally, this form is use on LANs and the information is provided by your system administrator :
'intf' => { |
'eth0' => { |
'DEVICE' => 'eth0', |
'BOOTPROTO' => 'static', |
'ONBOOT' => 'yes', |
'IPADDR' => '192.168.5.210', |
'NETMASK' => '255.255.255.0', |
'NETWORK' => '192.168.5.0', |
'BROADCAST' => '192.168.5.255' |
} |
}, |
|
'netc' => { |
'NETWORKING' => 'yes', |
'minus_one' => 0, |
'nb_cards' => 1, |
'FORWARD_IPV4' => 'false', |
'HOSTNAME' => 'linux-dev.eastcott.net', |
'DOMAINNAME' => 'eastcott.net', |
'GATEWAY' => '192.168.5.254', |
'GATEWAYDEV' => 'eth0', |
'dnsServer' => '192.168.5.254' |
}, |
|
DHCP IP: This minimal form is used when the DHCP server provides all the information that you require. Generally, the server dispenses IP information based on your cards ethernet hardware address and name resolution is provided by static DNS server tables:
'intf' => { |
'eth0' => { |
'DEVICE' => 'eth0', |
'BOOTPROTO' => 'dhcp', |
'ONBOOT' => 'yes' |
} |
}, |
|
'netc' => { |
'NETWORKING' => 'yes', |
'minus_one' => 1, |
'nb_cards' => 1, |
'FORWARD_IPV4' => 'false', |
}, |
|
DHCP IP: This is the next level, where the DHCP server needs you to supply a host name, typically so it can dynamically update a DNS server:
'intf' => { |
'eth0' => { |
'DEVICE' => 'eth0', |
'BOOTPROTO' => 'dhcp', |
'ONBOOT' => 'yes' |
} |
}, |
|
'netc' => { |
'NETWORKING' => 'yes', |
'minus_one' => 1, |
'nb_cards' => 1, |
'FORWARD_IPV4' => 'false', |
'DHCP_HOSTNAME' => 'mydog', |
}, |
|
Local LAN and Cable Access to Internet:
'intf' => { |
'eth0' => { |
'DEVICE' => 'eth0', |
'BOOTPROTO' => 'dhcp', |
'ONBOOT' => 'yes' |
}, |
|
'eth1' => { |
'DEVICE' => 'eth1', |
'BOOTPROTO' => 'static', |
'ONBOOT' => 'yes', |
'IPADDR' => '192.168.5.202', |
'NETMASK' => '255.255.255.0', |
'NETWORK' => '192.168.5.0', |
'BROADCAST' => '192.168.5.255' |
} |
}, |
|
'netc' => { |
'NETWORKING' => 'yes', |
'minus_one' => 1, |
'nb_cards' => 2, |
'FORWARD_IPV4' => 'false', |
'HOSTNAME' => 'linux2.eastcott.net', |
'DOMAINNAME' => 'eastcott.net', |
'DHCP_HOSTNAME' => 'CS167266-A', |
'GATEWAYDEV' => 'eth0', |
'dnsServer' => '192.168.5.253', |
}, |
|
NOTE: If you have a DNS server on your LAN, you may want to add PEERDNS=no to the /etc/sysconfig/network file to prevent the /etc/resolv.conf file being replaced when the ISP server responds with its DNS server IPs. By specifying the HOSTNAME and DOMAINNAME parameters, you are also inhibiting the dhcp client from "re-naming" the computer to the hostname and domain name (respectively) that the ISP thinks you are.
Dual Lan: (multiple is just more intf definitions)
'intf' => { |
'eth0' => { |
'DEVICE' => 'eth0', |
'BOOTPROTO' => 'static', |
'ONBOOT' => 'yes' |
'IPADDR' => '192.168.1.2', |
'NETMASK' => '255.255.255.0', |
'NETWORK' => '192.168.1.0', |
'BROADCAST' => '192.168.1.255' |
}, |
|
'eth1' => { |
'DEVICE' => 'eth1', |
'BOOTPROTO' => 'static', |
'ONBOOT' => 'yes', |
'IPADDR' => '192.168.5.202', |
'NETMASK' => '255.255.255.0', |
'NETWORK' => '192.168.5.0', |
'BROADCAST' => '192.168.5.255' |
} |
}, |
|
'netc' => { |
'NETWORKING' => 'yes', |
'minus_one' => 1, |
'nb_cards' => 2, |
'FORWARD_IPV4' => 'false', |
'HOSTNAME' => 'linux3.eastcott.net', |
'DOMAINNAME' => 'eastcott.net', |
'GATEWAY' => '192.168.5.253', |
'GATEWAYDEV' => 'eth1', |
'dnsServer' => '192.168.5.253', |
}, |
|
NOTE: If this computer is acting as a bridge between the two networks, then you need to change FORWARD_IPV4 to true.
Prev | Home | Next |
Setting up a Simple NFS Server | Problems and Issues |