- Mar 30, 2021
-
-
Maria Matejka authored
-
Ondřej Zajíček authored
The flag makes sense just in external representation. It is reset during BGP export, but keeping it internally broke MRT dumps for short attributes that used it anyways. Thanks to Simon Marsh for the bugreport and the patch.
-
- Mar 18, 2021
-
-
Ondřej Zajíček authored
BGP statistics code was preliminary and i wanted to replace it by separate 'show X stats' command. The patch hides the preliminary output in 'show protocols all' so it is not part of the released version.
-
- Mar 17, 2021
-
-
Ondřej Zajíček authored
-
Ondřej Zajíček authored
-
- Mar 16, 2021
-
-
Ondřej Zajíček authored
Pipe channels are kind-of implicit, so setting protocol debug flags should also set pipe debug flags.
-
Ondřej Zajíček authored
In OSPFv3, only Hello and DBDes packets contain flags specifying whether RFC 7166 authentication trailer is used. Other packets are processed based on stored authentication state in neighbor structure. Update this state with each received Hello to handle authentication change from reconfigurations. Thanks to Joakim Tjernlund and Kenth Eriksson for the bugreport.
-
- Mar 10, 2021
-
-
Ondřej Zajíček authored
-
- Feb 12, 2021
-
-
Ondřej Zajíček authored
Also, no automatic reload for BGP channels without import/export table.
-
- Feb 10, 2021
-
-
This is an implementation of draft-walton-bgp-hostname-capability-02. It is implemented since quite some time for FRR and in datacenter, this gives a nice output to avoid using IP addresses. It is disabled by default. The hostname is retrieved from uname(2) and can be overriden with "hostname" option. The domain name is never set nor displayed. Minor changes by committer.
-
- Jan 22, 2021
-
-
Ondřej Zajíček authored
Flag signalling that MP-BGP mode should be used got reset after first batch of routes, so remaining routes were processed without that, leading to missing MP_REACH_NLRI attribute. Thanks to Piotr Wydrych for the bugreport.
-
- Jan 12, 2021
-
-
Ondřej Zajíček authored
Add fake MP_REACH_NLRI attribute with BGP next hop when encoding MRT table dumps for IPv6 routes. That is necessary to encode next hop as NEXT_HOP attribute is not used for MP-BGP. Thanks to Santiago Aggio for the bugreport.
-
- Jan 10, 2021
-
-
Ondřej Zajíček authored
Direct BFD sessions needs to be dispatched not only by IP addresses, but also by interfaces, in order to avoid collisions between neighbors with the same IPv6 link-local addresses. Extend BFD session hash_ip key by interface index to handle that. Use 0 for multihop sessions. Thanks to Sebastian Hahn for the original patch.
-
- Jan 07, 2021
-
-
Ondřej Zajíček authored
It was mixed-up if hostname is IPv6 address, and reporting separate values (like port) on separate lines fits better into key-value style of 'show protocols all' output. Also, the patch simplifies transport identification formatting (although it is unused now). Thanks to Alarig Le Lay for the suggestion.
-
- Jan 06, 2021
-
-
Ondřej Zajíček authored
The option is not implemented since transition to 2.0 and no plan to add it. Also remove some deprecated RTS_* valus from documentation. Thanks to Sébastien Parisot for notification.
-
- Dec 28, 2020
-
-
Ondřej Zajíček authored
We need to define 'net' field temporarily as it may be accessed by per-route filters. Thanks to Damian Zaremba for the bugreport.
-
- Dec 07, 2020
-
-
Ondřej Zajíček authored
The patch add support for per-channel debug flags, currently just 'states', 'routes', and 'filters'. Flag 'states' is used for channel state changes, remaining two for routes passed through the channel. The per-protocol debug flags 'routes'/'filters' still enable reporting of routes for all channels, to keep existing behavior. The patch causes minor changes in some log messages.
-
- Nov 25, 2020
-
-
Ondřej Zajíček authored
This fixes an issue with dirty node passed to add_tail(). Thanks to Andreas Rammhold for the initial patch.
-
- Nov 24, 2020
-
-
Ondřej Zajíček authored
When config structures are copied due to template application, we need to reset list node structure before calling add_tail(). Thanks to Mikael Magnusson for patches.
-
Ondřej Zajíček authored
-
The babel protocol code was initialising objects returned from the slab allocator by assigning to each of the struct members individually, but wasn't touching the NODE member while doing so. This leads to warnings on debug builds since commit: baac7009 ("List expensive check.") To fix this, introduce an sl_allocz() variant of the slab allocator which will zero out the memory before returning it, and switch all the babel call sites to use this version. The overhead for doing this should be negligible for small objects, and in the case of babel, the largest object being allocated was being zeroed anyway, so we can drop the memset in babel_read_tlv().
-
- Nov 19, 2020
-
-
Ondřej Zajíček authored
Add support for proper handling of multiple routes with the same network to the static protocol. Routes are distinguished by internal index, which is assigned automatically (sequentially for routes within each network). Having different route preference or igp_metric attribute is optional.
-
- Nov 18, 2020
-
-
Ondřej Zajíček authored
When a new link-LSA is originated, we need to notify intra-area-prefix-LSA handling, like when a new link-LSA is received. Otherwise a new network prefix added to a DR is not propagated immediately. Thanks to Bala Sajja for the bugreport.
-
- Nov 12, 2020
-
-
Ondřej Zajíček authored
Merge multiple BFD option blocks in BGP configs instead of using the last one. That is necessary for proper handling of templates when BFD options are used both in a BGP template and in a BGP protocol derived from that template.
-
Ondřej Zajíček authored
-
- Nov 08, 2020
-
-
Ondřej Zajíček authored
BFD session options are configured per interface in BFD protocol. This patch allows to specify them also per-request in protocols requesting sessions (currently limited to BGP).
-
- Oct 11, 2020
-
-
Ondřej Zajíček authored
Add 'ignore max length' option to RPKI protocol, which ignores received max length in ROA records and instead uses max value (32 or 128). This may be useful for implementing loose RPKI check for blackholes.
-
- Aug 31, 2020
-
-
Maria Matejka authored
-
- Aug 12, 2020
-
-
Ondřej Zajíček authored
Sometimes multicast OSPF packet is received when neighbor adjacency is not established. Such packet should be ignored earlier in packet processing as otherwise it causes strange error messages when OSPFv3 authentication is enabled.
-
- Jun 28, 2020
-
-
Ondřej Zajíček authored
Most commands like 'show ospf neighbors' fail when protocol is not specified and there are multiple instances of given protocol type. This is annoying in BIRD 2, as many protocols have IPv4 and IPv6 instances. The patch changes that by showing output from all protocol instances of appropriate type. Note that the patch also removes terminating cli_msg() call from these commands and moves it to the common iterating code.
-
- Jun 10, 2020
-
-
Ondřej Zajíček authored
Thanks to Slava Aseev for the thorough bugreport.
-
- Jun 03, 2020
-
-
Compare the new timing parameters with the old configuration, not with the temporary state of the current connection. The timing values in struct rpki_cache is updated by a version 1 End Of Data PDU, unless this behavior is suppressed by the configuration explicitly by the "keep" keyword. Consequently, every reconfiguration of BIRD triggers a reconnection even if it is not necessary.
-
- Jun 02, 2020
-
-
Maria Matejka authored
-
- May 26, 2020
-
-
Ondřej Zajíček authored
If the next hop of a route is not a reachable address, the route should be installed as onlink. This enables a configuration common in mesh networks where the mesh interface is assigned a /32 and babel handles the routing by installing onlink routes. Thanks to Toke Hoiland-Jorgensen for the patch.
-
Ondřej Zajíček authored
This issue has a long history. In 2012, we changed data field for unnumbered PtP links from iface id (specified by RFC) to IP address based on reports of bugs in Quagga that required it, and we used out-of-band information to distinquish unnumberred PtPs with the same local IP address. Then with OSPF graceful restart implementation, we found that we can no longer use out-of-band information, and we need to use only LSAdb info for routing table calculation, but i forgot to finish handling of this case, so multiple unnumbered PtPs with the same local IP addresses were broken. Considering that even recent Mikrotik RouterOS has broken next hop calculation that depends on IP address in PtP link data field, we cannot just switch back to the iface id for unnumbered PtP links. The patch makes two changes: First, it goes back to use out-of-band (position) info for distinguishing local interfaces in SPF when graceful restart is not enabled, while still uses LSAdb-only approach for SPF calculation when graceful restart is enabled. Second, it adds OSPF interface option 'ptp address', which controls whether IP address or iface id is used in data field. It is enabled by default except for unnumbered PtP links with enabled graceful restart. Thanks to Kenth Eriksson for the bugreport and Joakim Tjernlund for suggestions.
-
- May 19, 2020
-
-
Ondřej Zajíček authored
-
- May 12, 2020
-
-
Ondřej Zajíček authored
-
- May 01, 2020
-
-
Maria Matejka authored
-
Maria Matejka authored
-
Maria Matejka authored
-