Nerijus Baliunas wrote: > route_rules: > eth1 - ISP1 1000 > eth2 - ISP2 1000 > What are those for? By default, Shorewall uses the corresponding routing table for traffic arriving on a provider interface.
> The problem is that some DNS requests, ssh connections from firewall to > outside > hang/timeout. shorewall dump shows that some requests are issued via ISP2. > DNS requests problem was cured by adding "query-source ISP1_IP;" > to /etc/named.conf. But I don't want to deal with every app. How to make > all connections from firewall go via ISP1? I personally would get rid of 'balance' and make eth2 a fallback provider. Be sure that you have turned off all reverse path filtering (route filtering) is you take that approach. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
