imagine. The fact that this sounds so troubling makes me think: Am I
doing something conceptually wrong?
How would one implement my scenario?
>
> On 2024-01-10 00:28, Lukas Haase via Bird-users wrote:
> > Hi,
> >
> > I have two "border gateways"; each establishes a BGP
just export via a filter like this?
export filter {
if (net ~ [192.0.2.0/24{25,32}]) then {
accept;
}
reject;
}
Thanks,
Luke
> You can also make some external daemon watching your kernel routes
> and adding/deleting the aggregate route to the table.
>
> R
gt; {
> > > > route 192.0.2.0/24 via 192.0.2.209;
> > > > route 192.0.2.0/24 via 192.0.2.250;
> > > > route 192.0.2.0/24 via 192.0.2.285;
> > > > route 192.0.2.0/24 via 192.0.2.254;
> > > > route 192.0.2.0/24 via 192.0.2.177;
>
main
> table and reachability tested in bgp export filter for example.
>
>
> ipv4 table aggr;
>
> protocol static prefix_aggregation
> {
> ipv4 { table aggr4; };
> route 192.0.2.0/24 recursive 192.0.2.209;
> ...
> }
>
> protocol pipe pip
Hello,
My BFD session between bird work fine but the ones but the ones to VyOS (which
uses FFR) just won't connect:
# birdc show bfd sess
BIRD 2.0.8 ready.
bfd1:
IP address Interface State Since Interval Timeout
172.20.215.131 --- Init 10:39:14.183 1.000 10.000
172.20.215.130 --- Up
the case, but I would try that first.
>
> Regards,
> Alexander
>
> On Tue, Jan 16, 2024 at 9:15 AM Lukas Haase via Bird-users
> wrote:
> >
> > Hello,
> >
> > My BFD session between bird work fine but the ones but the ones to VyOS
> > (which us
Hi,
I have two "border gateways" running bird; each establishes a BGP session to
the outside world. An internal router connects to each of the border gateways
and uses OSPF to exchange routes. (Note, other OSPF links may exist as well).
Both border gateways act as default gateways for the
Hi,
I have two "border gateways"; each establishes a BGP session to the outside
world. An internal router connects to each of the border gateways and uses OSPF
to exchange routes. (Note, other OSPF links may exist as well).
Both border gateways act as default gateways for the internal router.
Hi,
Is is somehow possible to export a larger prefix if one or more sub-prefixes
(subnets) are exported ... but also remove that prefix if no smaller subnet
exist any more?
Example: As soon as 192.0.2.44/32 or 192.0.2.208/28 (or any other prefix inside
192.0.2.0/24) is exported via eBGP, also
