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