WinGate Configuration
Apr 08 14 10:10 am
Hello,
I'm new to WinGate and have a quick question.
I'm looking to forward non-work related traffic (Facebook, Spotify, YouTube, etc) to our "Comcast" network. Our "Work" network is running off a T1 and, as you can imagine, a T1 with 100 employees working and using Spotify can really bog down a T1. I have an old Dell server with two NICs (one connected to "ComCast" and the other to "Work"). Is there any way for me to utilize WinGate as a middle man, redirecting non-work related traffic to the "Comcast" network, while all other traffic will go through "Work".
Please let me know if I'm going about this all wrong or if any additional information is needed.
I really appreciate your help.
Thank you,
Robert
I'm new to WinGate and have a quick question.
I'm looking to forward non-work related traffic (Facebook, Spotify, YouTube, etc) to our "Comcast" network. Our "Work" network is running off a T1 and, as you can imagine, a T1 with 100 employees working and using Spotify can really bog down a T1. I have an old Dell server with two NICs (one connected to "ComCast" and the other to "Work"). Is there any way for me to utilize WinGate as a middle man, redirecting non-work related traffic to the "Comcast" network, while all other traffic will go through "Work".
Please let me know if I'm going about this all wrong or if any additional information is needed.
I really appreciate your help.
Thank you,
Robert
Re: WinGate Configuration
Apr 09 14 9:33 am
Hi Robert,
You could try a flow-chart policy that checks the request against a list of URLs. A match on the list would then select the ComCast gateway, all other connections would go out through the Work gateway. So you'd end up with something like this where the "select ComCast gateway" is an expression evaluator that specifies "Session.Gateway = 192.168.1.1" or whatever your ComCast gateway IP address is:
You could try a flow-chart policy that checks the request against a list of URLs. A match on the list would then select the ComCast gateway, all other connections would go out through the Work gateway. So you'd end up with something like this where the "select ComCast gateway" is an expression evaluator that specifies "Session.Gateway = 192.168.1.1" or whatever your ComCast gateway IP address is:
- gateway selection policy.png (95.35 KiB) Viewed 4070 times
Re: WinGate Configuration
Apr 10 14 7:38 am
Thank you Matt!
I was wondering if you, or anyone else, may have seen this error?
There was an error processing the event WWW Proxy Server: ProxyRequest, please contact your system administrator.
Error source: Policy->Gateway Select->Comcast Gateway
Error description: unexpected token literal: 11.1 expected a member identifier
I was wondering if you, or anyone else, may have seen this error?
There was an error processing the event WWW Proxy Server: ProxyRequest, please contact your system administrator.
Error source: Policy->Gateway Select->Comcast Gateway
Error description: unexpected token literal: 11.1 expected a member identifier
Re: WinGate Configuration
Apr 10 14 12:41 pm
That sounds like a problem with what you've got in the policy, would you like to do a remote session and we can go over it together? If so, send an email to support@wingate.com and we'll organise a time to have a look with you.
Matt
Matt
Re: WinGate Configuration
Apr 10 14 2:13 pm
you will need double quotes around the IP address
e.g.
Session.Gateway = "192.168.0.1"
not
Session.Gateway = 192.168.0.1
That tells it it's a literal (data) vs a variable called 192, which is an object which has a member called 168, which is an object with a member called 0 etc.
Regards
Adrien
e.g.
Session.Gateway = "192.168.0.1"
not
Session.Gateway = 192.168.0.1
That tells it it's a literal (data) vs a variable called 192, which is an object which has a member called 168, which is an object with a member called 0 etc.
Regards
Adrien