I believe that Redhat's network-scripts are above network-manager and NM will not touch any interface that is configured using ifcfg and doesn't have a special line in the file (NM_MANAGED it is, I think). In (Debian and) Ubuntu, the role of network-scripts is taken by /etc/network/interfaces. See ifupdown documentation and documentation to whatever packages provide the advanced networking functionality. The debian packages often contain hooks for ifupdown, so you can configure the advanced network features directly in /etc/network/interfaces.
On Mon, Jun 25, 2012 at 10:02 AM, Christian Mertes <239...@bugs.launchpad.net> wrote: > Zsolt, in terms of documentation there is http://docs.redhat.com/docs > /en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1 > -networkscripts-interfaces.html of course. "NetworkManager is graphical > configuration tool which provides an easy way to make changes to the > various network interface configuration files [...] However, it is also > possible to manually edit the configuration files for a given network > interface." Where "configuration files" means /etc/sysconfig/network- > scripts/ifcfg-* which does not exist on Ubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/239999 Title: nm should support easy bonding Status in NetworkManager: Confirmed Status in “network-manager” package in Ubuntu: Triaged Bug description: -- The feature: Network Manager should assist the user as much as reasonably possible in setting up a bond0 interface. -- Motivating scenario: I'm watching a movie, accessed via sshfs from my desktop box over the wired interface. I get hungry, so I decide to move my laptop to my kitchen and continue watching the movie while cooking. The sshfs connection should seamlessly stay alive, such that I don't have to restart mplayer. -- A sketch of a solution: Look at the IP address and netmask of available interfaces. If two interfaces lie within the same network, ask the user whether to try enabling bonding. If yes, modprobe bonding mode=1, set up bond0, enslave eth0 and eth1 (say) with the fastest being the primary. Let the user say "always bond", "always bond for $ESSID", "never bond", "never bond for $ESSID" after testing whether it works. -- Taking this one step further: Support other values of mode= for the bonds. Don't do this only for wired+wifi, but any number of wired and wifi interfaces. Try to diagnose and repair (or suggest repairs for) any problems that occur while trying to bond. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/239999/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp