On 03/23/2013 05:54 PM, Mr Dash Four wrote: > >>> Another suggestion: for all table IDs shorewall uses provider numbers. >>> Can you change that to provider names instead? >>> >> >> That would break if KEEP_RT_TABLES=Yes were set. >> > Could you adopt a more flexible approach then and use names when > KEEP_RT_TABLES=No and define numbers when that option is Yes? >
I'm not too keen on that idea. Using numbers is foolproof; it doesn't
rely on /etc/iproute2/rt_tables at all. Plus, to avoid having to
recover the original /etc/iproute2/rt_tables file in the event of
a startup failure, the generated script writes that file *after* it has
started all providers.
I would consider a new option, however:
USE_RT_NAMES=[Yes|No]
When set to 'Yes', the emitted script will use routing table
(provider) names rather than numbers in the generated shell
script. When set to 'No', the default, table numbers will be
used.
Setting this option to 'Yes' requires that KEEP_RT_TABLES=Yes.
That means that you are responsible for ensuring that all
necessary entries are present in /etc/iproute2/rt_tables.
-Tom
--
Tom Eastep \ When I die, I want to go like my Grandfather who
Shoreline, \ died peacefully in his sleep. Not screaming like
Washington, USA \ all of the passengers in his car
http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
