On 03/02/16 02:33, Brian J. Murrell wrote:
> I have two providers, one is fast (with a bigger usage cap), one is
> slow (with a smaller usage cap) so I generally default route through
> the fast one as the dedicated primary route with the slow sitting back
> as secondary (i.e. for just when the
On Wed, 2016-02-03 at 16:02 +0800, James Andrewartha wrote:
>
> You could have time-based rules in the mangle file to select the
> default
> provider.
Oh. Now that is an interesting solution. I had not considered that
one. I was focused on raw routing, not policy routing with marks.
I will
You could easily maintain a separate shorewall configuration to apply
during your window, and copy them into the shorewall (using a cron task)
at the appointed hour and restart shorewall, then a second one to
restore your original rules at 7:59AM. I don't know of a better way to
do this.
-
I have two providers, one is fast (with a bigger usage cap), one is
slow (with a smaller usage cap) so I generally default route through
the fast one as the dedicated primary route with the slow sitting back
as secondary (i.e. for just when the first one goes down, not round-
robin).
But the slow
