Originally Posted by james.reid
I've set up bonding with Fedora 8 several times, but am having probs trying to do it with Fedora 9.
Things that I've noticed so far:
- There is no /etc/modprobe.conf but there is a /etc/modprobe.d - how does this work?
Same as it always did. modprobe.conf is ALWAYS optional, and F7 & F 8always had a /etc/modprobe.d . Make a new modprobe.conf if you wish or add entries under /etc/modprobe.d .
The only difference in F9 is that they've tried to minimize the need for the modprobe.conf.
- I've reconfigured my /etc/sysconfig/network-scripts/ifcfg-eth0 and eth1 files for bonding and created a ifcfg-bond0 file, but it does not seem to be getting noticed - eth0 and eth1 seem to be picking up dhcp addresses like they would if there was no changes.
- My suspicion is that NetworkManager is running everything and ignoring what I normally set up. Is there a command line version of NetworkManager? How can I turn NetworkManager off (if this is the problem)
To bypass networkmanager, use system-config-network (or the curses version system-config-network-tui) and disable the item that says the each interface is controlled by NetworkManager. Then disable the networmmanager service like this
chkconfig NetworkManager off
service NetworkManager stop
Then restart the network services - reboot or
service network restart
The box is being used as a server and will not be running a gui like kde - seems a little crazy that (I think) NetworkManager appears to be installed when there is no way to control it???
Thanks for any pointers!
Yes - I think many of the choices being made wrt Gnome (NetworkManager(NM) is/was a gnome project) are a **LOT** crazy. These wingnuts are trying to turn Linux into a single-user desktop system.
Originally NM was meant to handle all the complexity of the various wifi authentication & encryption schemes - and it often does than nicely. However AFAIK you cannot use NM to connect to a wifi until you have a controlling gui session. Someone has to login to a gui before NM will authenticate since they have per-user keyring for authentication. If you have two gui logins ((via the virtual consoles or separate heads)) then the NM gui gets confused.
Once the connection is up of course all users can use it - so it defeats any per-user-ness protection. It''s REALLY stupid.
I haven't tried NM on a wired F9 connection, but under F8 you could not make a wired network connection under NM until someone logged it !! So NM was completely useless for stand-alone servers. NM on F9 supports static wired configuration (w/o dhcp) so *maybe* it's smart enough to connect w/o a gui login.
The only command line tools for NM is "nm-tool" which just dumps a little connection info.
Yes for a wired server, headless or not, I think disabling NM and using the old-style RH network config is the thing to do.