What is the difference between Shorewall multiple internet connection and
Linux NIC bonding.
--
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to
Surely the clue is in the name...
Multiple internet connection is thus:
/ISP1
FW -ISP2
\ISP3
Bonding is thus:
/eth0\
FW -eth1-ISP
\eth2/
One provides redundancy in case you lose a connection to an isp, the other
provides redundancy in case of NIC failure. Obviously you co
Hello,
In which context and to what purpose can the braodcast parameter in
interfaces be used ? I have read the man page and have tried leqaving
it blank, setting an IP, and using 'detect', but each time an #iptables
-L' would should the same.
Thanks.
-
Il 15/12/2010 10:35, Phil Foxton ha scritto:
Obviously you could combine the
two (given enough NICs and enough ISP connections)
With "combine" did you mean "use both", I guess? Actually the two
features are unrelated each other, if I'm not going wrong.
Bye
___
Paolo Basenghi -- Sistemi In
Hi Boby,
Shorewall multiple internet connection is for different internet links and
using them in load balancing, where as NIC bonding is Link aggregation which
describes using multiple network ports in parallel to increase the link speed,
and to increase the redundancy for higher availability.
Yes, I do mean use both, so at the firewall end you could have multiple bonds
(which requires N interfaces, where N=x*y, x being number of interfaces per
bond, and y being number of bonds), so to do another piece of ASCII art, you
can have this:
BOND0
/eth0\ISP1
/ eth1/
FW
On 12/15/10 2:44 AM, lanas wrote:
> Hello,
>
> In which context and to what purpose can the braodcast parameter in
> interfaces be used ? I have read the man page and have tried leqaving
> it blank, setting an IP, and using 'detect', but each time an #iptables
> -L' would should the same.
That
On 12/15/2010 1:35 AM, Phil Foxton wrote:
> /eth0\
> FW -eth1-ISP
> \eth2/
>
> the other
> provides redundancy in case of NIC failure.
it also covers path failure, switch failure, etc. basically, *!isp
failure where
