On Wed, 2006-02-01 at 08:40 -0600, Greg Scott wrote: > Your script could have the backup router take on the IP Address of the > primary after it loses its heartbeat. You'll run into a problem with > ARP caches. I saw some code floating around earlier that allowed one > box to listen to the MAC address of another and respond to its ARP > requests. You would need to incorporate something like this in any > solution. Heartbeat (http://www.linux-ha.org/) does a gratuitous ARP (sends an ARP-reply broadcast) when it takes over the ip of the other host so the clients _should_ know the new MAC address belonging to the router. _sh_ > And this all assumes routers A and B are in parallel; all clients and > both routers are on the same LAN. So you have a separate NIC between > routers A and B for heartbeat. Each router has a NIC on the LAN side, > and each has a NIC connecting to the Internet. > > - Greg Scott > > > -----Original Message----- > From: lartc-bounces@xxxxxxxxxxxxxxx > [mailto:lartc-bounces@xxxxxxxxxxxxxxx] On Behalf Of Jandre Olivier > Sent: Wednesday, February 01, 2006 5:52 AM > To: lartc@xxxxxxxxxxxxxxx > Subject: failover routing > > Hi Guys, > > I would just like to have advice and pointers of the best way would be, > Someting like BGP or OSPF? > > I have 2 internet connections at diffrent locations. let say connection > A and B > > 1.) router A has a fast internet connection and a seperate interface for > clients using /lan/pppoe/ipsec etc and another ethernet interface going > to router B > > 2.) router B has similiar setup as router A and also a seperate ether > interface for clients and one going to router A > > 3.) all clients gets masqueraded as there is limited amount of internet > routable ips > > Now my first thought was to write some perl/bash scripts to just ping > your internet gateway address of Router A and if its down, just change > your default route to router B and everyone and vice versa and u can > still get access. > This way for me is not very clean though as Im the one writing the > scripts as something like zebra might do this perfectly? > just a basic idea of what my setup is. What would be my best way of > doing this.? > > -- > /*---------------------------------------------------------------------* > / > __ _ > ---------- / / (_)__ __ ____ __ --------- > ------- / /__/ / _ \/ // /\ \/ / -------- > ---- /____/_/_//_/\_,_/ /_/\_\ ------ > localhost@xxxxxxxxxxxxxxxxxx > _______________________________________________ > LARTC mailing list > LARTC@xxxxxxxxxxxxxxx > http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc > _______________________________________________ > LARTC mailing list > LARTC@xxxxxxxxxxxxxxx > http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc _______________________________________________ LARTC mailing list LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
