I was hoping someone could assist with defining a local constant for a BGP 'source address' through dynamic means. An example would be 'router id from' where a mask and prefix can be identified to inherit the router ID. router id from "lo*" 192.168.0.0/24; saddr = <whatever router id inherited> I was hoping that router id would be an internal symbol, but I don't see it in the 'show symbols ...' output. Any thoughts? The goal is to make this configuration as dynamic as possible, so that it can be deployed to a number of systems without manual changes on each. -- Eric Cables
One last ping on this, to see if anyone has a BIRD specific solution / example. -- Eric Cables On Tue, Jun 10, 2014 at 1:44 PM, Eric Cables <ecables@gmail.com> wrote:
I was hoping someone could assist with defining a local constant for a BGP 'source address' through dynamic means. An example would be 'router id from' where a mask and prefix can be identified to inherit the router ID.
router id from "lo*" 192.168.0.0/24; saddr = <whatever router id inherited>
I was hoping that router id would be an internal symbol, but I don't see it in the 'show symbols ...' output.
Any thoughts? The goal is to make this configuration as dynamic as possible, so that it can be deployed to a number of systems without manual changes on each.
-- Eric Cables
On Tue, Jul 08, 2014 at 12:11:56PM -0700, Eric Cables wrote:
One last ping on this, to see if anyone has a BIRD specific solution / example.
Hi It is not possible in BIRD. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
On Tue, Jun 10, 2014 at 1:44 PM, Eric Cables <ecables@gmail.com> wrote:
Any thoughts? The goal is to make this configuration as dynamic as possible, so that it can be deployed to a number of systems without manual changes on each.
You might want to split your config in multiple files (e.g. a common one and a router specific one) and include them. E.g. each of our bird config files contains a line like this: include "/etc/bird/bird.conf.local"; In that file we specify the router id and a couple of variables used in otherwise common configurations. Best Regards, Freddy
Freddy, That's exactly what I've done, but I was hoping this kind of configuration data could just be defined as a local variable. Perhaps I could define a variable that called a local script, which scraped ifconfig for the data I'm looking for? I haven't done this before, but expect BIRD is capable of such a construct. Has anyone done anything like the above (call a local shell script to populate a variable), or have an example of doing something similar? -- Eric Cables On Wed, Jul 9, 2014 at 5:29 AM, Frederik Kriewitz <frederik@kriewitz.eu> wrote:
On Tue, Jun 10, 2014 at 1:44 PM, Eric Cables <ecables@gmail.com> wrote:
Any thoughts? The goal is to make this configuration as dynamic as possible, so that it can be deployed to a number of systems without manual changes on each.
You might want to split your config in multiple files (e.g. a common one and a router specific one) and include them. E.g. each of our bird config files contains a line like this: include "/etc/bird/bird.conf.local"; In that file we specify the router id and a couple of variables used in otherwise common configurations.
Best Regards, Freddy
participants (3)
-
Eric Cables -
Frederik Kriewitz -
Ondrej Zajicek