[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

QUIC traffic throttled on AT&T residential

Subject: QUIC traffic throttled on AT&T residential
From: mpetach at netflight.com (Matthew Petach)
Date: Fri, 21 Feb 2020 15:20:52 -0800
In-reply-to: <[email protected]>
References: <CAJZMiuej5Tt=OjoY4b-f3iAmz5448BgTyPidJeBxLH++fzFKrw@mail.gmail.com> <CAD6AjGTGC548zbcMsq7xzZG61-YSThXROcySwoqOPVs_jPHmSQ@mail.gmail.com> <CA+FDdDSuCMig67N6qu2C8tg4Gyk+UGPSUk+PjReg5P+5bGXanQ@mail.gmail.com> <[email protected]> <CAJZMiudUY9JrYq_vLOMnnnJVQpioZFHcfhBn2UnuYMR2YfN9YA@mail.gmail.com> <CAJZMiucJhexCgtTyngjEXHqokek8FMx2REWpGe6u+B3T67QQBA@mail.gmail.com> <[email protected]> <CAJZMiuddSwU2pZi2aoAb=FSEkVonqL1=De3_+n0tvnbS4b_bAQ@mail.gmail.com> <CAL9Qcx4TPO7CAmO21-ovUuSHDRog1wF9OENs-FTx_GEATV7+0w@mail.gmail.com> <CAD6AjGQSz=BhL+=ikx3GVWLTDePTRZCS5Y=xOMN8AEYpYgZ+cg@mail.gmail.com> <CACXVQYDvaWYJG9TaiZE_F582LSQd73Ra2xvb=SELFAmmFZOzqQ@mail.gmail.com> <CAD6AjGS-2H=LFVBcnfDSZME1-GkQt+AHkWykDFsto6D+=hcROw@mail.gmail.com> <CAPcE_LdDydSkOaXnsWMG-05Zi__kObPqz7qkTrCs-ZnC-dqppA@mail.gmail.com> <[email protected]> <[email protected]>

On Fri, Feb 21, 2020, 13:31 Å?ukasz Bromirski <lukasz at bromirski.net> wrote:

>
> [...]
>
> Nowâ?¦ once we are aware, the only question is â?? where we go from here?
>
> â??
> ./
>

Well, it's clear the UDP 443 experiment wasn't entirely successful.

So clearly, it's time to use the one UDP port that is allowed through at
the top of everyone's ACL rules, and update QUIC in the next iteration to
use UDP/53.

*THAT* should solve the whole problem, once and for all.

;)

Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20200221/ee25f9e2/attachment.html>

Follow-Ups:
- QUIC traffic throttled on AT&T residential
  - From: owen at delong.com (Owen DeLong)
- QUIC traffic throttled on AT&T residential
  - From: lukasz at bromirski.net (Łukasz Bromirski)

References:
- QUIC traffic throttled on AT&T residential
  - From: sterling.daniel at gmail.com (Daniel Sterling)
- QUIC traffic throttled on AT&T residential
  - From: cb.list6 at gmail.com (Ca By)
- QUIC traffic throttled on AT&T residential
  - From: ross at tajvar.io (Ross Tajvar)
- QUIC traffic throttled on AT&T residential
  - From: michael at supermathie.net (Michael Brown)
- QUIC traffic throttled on AT&T residential
  - From: sterling.daniel at gmail.com (Daniel Sterling)
- QUIC traffic throttled on AT&T residential
  - From: sterling.daniel at gmail.com (Daniel Sterling)
- QUIC traffic throttled on AT&T residential
  - From: mohta at necom830.hpcl.titech.ac.jp (Masataka Ohta)
- QUIC traffic throttled on AT&T residential
  - From: sterling.daniel at gmail.com (Daniel Sterling)
- QUIC traffic throttled on AT&T residential
  - From: beecher at beecher.cc (Tom Beecher)
- QUIC traffic throttled on AT&T residential
  - From: cb.list6 at gmail.com (Ca By)
- QUIC traffic throttled on AT&T residential
  - From: me at geordish.org (Dave Bell)
- QUIC traffic throttled on AT&T residential
  - From: cb.list6 at gmail.com (Ca By)
- QUIC traffic throttled on AT&T residential
  - From: matthew at matthew.at (Matthew Kaufman)
- QUIC traffic throttled on AT&T residential
  - From: danwing at gmail.com (Dan Wing)
- QUIC traffic throttled on AT&T residential
  - From: lukasz at bromirski.net (Łukasz Bromirski)

Prev by Date: TCP-AMP DDoS Attack - Fake abuse reports problem
Next by Date: QUIC traffic throttled on AT&T residential
Previous by thread: QUIC traffic throttled on AT&T residential
Next by thread: QUIC traffic throttled on AT&T residential
Index(es):
- Date
- Thread