This technique may help you for inbound services: http://www.don.nz.net/wordpress/poor-mans-anycast/ For outbound, if you can't do a redundant connection with your ISP (or if such an arrangement with one ISP is not acceptable), you'll need some kind of link fail-over on your border gateway, possibly based on a ping of an upstream gateway or known-good host (or hosts). You'll lose active NAT sessions as your external IP changes, but new connections will work. -- don On 06/11/13 11:30, Matthew Poole wrote:
A "small company wanting to play big company" question: My employer is investigating options for network redundancy as having a functional internet connection is critical to our operation. We're not in any position to even try applying for PI IPv4 space from APNIC (only using a /28), and are in no way close to being ready to think about going to pure IPv6. Clients push to us, so we need to have functional DNS as well as link fail-over. We also have multiple public-facing servers offering the same services, so moving to *shudder* NAT or some kind of port proxying isn't an easy option (clients' internal bureaucracies to get firewall ports opened, client configuration, blah blah blah).
So, my question, what are our operational course of action for multi-homing when becoming an AS on the global tubes isn't on the cards?
Cheers