Hi,
I have a pretty simple design: two edge routers, one hypevisor. The
routing is done with the help of BGP.
regis is the hypervisor.
+-+ +---+
| nominoe | | budic |
+-+ +---+
\ /
\ /
\ / AS204092
Hello Ondrej,
thank you very much! :)
I modified the filter using your workaround. The prefix is now exported
with the correct AS path.
Best regards,
Daniel
Diff:
+ if !defined(bgp_path) then {
+bgp_path.empty;
+ }
+
Ondrej Zajicek wrote:
> A workaround is to use something like:
>
> i
On Wed, Dec 20, 2017 at 03:10:06PM +0100, Miłosz Oller wrote:
> Hi
>
> Tell me please, why in one definition of protocol can be only one neighbor
> and can be two channels.
Because one protocol = one BGP session = one TCP connection = one neighbor
IP address.
But routes of multiple address famil
On Wed, Dec 20, 2017 at 12:25:18PM +, Andrea Verni wrote:
> Hi guys,
>
> I noticed that the VM where I have deployed BIRD is having ~5 sec of 100% cpu
> used by the "vmtoolsd". This started to happened since I introduced a IPv6
> peering (full table).
>
> I found a discussion where someone
On Wed, Dec 20, 2017 at 06:11:42PM +0100, Daniel Czerwonk wrote:
> Hello bird users,
>
> I just started to test bird 2.0 and converted the existing bird 1.6
> configuration to bird 2.0. I compiled bird 2.0.0 on my fedora test VM
> and got it running. But when I use path prepending in BGP (the same
Hello bird users,
I just started to test bird 2.0 and converted the existing bird 1.6
configuration to bird 2.0. I compiled bird 2.0.0 on my fedora test VM
and got it running. But when I use path prepending in BGP (the same way
I did in 1.6) bird throws an error and does not export the route. Does
Hi
Tell me please, why in one definition of protocol can be only one
neighbor and can be two channels.
Channel ipv4
State: UP
Table: master4
Preference: 100
Input filter: ACCEPT
Output filter: ipv4_export_global_retn
Routes: 671182 impo
Hi guys,
I noticed that the VM where I have deployed BIRD is having ~5 sec of 100% cpu
used by the "vmtoolsd". This started to happened since I introduced a IPv6
peering (full table).
I found a discussion where someone was suggesting to set the poll-interval=900
in the 'tools.conf'. I did that
