Hi William, time based access using PF rules is relatively straight forward.
Time based http access requires considerable thought. It is a 4 stage process 1/. default access 2/. filter actions 3/. filter profiles 4/. filter assignments.
If you get the http proxy setup wrong you can and more than likely will drive your CPU to 100%.
Traps are time slots are not to overlap eg 1000-1100,1100-1200 overlap, you need 1000-1059, 1100-1159. You can't go 2330-0100, it must be 2330-2359, 0000-0100 Further traps are in setting up the profiles etc, they are fall through. It is not as easy as the v6 version.
I am still trying to prepare my answer to Gert's request for details to a thread I started a couple of weeks ago. I have my work laptop home which has a lot of capture tools on it so I expect to be able to complete the thread tonight.
Hi William, time based access using PF rules is relatively straight forward.
Time based http access requires considerable thought. It is a 4 stage process 1/. default access 2/. filter actions 3/. filter profiles 4/. filter assignments.
If you get the http proxy setup wrong you can and more than likely will drive your CPU to 100%.
Traps are time slots are not to overlap eg 1000-1100,1100-1200 overlap, you need 1000-1059, 1100-1159. You can't go 2330-0100, it must be 2330-2359, 0000-0100 Further traps are in setting up the profiles etc, they are fall through. It is not as easy as the v6 version.
I am still trying to prepare my answer to Gert's request for details to a thread I started a couple of weeks ago. I have my work laptop home which has a lot of capture tools on it so I expect to be able to complete the thread tonight.
