Using wingate as proxy server

[boris]

Hi there,
I am knew to Wingate, just installed in yesterday so this might be a newbie question however I have research this issue without results.

I need to use Wingate solely as a web proxy, I have one or two location outside my network who need to access the internet through a proxy. This works fine in Wingate 6 from get-go but there is this annoying fact of all the others out there who would like to exploit this service I am setting up:( This of course eats up my bandwidth and download and puts extra load on my server. To begin with I tried to identify the sources and just put them on ban list but the numbers of ip addresses that would require to be on this list is way to long. So I decided that the best way would be to ban all other ip addresses part from which need to access the proxy. Couldn't find a way to do that so I disabled the guest account so no none else could use the proxy server.

That work fine at least in the activity window I saw all the deny the server was handling but it is massive so it actually put strain on the Wingate console and it got unresponsive at times. So I looked around and research this issue on the internet but found no solution. So I decided to post here to see if anyone knows how to allow only f.e. assumed user to use the web proxy server in Wingate and discard/ban all other requests so the wont put strain on my resources?

Thanks
Eddie.

[adrien]

Hi

if you edit the policy for the WWW proxy that is bound to the external interface,

* click new
* select everyone, must be authenticated (or assumed)
* click ok
* default policy : are ignored
* go to general tab, enable authentication options
* click ok.

That will require remote users to be authenticated (or assumed if you chose that option). Authentication can be better, since then it's under user control (they don't have to wait for you to add their IP).

Adrien