Using Wingate as a proxy over the Internet

[alemos]

I recently tried to open up the www proxy to people on the Internet (protected by authentication, of course, and restricted to certain IPs) but although the connection is detected on the Gatekeeper window (I see the IP and connection coming in, but then the request is just "http://" and nothing else.

Any clues? Why doesn't this work.

On another note, Wingate does not detect the connection to the internet. I have to allow connections on ALL INTERFACES and then it works. If I try to bind, the public IP interface does not work.

[neil]

Oops. This is indeed an issue, i'm not sure when we broke java auth over an external interface, but it works in 4.5.2 but not in 5.2.3. We will fix this for the next version, which hopefully wont be too far away.

As for your second point, how is your external interface set up? Do you have a static IP? What sort of connection is it? A USB interface? Is it a permanent connection, or do you have to dial? If WinGate starts before this interface (assuming it isn't a dail up modem) then WinGate will not see it.

Regards

Neil

[alemos]

Oops. This is indeed an issue, i'm not sure when we broke java auth over an external interface, but it works in 4.5.2 but not in 5.2.3. We will fix this for the next version, which hopefully wont be too far away.

Okay! I'll wait for the new version then.

As for your second point, how is your external interface set up? Do you have a static IP? What sort of connection is it? A USB interface? Is it a permanent connection, or do you have to dial? If WinGate starts before this interface (assuming it isn't a dail up modem) then WinGate will not see it.

The external connection is an ADSL connection. The modem connects to a second LAN Card and the IP is not static, it's dynamic. It is necessary to dial a connection (although no real dialing is done) and authenticate through a website, then you're online. Usually Wingate starts up before this connection, but I have tried stopping the WG engine and then connecting and only then starting up the WG engine again, but the connection still does not show up in the list of connections in any of the bindings tabs. It only shows the loopback 127.0.0.1, the other lan card's fixed local IP address 192.168.0.1 and the second LAN card's address before it connects 169.254.20.120. This address changes to a public address after the DSL connection is established, but I can't get Wingate to see this.

Thanks for your help!

Regards,

Aécio