Many ISPs need the kinds of quality shaping cake can do
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: "Robert Chacón" <robert.chacon@jackrabbitwireless.com>,
	dan <dandenson@gmail.com>
Cc: libreqos@lists.bufferbloat.net
Subject: Re: [LibreQoS] how are you doing on ipv4 address supply?
Date: Wed, 26 Oct 2022 22:52:31 +0200	[thread overview]
Message-ID: <87wn8m1f5c.fsf@toke.dk> (raw)
In-Reply-To: <CAOZyJovoUHVrFv+rnU4MNd6Wjfsu4Unz87_3Cf_Zog5k4dLubA@mail.gmail.com>

Robert Chacón via LibreQoS <libreqos@lists.bufferbloat.net> writes:

> I'd prefer simple routing, but with IPv4 exhaustion - that would lead to a
> lot of unused RFC6598 addresses (and hence high CG-NAT ratios).

Note that it's possible to route IPv4 traffic over an IPv6-only backhaul
(at least with Linux gear):

# ip r add 10.0.0.1 via inet6 fe80::1 dev wg0
# ip r | grep 10.0.0.1
10.0.0.1 via inet6 fe80::1 dev wg0

There's an (expired, unfortunately; we should fix that) IETF draft
describing the general mechanism:
https://www.ietf.org/archive/id/draft-chroboczek-int-v4-via-v6-01.html

And an extension for the Babel routing protocol to implement this (so
you can route v4 traffic through a whole network without assigning
anything other than v6 link-local addresses to the intermediate nodes):

https://datatracker.ietf.org/doc/html/rfc9229

-Toke

  parent reply	other threads:[~2022-10-26 20:52 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
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 [this message]
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=87wn8m1f5c.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=dandenson@gmail.com \
    --cc=libreqos@lists.bufferbloat.net \
    --cc=robert.chacon@jackrabbitwireless.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