Bonding NICs in F17

[daytooner]

OK, so I'm upgrading from F14 to F17.

In my current system, I have three NICs: eth0 and eth1 are bonded together into bond0; eth2 I have on a separate subnet (ie, bond0 on 192.168.1.0, eth2 on 192.168.2.0).

In F14, I did this by changing the ifcfg-ethX script files in /etc/sysconfig/network-scripts, added the bonding module to /etc/modprobe.d, then disabling NetworkManager - because it didn't work right with these scripts, and enabling the network service.

This all worked fine in F14 (and previous versions). But now it seems that I need to use NetworkManager rather than network service, or else some applications won't have network access.

Can someone tell me what has changed so that I can do the bonding?

TIA

ken

[mjtbrady]

Similarly, I am about to get ride of NetworkManager and do networking via the ifcfg scripts due to the lack of bridging support, even though bonding and bridging support is supposed to be there (see http://fedoraproject.org/wiki/Featur...riseNetworking).

Can you elaborate on what applications don't work if NetworkManager isn't running?

[jvillain]

You don't have to use NetworkManager you have the choice to just use network. Personally I use network on servers and NetworkManager on my desktop/laptops. Just do the following.

First open your interface file eg. ifcfg-eth0. Then make sure you have a line like

NM_CONTROLLED=no

NM is NetworkManager. You can actually have some nics controlled by NetworkManager and some controlled by network. But it is easier to only manage one.


chkconfig network on
chkconfig NetworkManager off
service network start
service NetworkManager stop


Yes you should really be using systemctl rather than service and chkconfig but the sysntax sucks rhinos. This will work. Just make sure you can access the machine in some way other than via the nic while you are making the changes.

[daytooner]

You don't have to use NetworkManager you have the choice to just use network. Personally I use network on servers and NetworkManager on my desktop/laptops. Just do the following.

First open your interface file eg. ifcfg-eth0. Then make sure you have a line like

NM_CONTROLLED=no

NM is NetworkManager. You can actually have some nics controlled by NetworkManager and some controlled by network. But it is easier to only manage one.


chkconfig network on
chkconfig NetworkManager off
service network start
service NetworkManager stop

This is what I did in F14 (and before). But when I tried that with F15, FireFox, and maybe other apps, wouldn't connect to the network. Perhaps someone fixed that issue since then - I haven't tried it again.

Yes you should really be using systemctl rather than service and chkconfig but the sysntax sucks rhinos.

My sentiments exactly.

This will work. Just make sure you can access the machine in some way other than via the nic while you are making the changes.

Never a good idea to make changes to the network via a network connection :-(.

[daytooner]

Okay, finally got this working.

In short, everything is basically identical to previous versiosn of Fedora:

- disable NetworkManager service (do this FIRST!!!)

- in /etc/sysconfig/network-scripts, create ifcfg-XXX files for each interface you want to bond. Make sure each has the correct HWADDR value, SLAVE=yes, and MASTER=<bond interface name>. Also, DON'T include any IP address info. Use the interface name that udev creates for each slave interface (look at dmesg output).

- in the same directory, create a file "ifcfg-<bond interface name>". This should have all of the entries that a normal ifcfg-ethX file has (TYPE, IPADDR, NETMASK,GATEWAY,DNS1,etc.), without a HWADDR.

-in /etc/modprobe.d, create the file bonding.conf as done with previous Fedora versions

- enable the network service

and Voila.

The key problems were 1) getting NetworkManager out of the way BEFORE doing anything; 2) getting the right interface names. udev now renames everything to "emX" for embedded NICs, and pXpY for NIC cards (X for the slot number, Y for the device number in that slot - usually just 1).

Of course - as pointed out previously - doing things this way you will not have any network access :-).

Hope this helps someone...

ken

[meheezen]

thanks OP, saved my day