Ruby.social

0 posts0 participants0 posts today

ItzTrain<a href="https://transitory.social/@rachel" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@rachel</a> I have been in my software router era for a very long time with <a href="https://hachyderm.io/tags/VyOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VyOS</a> then <a href="https://hachyderm.io/tags/openwrt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openwrt</a> then back to <a href="https://hachyderm.io/tags/VyOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VyOS</a> tried to sprinkle <a href="https://hachyderm.io/tags/frr" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#frr</a> around there too. It just took a little bit of cognitive load when updating the host or the software I'm using as my virtualization layer.. Now! I just been on this router for like 4 days.. I might be full of shit 😂😂😂

36pickledeggsThis is what the new cluster looks like cabled up. Sexy, eh? For the OS, I decided to go with RHEL 9.5. There are reasons. Red Hat really made some super dumb moves around CentOS Stream, but I don't think they are evil. Setting up the routing for the ring topology network using <a href="https://fosstodon.org/tags/FRR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FRR</a> seems to work. I'm getting about 26.6Gbit/sec across the Thunderbolt 4 interfaces. That is using ipv6. ipv4 is not quite working on those for me. And that is my blocker for <a href="https://fosstodon.org/tags/rookceph" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rookceph</a>.

バルテクMoved my VPS from <a href="https://fosstodon.org/tags/Rocky" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rocky</a> 9 to <a href="https://fosstodon.org/tags/NetBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a> 10.1. Surprisingly it works fine - sans a quirky GRE implementation... I made it work in the end but all other network devices are able to use any subnet on a GRE interface.In the end I have: - <a href="https://fosstodon.org/tags/wireguard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#wireguard</a> to multiple <a href="https://fosstodon.org/tags/MikroTik" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MikroTik</a> routers - GRE tunnels to all of the routers - <a href="https://fosstodon.org/tags/FRR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FRR</a> running <a href="https://fosstodon.org/tags/BGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BGP</a> - <a href="https://fosstodon.org/tags/haproxy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#haproxy</a> doing reverse proxy for <a href="https://fosstodon.org/tags/Nextcloud" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nextcloud</a> and other services - <a href="https://fosstodon.org/tags/certbot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#certbot</a> renewing Let's Encrypt certificate

Jess ⨂ :v_trans:Someone out there might find this useful. I was fighting with getting an <a href="https://tech.lgbt/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6</a> <a href="https://tech.lgbt/tags/bgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bgp</a> session up between my Raspberry Pi running <a href="https://tech.lgbt/tags/pihole" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pihole</a> and <a href="https://tech.lgbt/tags/frr" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#frr</a> and my layer 3 switch. IPv4 worked fine. I wasn't really understanding the error on my switch and rebuilt the configs on both sides multiple times.The answer was the fact that my systemd-networkd wasn't creating a link-local address. After modifying the conf file to explicitly create one and restarting both services, I was finally good to go.This was a huge help in identifying the problem after enabling logging in FRR. <a href="https://connormcf.com/blog/frr-nexthop-set-failed/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://connormcf.com/blog/frr-nexthop-set-failed/</a>

ItzTrainI got tired of fussing with <a href="https://hachyderm.io/tags/FRR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FRR</a> and trying to use it to do VRF's and routing as it really is geared towards Dynamic Routing! Back to <a href="https://hachyderm.io/tags/VyOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VyOS</a> for the <a href="https://hachyderm.io/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homelab</a>. I am still using VRRP with 3 FRR routers on my <a href="https://hachyderm.io/tags/incus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incus</a> hosts. So as long as my upstream router is up. I can reboot hosts all day long and no internet go down.<a href="https://hachyderm.io/tags/selfhosted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosted</a> <a href="https://hachyderm.io/tags/selfhosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosting</a>

ItzTrainYo!! this shit kinda 🔥!! I'm using 2 lxc containers that are using the FRR project. I configured the <a href="https://hachyderm.io/tags/frr" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#frr</a> packages to use <a href="https://hachyderm.io/tags/VRRP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VRRP</a> for both lxc instances. I now have redundant gateways for the <a href="https://hachyderm.io/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homelab</a> . I dropped one packet as it switch over! <a href="https://hachyderm.io/tags/selfhosted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosted</a> <a href="https://hachyderm.io/tags/selfhosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosting</a> <a href="https://hachyderm.io/tags/incus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incus</a>

ijUhm, the other day I change my <a href="https://nerdculture.de/tags/Ceph" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ceph</a> setup that way, that I now use <a href="https://nerdculture.de/tags/FRR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FRR</a> & <a href="https://nerdculture.de/tags/OSPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OSPF</a> to utilize both links in my 3-node setup. So each node has a dedicated 10 GbE link to its neighbours, forming a ring (or triangle). Then I also changed my setup and added a SSD as my WAL/DB device for my OSDs (2 TB SSD split into 2x 1 TB for WAL/DB, one for each OSD). Although I see a slight speed increase in recovery speed, the increase is still below the expected performance: only 100-150 MB/s in most cases with 2x Seagate Exos X18 18 TB drives. Each drive can deliver up to 270 MB/s, according to technical datasheet.So, I would expect to see more like 200-400 MB/s. MTU is 9000 bytes . ceph -s reports: recovery: 182 MiB/s, 8 keys/s, 144 objects/sAny ideas how to increase the speed?

gyptazyJust a reminder: You can now also peer with <a href="https://mastodon.bsd.cafe/@BoxyBSD" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@BoxyBSD</a> via <a href="https://mastodon.gyptazy.com/tags/BGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BGP</a> as AS4242423588 (upstreamed by AS4242421344 / gyptazy Solutions) and minimize the latency to your <a href="https://mastodon.gyptazy.com/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a>, <a href="https://mastodon.gyptazy.com/tags/NetBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a> and <a href="https://mastodon.gyptazy.com/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenBSD</a> boxes in the <a href="https://mastodon.gyptazy.com/tags/DN42" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DN42</a> network! You can now also access your box via DN42 IPv4 in addition to IPv6 clearnet!Happy peering!<a href="https://mastodon.gyptazy.com/tags/BoxyBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BoxyBSD</a> <a href="https://mastodon.gyptazy.com/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv4</a> <a href="https://mastodon.gyptazy.com/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> <a href="https://mastodon.gyptazy.com/tags/network" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#network</a> <a href="https://mastodon.gyptazy.com/tags/frr" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#frr</a> <a href="https://mastodon.gyptazy.com/tags/bird" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bird</a> <a href="https://mastodon.gyptazy.com/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homelab</a> <a href="https://mastodon.gyptazy.com/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://mastodon.gyptazy.com/tags/education" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#education</a> <a href="https://mastodon.gyptazy.com/tags/Runbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Runbsd</a> <a href="https://mastodon.gyptazy.com/tags/BSDCafe" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BSDCafe</a> <a href="https://mastodon.gyptazy.com/tags/BSDNetwork" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BSDNetwork</a>

ijHmmm, <a href="https://nerdculture.de/tags/pfSense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pfSense</a> with <a href="https://nerdculture.de/tags/Wireguard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Wireguard</a> and <a href="https://nerdculture.de/tags/OSPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OSPF</a> / <a href="https://nerdculture.de/tags/FRR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FRR</a> seems to be a little more complex than thought. At least when you want to join an existing network based on <a href="https://nerdculture.de/tags/Debian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Debian</a> an <a href="https://nerdculture.de/tags/Bird" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bird</a> OSPF and Wireguard.

equiWhen we implemented live log display in <a href="https://chaos.social/tags/FRR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FRR</a>|'s CLI client, it was an amazing feature but I didn't think much of it. Now I've seen <a href="https://chaos.social/tags/strongSwan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#strongSwan</a>|'s swanctl do even better (it seems to explicitly show logs related to the SA you're dealing with), and it's driving me to a conclusion:All long-running daemons with a control interface need to do this. It's a basic UX requirement.And this shouldn't just be "tail -f" on the log, it should show context-relevant low priority messages disabled elsewhere.

ijCan bird ospf interact with frr ospf?I always get authentication method mismatch (2) in bird logs, but the password is correct. frr is running here on <a href="https://nerdculture.de/tags/pfsense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pfsense</a>, bird is standard Debian version.<a href="https://nerdculture.de/tags/ospf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ospf</a> <a href="https://nerdculture.de/tags/bird" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bird</a> <a href="https://nerdculture.de/tags/frr" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#frr</a>

Stéphane BortzmeyerPour le routage, <a href="https://mastodon.gougere.fr/tags/FRR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FRR</a> (la machine a un pair <a href="https://mastodon.gougere.fr/tags/BGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BGP</a>). Contrairement au Cisco, on peut utiliser <a href="https://mastodon.gougere.fr/tags/Puppet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Puppet</a>. <a href="https://mastodon.gougere.fr/tags/JRES2019" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#JRES2019</a>

Recent searches

Search options

Administered by:

Server stats:

#FRR