summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2023-04-21Alpha0 news addedv3.0-alpha1Ondrej Filip
2023-04-18Updated the version number to not include dash (breaks RPM)Maria Matejka
2023-04-18NEWS and version updateMaria Matejka
2023-04-18Merge tag '3.0-alpha0' into HEADMaria Matejka
3.0-alpha0
2023-04-17IO: added a specific loop pickup group for BFD; to be done better in futureMaria Matejka
2023-04-14Merge commit '9e44ace3' into thread-next-ifaceMaria Matejka
2023-04-14Merge commit 'f881b98d' into thread-next-ifaceMaria Matejka
2023-04-14Merge commit '231c6385' into thread-next-ifaceMaria Matejka
2023-04-14Merge commit '2f080b54' into thread-next-ifaceMaria Matejka
2023-04-14Merge commit '6c058ae4' into thread-next-ifaceMaria Matejka
2023-04-14Merge commit '913ec57f' into thread-next-ifaceMaria Matejka
2023-04-14Merge commit 'ee919658' into thread-next-ifaceMaria Matejka
2023-04-14Merge commit '0851fcde' into thread-next-ifaceMaria Matejka
2023-04-14Merge commit 'dc4c5f51' into thread-next-ifaceMaria Matejka
2023-04-14BGP: Add 'allow bgp_med' option for EBGP sessionsTrisha Biswas
This option allows to treat bgp_med as regular transitive attribute on EBGP sessions (without hacks in filters). Minor changes from committer.
2023-04-13Increase tests timeoutJakub Ružička
Tests may take longer than 5 s to complete on slow/virtual machines.
2023-04-12Temporarily disable MRT as it still lacks proper locking; to be re-enabled ↵Maria Matejka
in 3.0-alpha2
2023-04-06Loop: keep running the same loop for some time if there is work to doMaria Matejka
2023-04-06BFD: fixed a request pickup race conditionMaria Matejka
When several BGPs requested a BFD session in short time, chances were that the second BGP would file a request while the pickup routine was still running and it would get enqueued into the waiting list instead of being picked up. Fixed this by enforcing pickup loop restart when new requests got added, and also by atomically moving the unpicked requests to a temporary list to announce admin down before actually being added into the wait list.
2023-04-04BGP: set free bind also for connect sockets if configuredMaria Matejka
2023-04-04BGP: sockets use sk_resume_rx and sk_pause_rxMaria Matejka
2023-04-04BGP now has its own loopMaria Matejka
2023-04-04Sockets: Unified API for main and other loopsMaria Matejka
Now sk_open() requires an explicit IO loop to open the socket in. Also specific functions for socket RX pause / resume are added to allow for BGP corking. And last but not least, socket reloop is now synchronous to resolve weird cases of the target loop stopping before actually picking up the relooped socket. Now the caller must ensure that both loops are locked while relooping, and this way all sockets always have their respective loop.
2023-04-04More efficient IO loop event execution to avoid long loopsMaria Matejka
If there are lots of loops in a single thread and only some of the loops are actually active, the other loops are now kept aside and not checked until they actually get some timers, events or active sockets. This should help with extreme loads like 100k tables and protocols. Also ping and loop pickup mechanism was allowing subtle race conditions. Now properly handling collisions between loop ping and pickup.
2023-04-04Resource dumps also write out block addressesMaria Matejka
2023-04-04Linpool: State restoration works in initial linpool stateMaria Matejka
2023-04-04Misc allocator fixesMaria Matejka
2023-04-04Allocator fix: thread local kept pages counter must be thread localMaria Matejka
2023-04-04Route feed marks only the relevant pending exports as doneMaria Matejka
2023-04-04Propagated const through route feed routinesMaria Matejka
2023-04-04Moved channel export hooks to rt.h as the channel refactoring isn't going to ↵Maria Matejka
take place soon
2023-04-04Allowing to restart a route refresh.Maria Matejka
Repeated pipe refeed should not end route refresh as the prune routine may start pruning otherwise valid routes. The same applies for BGP repeated route refresh.
2023-04-04Fixed default table configurationMaria Matejka
When changing default table behavior, I missed that it enabled to configure multiple master4 and master6 tables. Now BIRD recognizes it and fails properly.
2023-04-04Fixed use-after-free of old protocol name pointer copied into rte_owner ↵Maria Matejka
structure
2023-04-04Fixed unwanted reloads while reconfiguring protocols with import table onMaria Matejka
2023-04-04Fixed bad filter re-evaluation with import table if filtered->acceptedMaria Matejka
The import table feed wasn't resetting the table-specific route values like REF_FILTERED and thus made the route look like filtered even though it should have been re-evaluated as accepted.
2023-04-04Fixed channel stopping when reload is activeMaria Matejka
2023-04-04Fix obvious mistake in protocol debug dumpMaria Matejka
2023-04-04Fixed stopping of import request with no imports in idle tableMaria Matejka
2023-04-04Moved table hostcache updater to table service routines to not bother the ↵Maria Matejka
mainloop
2023-04-04Reducing initial channel bitmap sizes to help extreme casesMaria Matejka
2023-04-04Flowspec links must have the destination table service loop lockedMaria Matejka
2023-04-04BGP Export Table: Fixed route source objects leaking when prefix best routes ↵Maria Matejka
is updated
2023-04-04BGP: LLGR Staleness optimization dropped.Maria Matejka
This brought unnecessary complexity into the decision procedures while the performance aspects weren't worth it. It just saved one ea_list traversal when many others are also done.
2023-04-04BGP: show detailed TX state in show proto all outputMaria Matejka
2023-04-04BFD notifications respect protocol loop settingsMaria Matejka
2023-04-04Temporarily switching off time annotations of debug logMaria Matejka
The "dump *" commands are totally garbled by the time annotations.
2023-04-04Conf: Fix too early free of old configurationOndrej Zajicek
The change 371eb49043d225d2bab8149187b813a14b4b86d2 introduced early free of old_config. Unfortunately, it did not properly check whether it is not still in use (blocked by obstacle during reconfiguration). Fix that. It also means that we still could have a short peak when three configs are in use (when a new reconfig is requeste while the previous one is still active).
2023-04-04Interface subsystem lockingMaria Matejka
2023-04-04Proto: published protocol-loop connectionsMaria Matejka