Many ISPs need the kinds of quality shaping cake can do
 help / color / mirror / Atom feed
From: dan <dandenson@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: libreqos@lists.bufferbloat.net
Subject: Re: [LibreQoS] how are you doing on ipv4 address supply?
Date: Wed, 26 Oct 2022 09:33:13 -0600	[thread overview]
Message-ID: <CAA_JP8UC7cnor7XY+fQ2W8a77OkbGvkj2LO1LUQoast321CF1w@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5m6HsXFoNPhdxmL-Y+YvoMte2c5XmemixH=BOW8AY=kg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1966 bytes --]

we use RFC6598 addressing and CGNAT on the edge unless someone pays for an
IP.  Very slowly getting IPv6 implementation down.  Poor CRM/Shaper support
for it being a big struggle.  Preseem+UISP for example requires that
whatever is handling IPv6 PD be pollable from preseem so they can grab
MAC:PD prefix and combine them.  VISP has implemented this better recently
but I haven't fully implemented yet, that's a goal for this month.

We don't 'tunnel' ie no MPLS/VPLS, SRV6, EVPN right now.  We technically do
GRE tunneling, terragraph works just like OSPFv3 on IPv6 w/ GRE tunnels.

Part of the reason not to tunnel is that we don't have a single headend, we
have regional POPs and interconnections between so we can reduce outages
caused by the POPs.  Fully routed seems to only non-convoluted way to
handle this.  Not interested in a VRRP moving my tunnel endpoint addresses
between regions, that's a mess.  And so we route.

On Tue, Oct 25, 2022 at 9:30 PM Dave Taht via LibreQoS <
libreqos@lists.bufferbloat.net> wrote:

> in my continued rip-van-winkle, living in the third world (california)
> way, I am curious as to how y'all are managing your
> ipv4 address supply and if you are deploying ipv6 to any extent?
>
> In all this discussion of multi-gbit fiber, my own direct experience
> is that AT&T's fiber rollout had very flaky ipv6, and more and more
> services (like starlink) are appearing behind cgnats, which have their
> own capex and opex costs.
>
> I see a lot of rfc1918 being used as the operational overlay
> elsewhere, tons of tunnels, also.
>
> --
> This song goes out to all the folk that thought Stadia would work:
>
> https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> LibreQoS mailing list
> LibreQoS@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/libreqos
>

[-- Attachment #2: Type: text/html, Size: 2637 bytes --]

  reply	other threads:[~2022-10-26 15:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26  3:30 Dave Taht
2022-10-26 15:33 ` dan [this message]
2022-10-26 16:05 ` Herbert Wolverson
2022-10-26 16:48   ` dan
2022-10-26 19:15     ` Robert Chacón
2022-10-26 19:32       ` Herbert Wolverson
2022-10-26 19:39         ` Robert Chacón
2022-10-26 19:58         ` Dave Taht
2022-10-26 20:18           ` Dave Taht
2022-10-26 20:52       ` Toke Høiland-Jørgensen
2022-10-26 22:38         ` dan

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_JP8UC7cnor7XY+fQ2W8a77OkbGvkj2LO1LUQoast321CF1w@mail.gmail.com \
    --to=dandenson@gmail.com \
    --cc=dave.taht@gmail.com \
    --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