Time limit based on destination

[batwater]

I would like to restrict the amount of time my kids spend on World of Warcraft by setting a time limit on connections from certain machines (IP addresses) to certain server IP addreses. Can this be done, if so, how?

I tried scanning the forums and didn't get a hit.

Thanks

Ben

[ChrisH]

In order for WG to record how long a user has been online it has to be setup so that at least an assumption based on machine name or machine IP is made to a user in the WG database. Once WG knows who is connected (by authentication level in policies) then it will track data about that user. This data is shown on the Accounting Tab of the specified user and one of the parameters recorded is Seconds on line. You can use this parameter as a criteria in policies to limit the amount of time online -which I think is what you want to do. The trick becomes on how to apply it.

So at a minimum you have to assume users and in your case know which Warcraft server IP's (or perhaps port numbers may be easier) you don't want those users connecting after the seconds online is greater than xxxxxxx. Where to apply the policies would depend on how your users(kids) connect through WG- NAT or WGIC(WRP service). If you don't have the WGIC installed on the user machines it is NAT which is administered in the Extended Networking tab on the Systems page in GateKeeper. Finally you have to set up a new scheduler event that resets the users accounts every day (if that is your wish) so that the user can start over again.

As another note ALL traffic whether it is email, WWW browsing, WoW etc is recorded as seconds on line for that user. So you have to be sure that your WoW policies don't interfere with the other online activities. That may be the hard part.

[Pascal]

As another note ALL traffic whether it is email, WWW browsing, WoW etc is recorded as seconds on line for that user. So you have to be sure that your WoW policies don't interfere with the other online activities. That may be the hard part.

I think that might be accomplished by using a double policy type setup.

Client1:
Filter1 -
Criterion1 - This right is granted if Seconds on line < x
Criterion2 - This right is granted if port is WoW port

Filter2
Criterion1 - This right is granted if port is not WoW port

Client2:
(Same as above)

That way only Wow will be affected by seconds online, while all other traffic will go through normally. I think - I'd need to test in the lab to make 100% sure.