http://brainstorm.ubuntu.com/item/18948/
[58 votes] Solution #1: Include bonding in installers network configuration


[103 votes] Solution #2: Create bonding configuration tool


[-9 votes] Solution #3: Include auto-bonding if two or more networks are available


]]> en-us Tue, 31 Mar 2009 11:26:04 +0000 Wed, 29 Apr 2009 05:24:14 +0000 QAPoll module http://brainstorm.ubuntu.com/idea/18948/ the configuration requires either some insight into linux networking

Of course it does. Interface bonding is useful only for administrators of quite large networks / for other special scenarios. If you don't have some insight into linux networking already, then I don't see any reason why you would like to implement it... Also if you're doing it, you really should read about the details - whether you're using a howto, or not.
What is your use case?]]> Tue, 31 Mar 2009 20:13:00 +0000 It's my response to Soren Hansen: What Ubuntu Server Edition could be: http://warma.dk/blog/article/98/

Ubuntu Server has not to be difficult to install and make it reliable. If a small tool could help not-so-advanced users/admins to set up a reliable and fast network connection, it's a small step to bring it closer to be adopted by more users/admins.]]> Tue, 31 Mar 2009 21:24:58 +0000 Actually - who needs bonding && still uses normal installation as a deployment method... That would be a bit strange ;)]]> Wed, 01 Apr 2009 21:07:59 +0000 "Actually - who needs bonding && still uses normal installation as a deployment method..."

Uhhm, me?? Seriously, that would then be a use case for the after-installation-config-tool.]]> Thu, 09 Apr 2009 07:21:37 +0000 More download-speed for average user.

But it should not configure automatically. If you have a UMTS-Connection available, for which you have to pay for use, it shouldn't use that unless no other connection is available.

This isn't just server stuff.]]> Tue, 14 Apr 2009 12:08:22 +0000
Interface bonding is not the same as balancing connections over the interfaces. It means that if you setup bonding, you expect both interfaces to be connected to the same network and routed exactly the same. Bonding should be configured on both ends to really work as expected (otherwise loop protection should kick in and disable one interface).

It's for redundancy, or making your 2 * 100Mbit cards handle 200Mbit traffic. This is not for home use.

Related reading material: http://linux-ip.net/html/ether-bonding.html]]> Tue, 14 Apr 2009 15:23:46 +0000
@phiphi: This is Enterprise and SMB stuff, it does not get you anything, connecting 2x 10GBase-T to connect to your 2MBit-DSL-Router at home ;)]]> Wed, 29 Apr 2009 05:24:14 +0000