I wrongly pasted your errors, but 78.150.32.0/20 and 78.150.44.0/22 are
the correct ones.
--
Alarig
On Sat 10 Oct 2020 22:05:45 GMT, Fabiano D'Agostino wrote:
> How does roa_check(roa_table,net,bgp_path.last) work?
> Having such a ROA as example:
> origin AS: 64513
> prefix: 78.150.40.0/20
> max mask: 24
>
> and a BGP announcement:
> origin AS: 64514
> prefix: 78.150.45.0/22
>
> so it's as
How does roa_check(roa_table,net,bgp_path.last) work?
Having such a ROA as example:
origin AS: 64513
prefix: 78.150.40.0/20
max mask: 24
and a BGP announcement:
origin AS: 64514
prefix: 78.150.45.0/22
so it's as invalid, but how does this check work?
roa_table: validated roa record (validated
Hi, all
Before commit `f9deedf1`, BFD was implemented allowing only one instance of BFD
protocol. The implementation was not prepared for multiple BFD protocol
instances. In that commit, to support VRF, the check for multiple BFD instances
was removed, which results in the possibility that
Hi, all
In bird, BFD sessions are distinguished only by their peers' address, so if
multiple routing protocols request BFD session for the same neighbor, they can
share and be controlled by one session. Normally it won't be a problem.
However, it is not the case when it come to the IPv6
Hello,
I am using bird-2.0.7 on Debian 10 to dump the RIBs tables.
The tables generated for IPv4 are fine when parsed using mrt2bgpdump or
bgpscanner.
But when I parse the IPv6 table, mrt2bgpdump doesn't return anything and
bgpscanner gives the following error:
bgpscanner: master6.mrt: bad RIB
Hi, all
I encountered a problem when trying to configure a static IPv6 route the
nexthop of which is a link-local address.
```
protocol static {
route 2001:db8:1::/48 via fe80::1234%foo;
}
```
The above configuration worked well for routing traffic to 2001:db8:1::/48 to
the router
