On 02/27/2018 08:35 AM, Olivier CALVANO wrote: > Hello, I have a problem with my config Quagga / BGP and Shorewall. > Whenever I connect a new site and Quagga receives a new prefix I see it > on my linux server in route -n but this prefix can not talk with him, > Shorewall blocks all flows coming from the prefix. A simple shorewall > reload solves the problem but it is painful. Someone already had the > problem? thank you >
If a simple reload solves the problem, it probably means that you have specified a SOURCE interface somewhere that requires Shorewall to use the main routing table to create the ruleset. What Shorewall version are you running? Does 'shorewall check' produce any warnings? -Tom -- Tom Eastep \ Q: What do you get when you cross a mobster with Shoreline, \ an international standard? Washington, USA \ A: Someone who makes you an offer you can't http://shorewall.org \ understand \_______________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
