On 8/30/2013 2:02 PM, Tom Eastep wrote: > > What is your setting of USE_DEFAULT_RT? We recommend USE_DEFAULT_RT=Yes, > in which case there will never be a default route in the main table.
Ah, okay. That explains that. Yes I'm using USE_DEFAULT_RT=Yes as recommended. I'm also using TRACK_PROVIDERS=Yes, which implies 'track' on all providers listed in /etc/shorewall/providers. /etc/shorewall/providers cable 1 1 - wancbl detect balance t1 2 2 - want1 207.97.179.65 fallback Questions at this point: http://shorewall.net/MultiISP.html #1 Where do variables like SW_ETH0_GATEWAY and SW_ETH0_ADDRESS get defined? #2 How does shorewall determine the gateway of a DHCP interface? On CentOS 6 with the interface named 'wancbl', the lease information file is /var/lib/dhclient/dhclient-wancbl.leases. #3 Do all providers get a routing table created, named after the provider? If so, and since I have no routing table named 'cable', would that be an issue with my /etc/shorewall/providers file? #4 It's possible that #2 and #3 are intertwined and I'm still seeing the following in /var/log/messages on restart: Adding Providers... WARNING: Interface wancbl is not usable -- Provider cable (1) not Started Provider t1 (2) Started WARNING: No Default route added (all 'balance' providers are down) Null Routing the RFC 1918 subnets ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
