Hello, I migrated some of our routers to Bird 1.3.3 yesterday and noticed that I was getting a syntax error in some of our previously working bird 1.3.2 configurations. Seems the word "external" is now a reserved word in 1.3.3? /etc/bird.conf <snip> 6 : 7 : # Configure Additional Routing Tables 8 : table internal; 9 : table external; 10: </snip> The configuration above seems to work fine in 1.3.2, and generates a syntax error on line 9 in bird 1.3.3. Just wanted to make sure this was expected behavior. <snip> birdc show symbols |grep -ci external 0 </snip> Thanks again to all the developers making bird such a great piece of software. -Mike -- Michael Vallaly <bird@nolatency.com>
On 13.9.2011 16:39, Michael Vallaly wrote:
Hello,
Hi!
I migrated some of our routers to Bird 1.3.3 yesterday and noticed that I was getting a syntax error in some of our previously working bird 1.3.2 configurations.
Seems the word "external" is now a reserved word in 1.3.3?
/etc/bird.conf <snip> 6 : 7 : # Configure Additional Routing Tables 8 : table internal; 9 : table external; 10: </snip>
The configuration above seems to work fine in 1.3.2, and generates a syntax error on line 9 in bird 1.3.3.
Just wanted to make sure this was expected behavior.
Yes, it was added as an option to the OSPF configuration. Look at http://bird.network.cz/?get_doc&f=bird-6.html#ss6.5 We are sorry for that. :-( Ondrej
<snip> birdc show symbols |grep -ci external 0 </snip>
Thanks again to all the developers making bird such a great piece of software.
-Mike
On Tue, Sep 13, 2011 at 09:39:04AM -0500, Michael Vallaly wrote:
Hello,
I migrated some of our routers to Bird 1.3.3 yesterday and noticed that I was getting a syntax error in some of our previously working bird 1.3.2 configurations.
Seems the word "external" is now a reserved word in 1.3.3?
/etc/bird.conf <snip> 6 : 7 : # Configure Additional Routing Tables 8 : table internal; 9 : table external; 10: </snip>
The configuration above seems to work fine in 1.3.2, and generates a syntax error on line 9 in bird 1.3.3.
Just wanted to make sure this was expected behavior.
Yes, although we generally try to not break working configs in minor versions, the way how BIRD config parser is done causes that any new config option may collide with user defined names like variables or table/filter/protocol names. -- 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."
participants (3)
-
Michael Vallaly -
Ondrej Filip -
Ondrej Zajicek