I don't understand what kind of connection you are describing here ... But I think ( to most of us mortals ) is CRAP.Calm down, please.
I am calm ... no need to worry about that ... Though I insist that you are confusing people ....
Bonding is about to utilize multiple ethernet interfaces (network cards) inside the same machine as one single virtual interface (that Linux usually identify with "bond0" or "bond1" o so). With bonding one implement faul tolerance in LAN connection (not WAN!) and, in some cases, even load balancing. Bonding is "ethernet on steroids", but is totally unrelated with WAN connections.There is no such thing such as bonding between a linux system and an ISP provider Unless some kind of exotic connection + hardware is involved that I have no knowledge off.If so please specify and inform us in order to expand our knowledge.Linux bonding can leverage bonding aware switches or servers, but it works perfectly even with dumb switches.You use bonding to aggregate links that is between servers, or between a server and a switch as long as both ends support bonding and the bonding mode desired.
Here again you are confusing people ... Cause It depends on the bonding mode you wish to use ... "........................................................................................ *mode=0 (balance-rr)*Round-robin policy: Transmit packets in sequential order from the first available slave through the last. This mode provides load balancing and fault tolerance.
*mode=1 (active-backup)*Active-backup policy: Only one slave in the bond is active. A different slave becomes active if, and only if, the active slave fails. The bond's MAC address is externally visible on only one port (network adapter) to avoid confusing the switch. This mode provides fault tolerance. The primary option affects the behavior of this mode.
*mode=2 (balance-xor)*XOR policy: Transmit based on [(source MAC address XOR'd with destination MAC address) modulo slave count]. This selects the same slave for each destination MAC address. This mode provides load balancing and fault tolerance.
*mode=3 (broadcast)*Broadcast policy: transmits everything on all slave interfaces. This mode provides fault tolerance.
*mode=4 (802.3ad)*IEEE 802.3ad Dynamic link aggregation. Creates aggregation groups that share the same speed and duplex settings. Utilizes all slaves in the active aggregator according to the 802.3ad specification.
/Pre-requisites:
1. Ethtool support in the base drivers for retrieving
the speed and duplex of each slave.
2. A switch that supports IEEE 802.3ad Dynamic link
aggregation.
Most switches will require some type of configuration
to enable 802.3ad mode./
*mode=5 (balance-tlb)*
Adaptive transmit load balancing: channel bonding that does not require
any special switch support. The outgoing traffic is distributed
according to the current load (computed relative to the speed) on each
slave. Incoming traffic is received by the current slave. If the
receiving slave fails, another slave takes over the MAC address of the
failed receiving slave.
/Prerequisite:
Ethtool support in the base drivers for retrieving the
speed of each slave./
*mode=6 (balance-alb)*
Adaptive load balancing: includes balance-tlb plus receive load
balancing (rlb) for IPV4 traffic, and does not require any special
switch support. The receive load balancing is achieved by ARP
negotiation. The bonding driver intercepts the ARP Replies sent by the
local system on their way out and overwrites the source hardware address
with the unique hardware address of one of the slaves in the bond such
that different peers use different hardware addresses for the server.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------" For instance If you try to have mode 4 *(802.3ad) with a plain switch you'll end up with a mess ... or think you have bonding enabled ...So please please-please-please try not to confuse people and be as accurate as possible, or hold your piece ....
We are here to get a piece of knowledge and not to be confused. Regards Harry *
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
