Many ISPs need the kinds of quality shaping cake can do
 help / color / mirror / Atom feed
From: "Robert Chacón" <robert.chacon@jackrabbitwireless.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] Ipv6 testing
Date: Sun, 30 Oct 2022 19:02:40 -0600	[thread overview]
Message-ID: <CAOZyJovkdL69aA03dv7AzDVB7=7hQyTJ5Xx94SbWD26eG7wktg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5TJGHftpdaatFyGw8BadKAq90O3L7Y9yD-_xZCARLNxw@mail.gmail.com>

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

Hoping to test IPv6 as well. In order to do so I need to get Mikrotik's ROS
v7 implemented on two major edge routers on our network (BGP performance is
way more stable on v7 - trying to avoid reboots).
Once that's done in a few weeks I can start testing IPv6 performance more
thoroughly. =)

On Sun, Oct 30, 2022 at 6:52 PM Dave Taht via LibreQoS <
libreqos@lists.bufferbloat.net> wrote:

> I know I'm pretty lonely on the ipv6 front 'round here, but some notes
> towards doing that for libreqos v1.3 start here.
>
> https://github.com/rchac/LibreQoS/issues/144
>
> Well over 50% of my traffic is ipv6.
>
> --
> 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
>


-- 
Robert Chacón
CEO | JackRabbit Wireless LLC <http://jackrabbitwireless.com>
Dev | LibreQoS.io

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

      reply	other threads:[~2022-10-31  1:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31  0:52 Dave Taht
2022-10-31  1:02 ` Robert Chacón [this message]

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='CAOZyJovkdL69aA03dv7AzDVB7=7hQyTJ5Xx94SbWD26eG7wktg@mail.gmail.com' \
    --to=robert.chacon@jackrabbitwireless.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