ok, that helps yes!
Thanks, Arthur.
Strangely: in the gui "all" was already selected, but I selected it
again, and it ended up in the config file.
Thanks for great support!
On 29-9-2015 20:43, Louis Munro wrote:
Good point.
Try defining that to one of either all or any.
Since there is only one condition it should not matter which you choose.
Regards,
--
Louis Munro
[email protected] <mailto:[email protected]> :: www.inverse.ca
<http://www.inverse.ca>
+1.514.447.4918 x125 :: +1 (866) 353-6153 x125
Inverse inc. :: Leaders behind SOGo (www.sogo.nu <http://www.sogo.nu>)
and PacketFence (www.packetfence.org <http://www.packetfence.org>)
On Sep 29, 2015, at 14:21 , Arthur Emerson <[email protected]
<mailto:[email protected]>> wrote:
Stupid questions. Our PF 4.x install (configured by GUI) seems to only
use "match=all" for catch-all rules. Where conditions are specified,
it has "match=any". Does the domain_admin rule above need "match=any"
or is it optional with only one condition configured? Is "match=all"
with no conditions making the domain_users rule into a catch-all?
Just curious, since I have never really worked with the config files
in PF 4.x.
------------------------------------------------------------------------------
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
------------------------------------------------------------------------------
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
