From: Sebastian Moeller <moeller0@gmx.de>
To: David Lang <david@lang.hm>
Cc: Rich Brown <richb.hanover@gmail.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] I wrote a blog entry about devices I know of out there...
Date: Fri, 3 Feb 2017 22:15:21 +0100 [thread overview]
Message-ID: <D5EB3A07-1E9B-41F2-B843-5EDC78114252@gmx.de> (raw)
In-Reply-To: <nycvar.QRO.7.75.62.1702031208090.6590@qynat-yncgbc>
> On Feb 3, 2017, at 21:11, David Lang <david@lang.hm> wrote:
>
> On Fri, 3 Feb 2017, Rich Brown wrote:
>
>>> On Feb 3, 2017, at 2:50 PM, David Lang <david@lang.hm> wrote:
>>>
>>> On Fri, 3 Feb 2017, Rich Brown wrote:
>>>
>>>> Friends in town say that Fairpoint recommends a Zyxel VMG4380-B10A modem for bonded pairs. They seem to have fairly good luck with it.
>>>
>>> I've got a VMG4325-B10A and it's horrific, still running a 2.6 kernel. I routinely have several seconds of buffering on my upload. according to the Zyxel site, the 4380 has a coax connection.
>>
>> Yes, that's why it makes sense to stick LEDE in series with the Zyxel, to let LEDE handle the queueing.
>
> the trouble is that to do this, you have to set the outbound speed well below the actual speed, and when you only have 2Mb to start with…
Why? I have been using XDSL lines with great succes with SQM set to 100% of the actual sync bandwidth and accounting for all known overhead. This worked so well without induced bufferbloat that I even caught my ISP temporarily adding a VLAN tag to my line; the added 4 bytes made buffer bloat re-appear (I confirmed with re-measuring the overhead, increasng the sqm overhead by 4 also got rid of the bufferbloat). With ingess, sure one needs to stay well below the line speed, but egress on ADSL is pretty much solved. Unless the DSLAM’s uplink is congested, then all bets are off…
Best Reagards
Sebastian
>
>> I've actually never seen a Zyxel, so can't speak to the connectors. Hmmm... The Zyxel specs at https://www.zyxel.com/me/en/promotions/promotion_20130416_076615_me_en.shtml show the 4380 as having both a GbE connector (as if... :-) and a coax HPNA connector.
>
> Yes, this series has a Gig-E as well as the DSL/Coax WAN connector(s)
>
> It's really a horrible, overbuffered, limited firmware from the factory (the "firewall" has three settings for example)
>
> I'm looking for a replacement for it, and when you spoke of people recommending it, I have to disagree with them.
>
> David Lang
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2017-02-03 21:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 18:55 Rich Brown
2017-02-03 19:00 ` Jim Gettys
2017-02-03 19:33 ` Rich Brown
2017-02-03 19:50 ` David Lang
2017-02-03 20:01 ` Rich Brown
2017-02-03 20:11 ` David Lang
2017-02-03 20:33 ` Jim Gettys
2017-02-03 21:15 ` Sebastian Moeller [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-02 21:53 Jim Gettys
2017-02-02 22:34 ` 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=D5EB3A07-1E9B-41F2-B843-5EDC78114252@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
--cc=david@lang.hm \
--cc=richb.hanover@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