Re: Help with AS-Path manipulation

2018-09-15 Thread Saku Ytti
You could recreate the route via static route and depend on existing one. In static route you can attach AS-PATH in any way you want. route 2.20.144.0/22 unreachable { bgp_local_pref = 0; bgp_path.prepend(20940); bgp_path.prepend(20940); bgp_path.prepend(10429); bgp_path.prep

Re: Multiple neighbours between same devices

2018-09-11 Thread Saku Ytti
Hey Ondrej, On Tue, 11 Sep 2018 at 14:01, Ondrej Zajicek wrote: > You are right, there is a lock to avoid run two instances for the same > neighbor. Although the primary reason for this lock is to have proper > ordering of protocol startups during reconfiguration. We should fix it > to avoid thi

Re: Multiple neighbours between same devices

2018-09-10 Thread Saku Ytti
. Fugly hack to deal with what is broken sanity check. And in fact the hack probably shouldn't work, we likely shouldn't accept those sessions as peerPort is not right. But for me this works great for now :) On Mon, 10 Sep 2018 at 13:54, Saku Ytti wrote: > > I'm trying to setup

Multiple neighbours between same devices

2018-09-10 Thread Saku Ytti
I'm trying to setup between DUT<->Bird in same interface multiple iBGP neighbours with DUT IP and routerID staying same, and Bird sourceIP and table changing. If I configure just 1, it works grand, the 2nd one won't come up. If I change the order, the previous one which didn't work now works, and

Re: constant not available everywhere and passing variables from protocols

2018-03-21 Thread Saku Ytti
On 21 March 2018 at 12:13, Jan Maria Matejka wrote: >> Why not? It barfs with 'line 10: IP address expected' > > In v1.6.x, nobody implemented it. In v2, it should work. Thanks, will consider upgrading. > Try 'import where yourCustomImportFunction(arg1, arg2, arg3, ... argN)'. Thanks. Are th

constant not available everywhere and passing variables from protocols

2018-03-21 Thread Saku Ytti
My config: define local_ip = 129.250.14.127; define default_candidate_net = 129.250.0.0/16; define default_candidate_ip = 129.250.0.0; define default_net = 0.0.0.0/0; include "common.conf"; protocol static { route 0.0.0.0/0 recursive default_candidate_ip; } # ens192 pro

Re: static routes and 'src' parameter

2018-03-20 Thread Saku Ytti
ople! On 20 March 2018 at 20:22, Saku Ytti wrote: > I want default address to use lo as source for locally originated > connections. Is this possible? > > bird> show route > 0.0.0.0/0 via 204.141.224.2 on ens224 [static1 18:11:50] * (200) > 129.250.15.29/32

static routes and 'src' parameter

2018-03-20 Thread Saku Ytti
I want default address to use lo as source for locally originated connections. Is this possible? bird> show route 0.0.0.0/0 via 204.141.224.2 on ens224 [static1 18:11:50] * (200) 129.250.15.29/32 dev lo [direct1 18:11:50] * (240) 129.250.0.0/16 via 204.141.224.2 on ens224 [red 18:17