> Why isn't any a valid specification? I am running 2.1 > > [POLICIES] WARNING: [ID:6/Name:Default Outbound]: - Source 'any' is > not a valid specification
2.1 trunk is in a state of flux at present due to the caching additions, I would not suggest using it right now, unless of course you want to see if caching has any affect on load, and your policies don't change often :D I'm using trunk in a production environment to test out the effect caching has, doesn't appear like it has much of an effect though, so in future 2.1 releases it may be optional with appropriate documentation of when and when not to enable it. "any" should still work though regardless if its a policy member, I can't see how it can't be working .... are you using it as a group member?, if so its not supported as a group member, afaik in that context its redundant. Please paste more logs. Regards Nigel _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
