From: David Lang <david@lang.hm>
To: Dave Taht <dave.taht@gmail.com>
Cc: Daniel Sterling <sterling.daniel@gmail.com>,
Rich Brown <richb.hanover@gmail.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Multiple WAN ports & SQM?
Date: Sun, 3 May 2020 17:26:14 -0700 (PDT) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.2005031724480.16262@qynat-yncgbc> (raw)
In-Reply-To: <CAA93jw6W69B7Fq-LN3qm9um7kmbCkV5iddQQuTVT4BH3L7dxfw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2327 bytes --]
I've been wanting to set this sort of thing up (the best DSL I can get is 8/1,
and that's with a bondd DSL setup) but have not been able to find a good
tutorial in setting things up.
anyone have any pointers?
David Lang
On Sun, 3 May 2020, Dave Taht wrote:
> Date: Sun, 3 May 2020 07:33:56 -0700
> From: Dave Taht <dave.taht@gmail.com>
> To: Daniel Sterling <sterling.daniel@gmail.com>
> Cc: Rich Brown <richb.hanover@gmail.com>, bloat <bloat@lists.bufferbloat.net>
> Subject: Re: [Bloat] Multiple WAN ports & SQM?
>
> not huge on bonding, simpler to just get the two uplinks and split
> flows across them with an sqm instance for each and a tc hash
> directing flows at one or another.
>
> On Sun, May 3, 2020 at 7:30 AM Daniel Sterling
> <sterling.daniel@gmail.com> wrote:
>>
>> When I had both DSL and cable modem, I compiled Linux with this patch set to make multi gateway NAT work and it worked great
>>
>> http://ja.ssi.bg/#routes
>>
>> Should be able to use that plus ifb+cake on each NIC to do the right thing, aye?
>>
>> As an aside, I'm kind of furious that NAT fix never got merged upstream :( it's so useful for multiple uplinks
>>
>> -- Dan
>>
>> On May 3, 2020, at 10:23 AM, Rich Brown <richb.hanover@gmail.com> wrote:
>>
>> Given the crummy internet service in my area (DSL, max of 15mbps/1mbps), I wonder if we could improve things by getting a second connection from our ISP and "bonding" the two links together in my OpenWrt router.
>>
>> I see both Multiwan (which is self-described as old) and mwan3.
>>
>> But neither would seem to offer the kinds of latency control (SQM/fq_codel/cake) that the cool kids in networking have come to expect.
>>
>> Any recommendations from this group for such an effort? Thanks.
>>
>> Rich
>> _______________________________________________
>> Bloat mailing list
>> Bloat@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat
>>
>> _______________________________________________
>> Bloat mailing list
>> Bloat@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat
>
>
>
> --
> Make Music, Not War
>
> Dave Täht
> CTO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-831-435-0729
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2020-05-04 0:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 14:23 Rich Brown
2020-05-03 14:30 ` Daniel Sterling
2020-05-03 14:33 ` Dave Taht
2020-05-03 14:42 ` Sebastian Moeller
2020-05-04 0:26 ` David Lang [this message]
2020-05-04 11:28 ` Daniel Sterling
2020-05-04 11:40 ` Daniel Sterling
2020-05-03 14:46 ` Arie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.2005031724480.16262@qynat-yncgbc \
--to=david@lang.hm \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=richb.hanover@gmail.com \
--cc=sterling.daniel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox