From: Herbert Wolverson <herberticus@gmail.com>
Cc: libreqos@lists.bufferbloat.net
Subject: Re: [LibreQoS] routing protocols and daemons
Date: Wed, 26 Oct 2022 15:53:15 -0500 [thread overview]
Message-ID: <CA+erpM46beFMwVYeMRt7fEhOKAzUh00fbtq_mH7fXx=pe+ND4Q@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5KY4V1_01ZEaavZmkduVqjKGzO4ThZPp9Y4ACjWJ0SDg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2008 bytes --]
My name is Herbert, and I'm an OSPF addict... seriously, I love OSPF.
Right down to stub sites, not-so-stubby sites, and isolating IP blocks
within a site into "stub" nets and ensuring they are aggregated properly. I
should probably go outside more...
On Wed, Oct 26, 2022 at 3:29 PM Dave Taht via LibreQoS <
libreqos@lists.bufferbloat.net> wrote:
> OK, since I'm getting such great updates on the state of the wisp
> world, far more in a few days than I've had in 10 years... and btw, no
> need to leap on dr science guy research questions like mine if you
> have like, towers flooding or the phone ringing off the hook....
>
> What routing protocols are in use nowadays? BGP, yes, and it seems
> ospf is popular?
>
> How about ISIS?
>
> I figure babel has zero traction or awareness despite being mandated
> by the ietf homenet working group.
>
> Secondly, do you rely on BGP based on the edge router or use it in
> software (frr? quagga? bird?). Using RPKI? Push FIBs anywhere? (route
> 666 in particular)
>
> Similar question related to the IGP protocol in use, where do you rely
> on it, vs all the tunnels you have, on what kinds of hardware?
>
> I note that robert at some point, somewhere, pointed out how fq_codel
> saved his bacon when there was a major routing mishap (as there is no
> congestion control in ospf), and I'd like to hear more of that story.
>
> BATMAN has been mentioned. There's other wireless protocols I've liked
> - OLSR for example...
>
> Nobody knows what lies underneath many consumer wireless meshes
> although it looks like 802.11s is a starting point, none, so far as I
> know interoperate across brands.
>
> --
> 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
> Rip Van Winkle COO, TekLibre, LLC
> _______________________________________________
> LibreQoS mailing list
> LibreQoS@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/libreqos
>
[-- Attachment #2: Type: text/html, Size: 2764 bytes --]
next prev parent reply other threads:[~2022-10-26 20:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 20:29 Dave Taht
2022-10-26 20:53 ` Herbert Wolverson [this message]
2022-10-26 21:38 ` Dave Taht
2022-10-26 22:35 ` dan
2022-10-27 13:29 ` Herbert Wolverson
2022-10-27 15:29 ` Mark Steckel
2022-10-27 16:35 ` Dave Taht
2022-10-28 21:47 ` Juliusz Chroboczek
2022-10-28 21:45 ` Juliusz Chroboczek
2022-10-29 0:01 ` Dave Taht
2022-10-29 0:34 ` Dave Taht
2022-10-29 9:15 ` Juliusz Chroboczek
2022-10-29 13:48 ` Herbert Wolverson
2022-10-29 14:13 ` dan
2022-10-29 22:18 ` Juliusz Chroboczek
2022-10-30 0:09 ` dan
2022-10-30 13:42 ` Juliusz Chroboczek
2022-10-29 20:11 ` Juliusz Chroboczek
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='CA+erpM46beFMwVYeMRt7fEhOKAzUh00fbtq_mH7fXx=pe+ND4Q@mail.gmail.com' \
--to=herberticus@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