Multiple Network Interfaces Howto: Difference between revisions

From FAIWiki
Jump to navigation Jump to search
(→‎Solution: + 2nd draft (suggested by olivalukas@gmail.com))
Line 9: Line 9:
== Solution ==
== Solution ==


''Draft recommendation:''
''Draft recommendation I:''


* Set up DHCP for each network (card), otherwise the installation boot process will hang when <tt>ipconfig</tt> tries to set up all interfaces.
* Set up DHCP for each network (card), otherwise the installation boot process will hang when <tt>ipconfig</tt> tries to set up all interfaces.
* You should have one template <tt>/etc/network/interfaces</tt> for each class of machine, and then plug in the IP addresses for each machine via search and replace. Use cfagent for this.
* You should have one template <tt>/etc/network/interfaces</tt> for each class of machine, and then plug in the IP addresses for each machine via search and replace. Use cfagent for this.
''Draft recommendation II:''
* Set up BIOS to boot preferably from network card on internal network where you have the FAI server.
* Specify a <tt>ip=eth0:dhcp</tt> line in the tftp config file for all clients. If that doesn't work specify it statically (see <tt>/usr/src/linux/Documentation/filesystems/nfsroot.txt</tt> for the syntax).
* Set up the dhcp server to assign IP address to the MAC address of the client network interface you boot from.
* Write a simple shell script to generate an appropriate <tt>/etc/network/interfaces</tt> file from the <tt>$HOSTNAME</tt> corresponding to the IP address obtained from DHCP (also check <tt>/etc/hosts file</tt>).


== Analysis, Troubleshooting ==
== Analysis, Troubleshooting ==

Revision as of 09:46, 19 November 2009

Motivation

You want to use FAI to install systems with two or more network interface cards (NIC).

Installing a client with two active interfaces usually causes trouble as the boot process hangs when ipconfig tries to set up the 'wrong' interface using DHCP when no DHCP server is present for the respective interface. Also, by default FAI sets up only one (i.e. the first) network interface dynamically with the following script of the FAIBASE class:

/var/lib/fai/config/scripts/FAIBASE/30-interface

Solution

Draft recommendation I:

  • Set up DHCP for each network (card), otherwise the installation boot process will hang when ipconfig tries to set up all interfaces.
  • You should have one template /etc/network/interfaces for each class of machine, and then plug in the IP addresses for each machine via search and replace. Use cfagent for this.

Draft recommendation II:

  • Set up BIOS to boot preferably from network card on internal network where you have the FAI server.
  • Specify a ip=eth0:dhcp line in the tftp config file for all clients. If that doesn't work specify it statically (see /usr/src/linux/Documentation/filesystems/nfsroot.txt for the syntax).
  • Set up the dhcp server to assign IP address to the MAC address of the client network interface you boot from.
  • Write a simple shell script to generate an appropriate /etc/network/interfaces file from the $HOSTNAME corresponding to the IP address obtained from DHCP (also check /etc/hosts file).

Analysis, Troubleshooting

Boot process stops at ipconfig (client installation over network)
Check which MAC address ipconfig is trying to set up. Typically, the related interface is not connected to a network that provides a DHCP address for that network card.

See also

Related Discussions