[Xorp-hackers] HEADS UP: XORP configuration syntax changes

[Pavlin Radoslavov]

All,

As of today, there are few changes in the XORP configuration
syntax in XORP-current, and those changes will be in the forthcoming
XORP-1.1 release as well.

The changes are:

 * All "enabled: true/false" XORP configuration flags are now
   renamed to "disable: false/true".
   Furthermore, now all of them have default value of "false".
   In other words, if a configuration section doesn't contain
   the "disable" flag, it is implicitly enabled.
   [The reason for this renaming is for better consistency with the
   configuration of other router vendors.]

   Therefore, if you have "enabled: true" in your configuration, you
   should either change it to "disable: false" or you you can simply
   delete it (because it is same as the default).

   However, if you have "enabled: false", then you should change it
   it to "disable: true".
	
 * Change the syntax for configuring the IPv4/IPv6 forwarding
   (for consistency with the above renaming):
	
   OLD:
   fea {
       enable-unicast-forwarding4: true
       enable-unicast-forwarding6: true
   }
	
   NEW:
   fea {
       unicast-forwarding4 {
           disable: false
       }

       unicast-forwarding6 {
           disable: false
       }
   }

   OR JUST (if you want to enable the IPv4 and IPv6 forwarding):

   fea {
       unicast-forwarding4 {
       }

       unicast-forwarding6 {
       }
   }


Now the old syntax is marked as %deprecated in the rtrmgr templates,
so the appropriate error message is printed on startup if someone
tries to use a configuration file with the old syntax.


Please let us know if you find any problems because of the above
change.

Thanks,
The XORP Team