From: dan <dandenson@gmail.com>
To: David Lang <david@lang.hm>
Cc: Dave Taht <dave.taht@gmail.com>,
libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] [Make-wifi-fast] SCALE 21x conference this week results?
Date: Thu, 14 Mar 2024 11:44:57 -0600 [thread overview]
Message-ID: <CAA_JP8WD15QAGeT71WY5CvaBR8ZMsBQWUfy4BO68pPSNJfV2Rg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.2403141033510.19343@nftneq.ynat.uz>
[-- Attachment #1: Type: text/plain, Size: 4547 bytes --]
If MTU discovery fails it's usually because a device is trying to
seamlessly fragment. Set do not fragment on your device nearest the
customer and that should solve it.
On Thu, Mar 14, 2024 at 11:38 AM David Lang via LibreQoS <
libreqos@lists.bufferbloat.net> wrote:
> we are having some issues with ipv6, since you are a big ipv6 advocate,
> you may
> be able to help
>
> we get IPv6 via a hurricane electric tunnel and apparently PMTU discovery
> is
> misbehving. We've tried reducing the MTU a bit but still having issues.
>
> David Lang
>
> On Thu, 14 Mar 2024, David Lang via Make-wifi-fast wrote:
>
> > Date: Thu, 14 Mar 2024 10:19:21 -0700 (PDT)
> > From: David Lang via Make-wifi-fast <
> make-wifi-fast@lists.bufferbloat.net>
> > Reply-To: David Lang <david@lang.hm>
> > To: Dave Taht <dave.taht@gmail.com>
> > Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
> > Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
> > libreqos <libreqos@lists.bufferbloat.net>
> > Subject: Re: [Make-wifi-fast] SCALE 21x conference this week results?
> >
> > On Thu, 14 Mar 2024, Dave Taht via Make-wifi-fast wrote:
> >
> >> I am curious if anyone here is at scale this week? (it is in pasadena,
> and
> >> one of my favorite conferences -
> https://www.socallinuxexpo.org/scale/21x )
> >> One of our core bufferbloat contributors (david lang) used to fq_codel
> the
> >> wifi there and they built custom boxes to manage the wifi in general
> >> (leveraging openwrt), I am not sure how they are doing it this year.
> >
> > I am here, and we are still running openwrt, mostly on the wndr3800 APs
> > still. stop by the noc in the conf center room 215.
> >
> > David Lang
> >
> >> I always appreciate random users testing with speedtest,
> >> cloudflare,flent,irtt on the conference wifi, and would love results
> from
> >> this one especially. David published an update to this document a few
> years
> >> ago, but I cannot find it. This was the state of play in 2013.
> >>
> >>
> https://www.usenix.org/sites/default/files/conference/protected-files/wireless_paper_slides.pdf
> >>
> >> It was the best wifi on the planet then.
> >>
> >> ---------- Forwarded message ---------
> >> From: Google Calendar <calendar-notification@google.com>
> >> Date: Thu, Mar 14, 2024 at 8:50 AM
> >> Subject: Notification: SCALE 21x @ Thu Mar 14 9am - Sun Mar 17, 2024
> 5:30pm
> >> (GMT-4) (Dave Taht)
> >> To: Dave Taht <dave.taht@gmail.com>
> >>
> >>
> >> SCALE 21x
> >> You have been invited by unknownorganizer@calendar.google.com to
> attend an
> >> event named SCALE 21x on Thursday Mar 14 ⋅ 9am – Sunday Mar 17, 2024 ⋅
> >> 5:30pm (Eastern Time - New York).
> >>
> >> You have an upcoming event
> >>
> >> SCALE 21x
> >> Thursday Mar 14 ⋅ 9am – Sunday Mar 17, 2024 ⋅ 5:30pm (Eastern Time - New
> >> York)
> >> Locationhttps://www.linkedin.com/events/scale21x7123455134910574592
> >> View map
> >> <
> https://www.google.com/url?q=https%3A%2F%2Fwww.linkedin.com%2Fevents%2Fscale21x7123455134910574592&sa=D&source=calendar&usd=2&usg=AOvVaw3X1UEtve0I57MTQPZbLnZG
> >
> >> Organizer
> >> unknownorganizer@calendar.google.com
> >> Guests
> >> Dave Taht <dave.taht@gmail.com> - creator
> >> View all event details
> >> <
> https://calendar.google.com/calendar/event?action=VIEW&eid=XzZ0bG5hcXJsZTVwNmNwYjRkaG1qNHBocGVobW02b3BnNjlwbW1xcmtkZGlqMGQxcDY5b200ZTMzZWNyNjhwcjZkaGhta2NyZ2M1aDZvcHBpZWNxNmtkYjFlNHA2MmNwcDZoajc0cXBqZTFoNmUgZGF2ZS50YWh0QG0&tok=MzYjdW5rbm93bm9yZ2FuaXplckBjYWxlbmRhci5nb29nbGUuY29tNGI5YTMyMDY3NGRiMDIzNTk2Mzk2ZGYyN2ZjY2U1ZWIxN2E4MjEwNA&ctz=America%2FNew_York&hl=en&es=1
> >
> >>
> >> Invitation from Google Calendar <https://calendar.google.com/calendar/>
> >>
> >> You are receiving this email because you are subscribed to calendar
> >> notifications. To stop receiving these emails, go to Calendar settings
> >> <https://calendar.google.com/calendar/r/settings>, select this
> calendar,
> >> and change "Other notifications".
> >>
> >> Forwarding this invitation could allow any recipient to send a response
> to
> >> the organizer, be added to the guest list, invite others regardless of
> >> their own invitation status, or modify your RSVP. Learn more
> >> <https://support.google.com/calendar/answer/37135#forwarding>
> >>
> >>
> >_______________________________________________
> LibreQoS mailing list
> LibreQoS@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/libreqos
>
[-- Attachment #2: Type: text/html, Size: 7659 bytes --]
next prev parent reply other threads:[~2024-03-14 17:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <calendar-854db7ad-2284-416b-8702-cc4dc79ef746@google.com>
2024-03-14 12:58 ` [LibreQoS] " Dave Taht
2024-03-14 17:19 ` [LibreQoS] [Make-wifi-fast] " David Lang
2024-03-14 17:38 ` David Lang
2024-03-14 17:44 ` dan [this message]
2024-03-14 19:10 ` Dave Taht
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/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA_JP8WD15QAGeT71WY5CvaBR8ZMsBQWUfy4BO68pPSNJfV2Rg@mail.gmail.com \
--to=dandenson@gmail.com \
--cc=dave.taht@gmail.com \
--cc=david@lang.hm \
--cc=libreqos@lists.bufferbloat.net \
/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