Hello!
I'd recommend doing some templating, and even reconsider whether the
pipe and auxiliary table is really needed. With BIRD 2 and import table
/ export table BGP setting, the pipes are just unnecessary burden in
most cases.
More on this in Rome (Nov 27, RIPE 87).
Maria
On 2023-10-13
Hi,
You can try to still have separate IPv4/IPv6 daemons and that may help
not to repeat the protocol sections. But simple include might not help
still, as the syntax requires you sometimes to specify "ipv4"/"ipv6"
for tables and channels for example. Some templating might be helpful
here though.
On 10/13/23 16:58, Nico Schottelius wrote:
Hello Robert,
Robert Sander writes:
Hi,
please help me understand the configuration logic for BIRD2.
In BIRD 1 we have a config file common.conf that gets included from
bird.conf and bird6.conf. It holds common configuration applicable to
both
Hello Robert,
Robert Sander writes:
> Hi,
>
> please help me understand the configuration logic for BIRD2.
>
> In BIRD 1 we have a config file common.conf that gets included from
> bird.conf and bird6.conf. It holds common configuration applicable to
> both IPv4 and IPv6 like this:
I believe
Hi,
please help me understand the configuration logic for BIRD2.
In BIRD 1 we have a config file common.conf that gets included from
bird.conf and bird6.conf. It holds common configuration applicable to
both IPv4 and IPv6 like this:
table bgpext;
protocol pipe p_bgpext {
table
Hi Ondrej,
as.path.len = 2 as.path.len = 1
Upstream1 Node1 ---(10ms) Node2 --(20ms)-- Upstream2
|
Node3
For this network situation, I need to have node 3 go to
Dear BIRD Users,
On 2023-09-26 10:56, Maria Matejka wrote:
I'd like to let you know that we're planning to visit several meetings
before this year ends:
* LinuxDays in Prague, October 7 (presentation in Czech),
This event is gone. The presentation was targeted on non-users of BIRD
on
