From: Michael K. <mic...@ip...> - 2019-07-23 21:24:41
|
Yes I gathered that was the case. Hmm wonder why it was working for a while. So it doesn't seem too difficult to set up policy based routing from this article which sends traffic out the interface it was received. https://www.linuxjournal.com/article/7291 What do you think? Regards Michael Knill On 24/7/19, 7:12 am, "Lonnie Abelbeck" <li...@lo...> wrote: > My assumption is that the reply will route out the primary interface so it will not work. Exactly. If there is not a return route to your source IP the packet is lost. Or if over WireGuard, a too narrow AllowedIPs to allow the return packet. Using "ip r" at each end should tell the story. Lonnie > On Jul 23, 2019, at 3:58 PM, Michael Knill <mic...@ip...> wrote: > > Hi group > > Forgive my ignorance but should I be able to ping the failover Astlinux interface if the primary is up? I cant for one of my sites but it used to work for some reason. The link seems fine and I can ping the secondary WAN gateway. > My assumption is that the reply will route out the primary interface so it will not work. > > Regards > Michael Knill > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |