On 9 Mar 2010, at 16:22, Tom Eastep wrote: > Niall O Broin wrote: > >> But (you knew there had to be a but, didn't you) I have one question >> which isn't covered there, or perhaps it is, in a way I didn't see. >> We pay for traffic on the LL, so I'd like to restrict its use to when >> the DSL is down, and of course for outgoing packets on incoming >> connections which have been set up via the LL. The latter is, I >> think, the rub -it's not simply a failover situation, as in the >> normal case, both interfaces will be up, but for outgoing >> connections, I want to always use the DSL, if it's available. How >> would I go about doing this? Thanks for any suggestions, and I hope >> I've made myself clear enough. > > PLEASE -- do not hijack someone else's thread by replying to it and > supplying your own subject. It is extremely irritating to those of us > who use a threaded mail reader because your thread is now embedded in > the original thread.
Sorry - I don't know why I do that - I use a threaded reader myself and I know how annoying that can be. Can we go with "The devil made me do it" ? > The complete example (http://www.shorewall.net/MultiISP.html#Complete) > does what you want. In that example, the Avvanta provider is only used > from systems that have static IP addresses from that ISP and for > responding to connections from the Internet. Does it though? Surely in that case, those systems will have no internet connection if the Avvanta link goes down? In my case, all the internal systems will have RFC1918 addresses, and they will all use NAT to reach the outside world, preferrably via the DSL (unmetered) but in the event of its failure, seamlessly switching to the LL (metered). I say seamlessly, though I presume that existing connections (e.g. ssh, which we would use a lot) would die in the event of a switchover. Anyway, I guess at this point the thing for me to do is setup a configuration based on http://www.shorewall.net/MultiISP.html#Complete and see where I go from there. Thanks for your prompt help, as always. __ Kindest regards, Niall O Broin ------------------------------------------------------------------------------ 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
