eave them intact. (e.g. RR
> clients can export some private ip ranges which I don't want to be routable
> on the RRs)
So I *think* that I need a way on the RRs to only change next hop of EBGP
> prefixes that get exported from RRs to RR clients but leave other prefixes
> unaffected
1.1/32, 2.2.2.2/32] {
preference = 90;
}
accept;
}
}
With that said, is this a correct fix, or is there a more generic solution
around this issue?
Thanks!
czw., 29 lip 2021 o 12:06 Ondrej Zajicek
napisał(a):
> On Thu, Jul 29, 2021 at 11:34:18AM +0200,
Hi,
I am trying to setup two route reflectors (that also pass traffic) that
peer with ebgp (and exchange routes via ibgp between themselves). So
something like.
as100 as200
||
||
ebgp ebgp
Hello.
I have a FreeBSD x64 10.2-p7 system with Bird 1.5.0 acting as a PPPOE
concentrator using MPD5 version 5.7
The system has 2 physical interfaces:
ix0 ( a /30 connection to another freebsd router - ABR running Bird )
ix1 ( listening for PPPOE via MPD5 )
And many virtual interfaces when a P
