L’EUROPE INVESTIT AUTREMENT

Prêts, garanties, fonds propres : les instruments financiers du plan Next Generation EU prolongent l’impact au-delà de 2026. Une Europe qui prête pour bâtir, plutôt que subventionner sans lendemain.

https://whatsapp.com/channel/0029VaE5Wl8Dp2Q7vJyg0G30

#EuroScope #NextGenerationEU #Relance #Investissement #TransitionVerte #FRR

Just made a small app for Flammenrouge racing tour :)

https://frr2025.streamlit.app/

#frr #zwift #plotting #flammenrougeracing

Анонсируем Full-View на изолированном стенде

Мы разрабатываем сервис, который поможет сетевикам управлять аплинками. В процессе подготовки стенда для тестирования потребовалось в изолированном окружении развернуть виртуальный маршрутизатор и анонсировать на него несколько Full-View.

https://habr.com/ru/articles/887732/

#bgp #frr #linux #fullview #vmx

FRRouting. Без кликбейтного названия

Вот есть у нас, например, два хоста-клиента и есть один Linux. Хосты из одной сети. Надо чтобы пообщаться смогли они друг с дружкой...

https://habr.com/ru/articles/884824/

#FRR #маршрутизация #mpls #evpnvxlan

#frr weirdness: ospf6d accumulated a ton of duplicate routes for 2 peering links and an anycast subnet around 66-68 days ago. there's 13.4k entries for the anycasted /64 and 5.6k/5.8k for the two /127s
none of the other routes are unusual

@rachel I have been in my software router era for a very long time with #VyOS then #openwrt then back to #VyOS tried to sprinkle #frr 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 😂😂😂

I am confused by FRR.

https://docs.frrouting.org/en/latest/bgp.html

"-l, --listenon - Specify specific IP addresses for bgpd to listen on[...] Note that this option implies the –no_kernel option, and no learned routes will be installed into the linux kernel."

But they are installed into the kernel table! I can see it (with ip -6 route show table 50).

Is this because it's an bgpd option, and the routes go via zebra instead?

Config:
https://privatebin.net/?6461c22964ba20b8#BtwSKdrrRPu2tx8DQwfqyBaDU2gjdD5MqSYTUejXBTMq
and
https://privatebin.net/?34bd84b23b49a596#AVw68P7USz458c8hgk91GZ9dBmJZCADEw2Mq2gYtBw7y

And even if it did. what if I want to run multiple instances of bgpd and to install the routes into the kernel?

edit:

The docs seem to be wrong. Adding "-n", the routes are indeed not installed in the routing table.

#frr #frrouting

Updating #frr routing software when 9462km away from the system. What could probably go wrong? #yoloOps

Moved my VPS from #Rocky 9 to #NetBSD 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:
- #wireguard to multiple #MikroTik routers
- GRE tunnels to all of the routers
- #FRR running #BGP
- #haproxy doing reverse proxy for #Nextcloud and other services
- #certbot renewing Let's Encrypt certificate

Quick ubiquiti #unifi q: can someone who's running OS 4.1 on something that doesn't *officially* support BGP tell me if #frr is still the same as in the 4.0 releases?

Someone out there might find this useful. I was fighting with getting an #ipv6 #bgp session up between my Raspberry Pi running #pihole and #frr 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.
https://connormcf.com/blog/frr-nexthop-set-failed/

I got tired of fussing with #FRR and trying to use it to do VRF's and routing as it really is geared towards Dynamic Routing! Back to #VyOS for the #homelab. I am still using VRRP with 3 FRR routers on my #incus hosts. So as long as my upstream router is up. I can reboot hosts all day long and no internet go down.

#selfhosted #selfhosting

Yo!! this shit kinda 🔥!! I'm using 2 lxc containers that are using the FRR project. I configured the #frr packages to use #VRRP for both lxc instances. I now have redundant gateways for the
#homelab . I dropped one packet as it switch over!

#selfhosted
#selfhosting
#incus

VyOS 1.5 is somehow broken for me: Babel does not work at all (not even with the example from the documentation) and with BGP you cannot set a source address for installed routes (possible with route-map set src, but has no effect).

The rolling release seems to be enormously rolling.

#VyOS #Babel #FRR #BGP #Networking

Uhm, the other day I change my #Ceph setup that way, that I now use #FRR & #OSPF 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/s

Any ideas how to increase the speed?

Just a reminder: You can now also peer with @BoxyBSD via #BGP as AS4242423588 (upstreamed by AS4242421344 / gyptazy Solutions) and minimize the latency to your #FreeBSD, #NetBSD and #OpenBSD boxes in the #DN42 network! You can now also access your box via DN42 IPv4 in addition to IPv6 clearnet!

Happy peering!

#BoxyBSD #IPv4 #IPv6 #network #frr #bird #homelab #linux #education #Runbsd #BSDCafe #BSDNetwork

So I decided to spin up #frr on my home testing setup again (recently switched to bird2) and oh well...

Hmmm, #pfSense with #Wireguard and #OSPF / #FRR seems to be a little more complex than thought. At least when you want to join an existing network based on #Debian an #Bird OSPF and Wireguard.

After hours of messing about with #frr, I settled down for a few rounds of Quake 3.

5yo: "Daddy why is it called the BFG?"

When we implemented live log display in #FRR|'s CLI client, it was an amazing feature but I didn't think much of it. Now I've seen #strongSwan|'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.