From: David Lang <david@lang.hm>
To: "Luis A. Cornejo" <luis.a.cornejo@gmail.com>
Cc: David Lang <david@lang.hm>, John D <j.w.r.dexter@gmail.com>,
bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Dual WAN home router with decent SQM?
Date: Mon, 5 Jun 2023 09:20:28 -0700 (PDT) [thread overview]
Message-ID: <o0n09012-ooop-0p92-64q2-7913927r39q7@ynat.uz> (raw)
In-Reply-To: <CAKJdXWA7e2=hKsTfCDGhzR43gkcP51TqMPgbvE=PhMkXn+YNEg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2189 bytes --]
you aren't going to bond two differnt ISPs for faster upload.
you may setup tunnels over each of the ISPs and bond them together.
Even with a full BGP link, any given connection is very unlikely to use both
ISPs.
David Lang
On Mon, 5 Jun 2023, Luis A. Cornejo wrote:
> I’ve done the multi wan with mwan3 and it works fine for load balance or
> failover.
>
> But if you are trying to improve your upload then the best you can get is
> one upload vs the other. You won’t get both uploads to the same stream,
> that is bonding, which is a little harder to do.
>
> -Luis
>
> On Sun, Jun 4, 2023 at 9:35 AM David Lang via Bloat <
> bloat@lists.bufferbloat.net> wrote:
>
>> any router that you can run OpenWRT on will do the job
>> look at the mwan3 package to mange the multiple ISPs
>>
>> at 100Mb, you don't need an especially beefy router.
>>
>> David Lang
>>
>> On Sun, 4 Jun 2023, John D
>> via Bloat wrote:
>>
>>> Date: Sun, 4 Jun 2023 09:48:21 +0100
>>> From: John D via Bloat <bloat@lists.bufferbloat.net>
>>> Reply-To: John D <j.w.r.dexter@gmail.com>
>>> To: bloat@lists.bufferbloat.net
>>> Subject: [Bloat] Dual WAN home router with decent SQM?
>>>
>>> I want to set up a new home router with SQM support to alleviate (mostly
>>> upload) bloat.
>>> However I would also like dual ISP support, more for backup/failover than
>>> load sharing.
>>> I can see affordable multi wan "load balancer" routers eg TP-link, and
>>> affordable SQM routers such as ubiquity Edgerouter, but I'm struggling to
>>> find a single device providing both.
>>> Just after any advice on a) am I better having two separate components b)
>>> if so any suggestions which product/brand?
>>> Two devices means more configuration but possibly more flexible and
>> cheaper.
>>>
>>> My internet speed is looking to max out around 100/20mbps so I don't need
>>> Gbit performance. Thanks for any help.
>>> _______________________________________________
>> 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
>>
>
next prev parent reply other threads:[~2023-06-05 16:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 8:48 John D
2023-06-04 13:07 ` Nils Andreas Svee
2023-06-04 13:57 ` John D
2023-06-04 14:22 ` Nils Andreas Svee
2023-06-04 14:35 ` David Lang
2023-06-05 16:06 ` Luis A. Cornejo
2023-06-05 16:20 ` David Lang [this message]
2023-06-05 16:24 ` Dave Taht
2023-06-05 18:25 ` John D
2023-06-05 18:53 ` David Lang
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=o0n09012-ooop-0p92-64q2-7913927r39q7@ynat.uz \
--to=david@lang.hm \
--cc=bloat@lists.bufferbloat.net \
--cc=j.w.r.dexter@gmail.com \
--cc=luis.a.cornejo@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