[7.080] HTTP Proxy - Time events do not work correctly [CONFIRMED]

[Gert]

In version 7.101 this issue is still not solved.
Any ideas when it will be done ?

thanks.

[svens]

Hi,

Originally Posted by Gert

In version 7.101 this issue is still not solved.
Any ideas when it will be done ?

It's scheduled for the 7.102 release.

Cheers,

Sven.

[sengsational]

Can someone confirm that the "Sunday Time Events" is a current bug? Or have I got it configured wrong? The following should block access at this time (Sunday), but it does not:

1) Time Event includes "now" (called "Sunday Evening").

2) Filter Assignment using the "Sunday Evening" Time Event and a "Block All" Filter Action.

3) Single Proxy Profile with the Filter Assignment, above.

If, in the Filter Assignment, I put "<<Always>>" instead of "Sunday Evening", the browser correctly displays the "content not available" message. But like I said, if I used my defined Time Event, it allows content. I even expanded my Time Event to include all of Sunday and Monday, and it still didn't block.

So in 7.102 I can expect this to work?

--Dale--

[RFCat_vk]

Hi,
as far as I can tell Sunday night block works fine.

You can't just block Sunday you need to setup allow profiles for the other days of the week and also modify the default profile in http.

I will admit I don't actually have any block profiles, I only have allow profiles and allow the block time slots to fall through to the default profile. I know this works because I made a mistake in my new configuration and left a 15 minute time slot between two allow profiles and the user wasn't very happy.

Ian M

[sengsational]

Originally Posted by RFCat_vk

as far as I can tell Sunday night block works fine.

Thanks, Ian, for the reply. I'm glad you mentioned this because I would hate to have waited for a new release only to find it was a configuration issue all along!

Originally Posted by RFCat_vk

You can't just block Sunday you need to setup allow profiles for the other days of the week

Is this a work-around, or is it the way it's supposed to be? I'm not at the machine right now, so can't get specific, but it sure seems like it should work. Like I said in my earlier post, if I change just one thing, from a "timed event" to "always", it begins blocking correctly.

Yeah, so I guess I'll have to try setting up "allow profiles" instead of the seemingly more straight-forward block thing that I've tried. When I get home, though, I'm going to take some screen shots and maybe I can learn why my original config doesn't work.

Originally Posted by RFCat_vk

and also modify the default profile in http.

If by this you mean taking action so that users must use the proxy, as opposed to going straight to the Internet, then yes, I did that. There was a rule for web browsing from the internal network that I changed the rule to always drop. It changed from a straight green arrow to a red arrow that pointed down at the end.

[sengsational]

I just went through a little test using the "obvious" configuration scheme and everything worked exactly as I expected (today, on a Monday).

[sengsational]

(Continued from previous post: last two images)

[RFCat_vk]

Hi,
what I meant with the default profile is that the "default" is the http page. If you have a look at that page that is your default block/allow control for your not allowed functions in your specific profiles.

When v7 was first released I spent a lot of time manually configuring the equivalent functions from v6 in v7 and could not understand why they didn't work. Some where because there was a fault on Sunday, others were because I didn't understand the new approach by Astaro.

You only need an allow for the time slots, you might add a your generic fall through, but in the end they all end up at the ASG default. If you haven't configured the ASG default then all your other profiles are in vain.

I use standard mode without user authentication at this stage. I have PF blocks for most standard ports to ensure proxy use. I also have timed managed PF rules as well as the HTTP proxies.

Pity there aren't more time managed functions eg for the socks proxy and the helpers. Maybe I am being a bit overly cautious.

Ian M

[Gert]

The Sunday problem is solved in version 7.102.

The HTTP proxy filters are working now, also on a sunday.
Thanks Astaro

Gert