-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/03/15 00:02, Ondrej Filip wrote:
> Your problem is cause by the fact that definition of unnamed
> protocol from template is not supported. I added this option to
> the git repository today. To solve this on 1.4.5 please use:
>
> protocol bgp bgp_1 from peers {
Hi Ondrej,
I figured that out too :) I'm generating my config from a template, so
I just made the template generate names like bgp1, bgp2 ...
However, when looking at the output of "birdcl show protocols", I just
see "bgp1", "bgp2" and so on. So I then edited my template to generate
config like this:
protocol bgp '<peeraddr>/AS<peerasn>' from mytemplate {
...
}
Now when I run "birdcl show protocols" I can see which peer is
connected, and so on.
By the way, the documentation about using single quotes shows an
example using triple quotes. So I first used triple quotes, and it
failed with a syntax error. Perhaps you should change the example and
only use single quotes.
Regards,
Anand
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
iEYEARECAAYFAlT+L5MACgkQi+U8Q0SwlCtwRgCghTm0toM4m7P4/4lbYJdwdq8N
daIAoIcvrQjDWTdbtDJ4lWTrGbAh3LKG
=nN9f
-----END PGP SIGNATURE-----
