Perfect -- The start order seems to be important for the system. What I did to resolve this was setup each peering gateway when configuring with nmtui. I then removed all shorewall routing, including multi-isp.
I am now successfully able to hit each ISP interface externally, and see the proper routing tables. Thank you all for your assist. On Thu, Apr 27, 2023 at 7:31 AM Tuomo Soini <t...@foobar.fi> wrote: > On Wed, 26 Apr 2023 18:25:16 -0500 > Red Baron <redbaro...@gmail.com> wrote: > > > I did attempt to install multi-isp, using mark columns & track > > options as such: > > > > ISP1 1 1 - eno1 $GW1 track > > ISP2 2 2 - eno2 $GW2 track > > > > > > I Also have "USE_DEFUALT_RT=Yes" > > > > this failed to work. I then replaced the mark columns in the > > providers file with "-", and reset, but that too failed. > > > > I think I want to disable all shorewall routing management. If I do a > > shorewall clear, then restart FRR, the interfaces work as expected. > > Any suggestions on how to best prevent shorewall from altering > > routing tables? I assumed that removing the providers was enough, but > > I must be missing something else. > > With bgp4 you absolutely don't want shoreall to do any routing related > stuff and especially NOT multi-isp. > > BGP4 routing is by definition asymmetric and managed by routing daemon. > You also do not want to have default route on your system at all. > > -- > Tuomo Soini <t...@foobar.fi> > Foobar Linux services > +358 40 5240030 > Foobar Oy <https://foobar.fi/> > > > _______________________________________________ > Shorewall-users mailing list > Shorewall-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/shorewall-users >
_______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
