ExaBGP 5.0.8 is out.
get it at: https://t.co/e5C0YKk8Hp
And after over 100 days of dev, and a total of $0 VC raised, we are leaving stealth mode! Introducing Ze. Pronounced like "The" but with ze right accent.
WIP at: https://t.co/qLX3eNOYQJ
@lea_linux L’utilisation des variables d’environnement XDG_{CONFIG,DATA,CACHE}_HOME pour avoir ses configuration en dehors de $HOME et utiliser git pour le backup.
@arunkumar548 ExaBGP was designed to be used via its API and with health checkers. If SIGHUP is not working then it is a bug but also not the best use case.
@vince2_ BGP should be a business case on vendor-pressured design. I documented some of the issues (2017); some work to fix some of the problems since then, inc. BGP packet size, attribute ordering, etc.
https://t.co/UNnN1rtmYX
@vince2_ re-reading the rfc I would like to change my suggestion to .. no clue, as sending one should be enough as notification. So sorry for spamming you
@vince2_ Minor correction can applied retrospectively to RFCs and if other implementations are only sending one the wording could be updated to something like “any valid EOR” for better clarity going forward
@vince2_ It may be that one is enough but sending multiple should be harmless and therefore my take … but it may be worth asking one the ietf mailing list
#slack
https://t.co/8N6ClzBQXC - Massive downgrade here, it goes from nearly unlimited to 3 months.
"The majority of our active free teams will have access to more of their message history", with the "active team" definition missing ..
But still thank you for the free tier.
@lqaddict @vince2_@taktv6 Thank you @lqaddict . I did not plug ExaBGP when I normally never miss an opportunity 😈 and praised biorouting instead as I think my solution is not best for Vincent’s use case 😉 Thank you for suggesting it though 👍