I visited that page several times last night, but it didn't get me any closer to a solution. I have been using the providers table on my ipv4 setup for awhile now, but that doesn't seem to actually keep a connection associated with the ISP it came in on. For example, if a query comes in to my DNS server, the reply has a 50/50 chance of coming back through either ISP. The only way I've been able to control the flow of packets is through a set of DNAT rules and masq entries on the firewall pushing to dedicated secondary IP's on each server, coupled with bind9 views set to respond specifically to queries on those IP addresses.
I have also been trying to set up the providers file under shorewall6, but every time I enable the entries, shorewall6 bombs on restart. Note again that I do use the providers entries under shorewall with no failures... Providers: ISP1 10 10 main sit1 2001:470:8388::1 track eth1,eth2,eth3,eth5 ISP2 20 20 main sit2 2001:470:f032::1 track eth1,eth2,eth3,eth5 When restarting, I get the following error in the log: 09:13:09 Adding Providers... RTNETLINK answers: No route to host ERROR: Command "ip -6 route add default via 2001:470:8388::1 src 2001:470:8388::1 dev sit1 table 10" Failed Note that I tried doing this with the tunnel device (sit1) and the ethernet device (eth0), making the appropriate changes to providers and interfaces. I'm just completely lost here, I don't know what I'm missing. On 10/20/2011 07:12 AM, Tom Eastep wrote: > > http://www.shorewall.net/MultiISP.html. Note that there is no separate > IPv6 documentation and that 'balance' isn't available with IPv6. > > -Tom > ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Ciosco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
