#frrouting — Public Fediverse posts

Катастрофоустойчивый Kubernetes: как использовать балансировщик MetalLB с BGP-anycast

Клиенты часто спрашивают, как построить геораспределенный и катастрофоустойчивый

https://habr.com/ru/companies/selectel/articles/992092/

#k8s #metallb #anycast #frrouting #selectel

IPv6 should be treated the same as, if not better than, IPv4!

https://github.com/FRRouting/frr/issues/20067
https://github.com/FRRouting/frr/issues/20102

#IPv6 #frr #frrouting

#BSDRouterProject 1.994 has been released (#BSDRouter / #BSDRP / #BSD / #RouterDistribution / #NanoBSD / #FreeBSD / #FRRouting / #FreeRangeRouting / #BIRDInternetRoutingDaemon) https://bsdrp.net/

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