misc/firestuff
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

More sensible header structure. Cute cow at the bottom

Browse Source
This commit is contained in:
Ian Gulliver
2019-04-25 03:18:54 +00:00
parent a3dfa24549
commit 8663055dd3
34 changed files with 282 additions and 303 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
2006-03-21-redundant-network-interfaces.html
View File

@@ -18,7 +18,7 @@ Yes? <strong>bonding:802.3ad</strong>. No? <strong>bonding:active-backup</strong
Yes? <strong>bonding:balance-alb</strong>. No? <strong>bonding:active-backup</strong>.</li>
</ol>
<h3>STP</h3>
<h2>STP</h2>
<p>This bonding method actually uses Linux’s support for interface bridging. If a bridge is set up between two interfaces connected to the same network and spanning tree protocol is activated, one interface will be put into blocking state and won’t pass traffic. This doesn’t aggregate bandwidth between interfaces when both are up, but it has the interesting effect of allowing the server to bridge traffic between the switches if there are no other available connections. Special configuration at the switches is required to prevent it from being used as a link under normal circumstances.</p>
@@ -66,7 +66,7 @@ brctl showstp br0
<p>One side of one interface should be blocking.</p>
<h3>bonding</h3>
<h2>bonding</h2>
<p>For any of the bonding methods, you’ll need the ifenslave program. In Debian:</p>
@@ -91,7 +91,7 @@ down ifenslave -d bond0 eth0 eth1
<pre><code>ifup bond0
</code></pre>
<h3>bonding:active-backup</h3>
<h2>bonding:active-backup</h2>
<p>This bonding mode keeps one interface completely blocked (including not sending ARP replies out it), using it strictly as a backup.</p>
@@ -102,7 +102,7 @@ down ifenslave -d bond0 eth0 eth1
<p>Follow the general bonding instructions above, and you’re all set!</p>
<h3>bonding:802.3ad</h3>
<h2>bonding:802.3ad</h2>
<p>This bonding mode uses the standardized IEEE 802.3ad bonding method, with a protocol (LACP) for both sides to agree on bonding information. All links must be the same speed and duplex. The balancing method between links is determined by each end; a single connection will only go over one link, and sometimes traffic with a single (ethernet-level) peer will use a single link as well.</p>
@@ -127,7 +127,7 @@ end
<p>Then follow the general bonding instructions.</p>
<h3>bonding:balance-alb</h3>
<h2>bonding:balance-alb</h2>
<p>This bonding mode balances outgoing traffic accoridng to interface speed and usage. It intercepts and rewrites outgoing ARP replies to make them come from different physical interfaces, tricking the network fabric into balancing incoming traffic as well.</p>