|
Actually, there is a way to do this (at least for
outbound access and mail) without BGP, but it requires two firewalls in a
RainWall cluster. You connect one firewall to ISP A and the other firewall
to ISP B, and both to the same internal subnet. The firewall A does NAT
using range from ISP A, and firewall B does NAT using range from ISP B.
Then you set up the RainWall Ping Monitor to watch the ISP links. If link
to ISP A goes down, RainWall can automatically disable firewall A, and move
its internal IP address to firewall B, thereby redirecting users out to ISP
B. This also allows load sharing of outbound traffic between the two
links. It does not help in the case of inbound access to an internally
hosted webserver, but mail will still work if you use multiple MX
records. Failover is automatic, but not transparent (because src/dest pair
changes). Not a perfect solution, but then neither is
BGP.
Mark L. Decker
Rainfinity
(408) 382-4870
|
- [FW1] Multiple WAN Links. Gunjan Mathur at 9netave
- Re: [FW1] Multiple WAN Links. CryptoTech
- Re: [FW1] Multiple WAN Links. Mark L. Decker
- Re: [FW1] Multiple WAN Links. CryptoTech
- RE: [FW1] Multiple WAN Links. Mark L. Decker
- RE: [FW1] Multiple WAN Links. Scopelliti, Pasquale F
- RE: [FW1] Multiple WAN Links. Mark L. Decker
- RE: [FW1] Multiple WAN Links. iden fw
- RE: [FW1] Multiple WAN Links. Mark L. Decker
- RE: [FW1] Multiple WAN Links. iden fw
- RE: [FW1] Multiple WAN Links. Mark L. Decker
- RE: [FW1] Multiple WAN Links. Ed Davidson
- RE: [FW1] Multiple WAN Links. Lee Hughes
