[Xorp-cvs] XORP cvs commit: xorp/etc/templates xorp/policy

[Andrea Bittau]

CVSROOT:	/usr/local/www/data/cvs
Module name:	xorp
Changes by:	abittau at chum.icir.org	2008-08-06 08:25:26 UTC

XORP CVS repository


Modified files:
	etc/templates policy.tp 
	policy        policy_statement.cc policy_statement.hh 

Log message:
	allow for the "final action" in an unnamed term.  I had to write a little patch
	to get the rtrmgr order right.  I don't know whether it's an issue with the
	rtrmgr's ordering, and if so it should be fixed there - not in my policy patch.
	I don't know enough about the rtrmgr and all that ordering stuff looks kind of
	awkward, at least in use, in policy statements.
	
	The juniper manual is vague on what the final action really is.  It seems to be
	only accept/reject and those sorts of actions (maybe flow control too such as
	next policy).  It doesn't seem to include route modification actions.  Also in
	order documentation it hinted that terms that match, but with no action, take
	the final action - the latest documentation omits this though.  (We don't take
	the final action on terms that match but have no action.)
	
	In practice, i think that the final action is used merely as a final
	catch-allaccept/reject statement and we do provide this functionality.  From the
	juniper manual it's unclear to me whether it is anything more than this.

Revision  Changes                               Path
1.31      +27 -2;  commitid: 8c2b48995ff341a7;  xorp/etc/templates/policy.tp
1.17      +34 -3;  commitid: 8c2b48995ff341a7;  xorp/policy/policy_statement.cc
1.14      +6 -7;  commitid: 8c2b48995ff341a7;   xorp/policy/policy_statement.hh