Public bug reported:
-- 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.
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: feature-request
--
nm should support easy bonding
https://bugs.launchpad.net/bugs/239999
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
