Re: [44net] Local Hot-Standby Question

This can not be done with a flat LAN, because there would be a need to change gateways for participating machines, which is not possible. And on the other hand, a router has to be able to distinguish between the 2 half, unless you want to bridge the 2 segments. So the necessary first step would be: Site A: - standby tunnel endpoint on machine 44.60.44.129 - 44.60.44.128/25 with default gw 44.60.44.129 - route to 44.60.44.0/25 via ethernet - ampr-ripd on 44.60.44.129 - quagga on 44.60.44.129 Site B: - tunnel endpoint on machine 44.60.44.1 - 44.60.44.0/25 with default gw 44.60.44.1 - route to 44.60.44.128/25 via ethernet - ampr-ripd on 44.60.44.1 with RIP forward to 44.60.44.129 via ethernet The ethernet link can use any private addresses, or, to keep it hamish, 44.128.0.0/24. There is also a possibility to set ethernet link to 44.60.44.0/24 and use proxy arp. This would allow you not to use specific routes. Marius, YO2LOJ -----Original Message----- From: lleachii--- via 44Net Sent: Saturday, March 26, 2016 16:31 To: 44net(a)hamradio.ucsd.edu Cc: lleachii(a)aol.com Subject: Re: [44net] Local Hot-Standby Question (Please trim inclusions from previous messages) _______________________________________________ Marius, That's excellent! I think your note added an extra step of complexity (using standard RIP) to solve the issue of devices at Site 2 using the outbound while in Hot-Standy Mode (before entering Hot-Active-Failover). ...Let's assume then (since two portal entries are not needed): ***STANDBY tunl0*** <<>> 44.60.44.128/24 ROUTER-X <<ETHERNET>> ROUTER-Y 44.60.44.1/24 <<>> **AMPR tunl0** (kept as a flat /24's and a common LAN) Could the failover take place, thus allowing me to setup (e.g.) a standby http://44.60.44.10 at Site 2? - Lynwood KB3VWG _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net