Allow Public IP

[pisidoubleu]

Hi there...
I just want to ask..before using Gatekeeper software, our network use other proxy...but by using that other proxy, the network allow computer with public address in our LAN to still go through the network...but after installing Gatekeeper with the default setting, those with public IP can no longer access the Net...how is this possible ? Do we need to create another group with IP masking on ?
Thanks in advance.

[pisidoubleu]

hi...im a newbie here...if my question has been answer before, or its just a simple question too follish to ask, you could always help guide me to the manual...i try to look for it in wingate documentation, white paper, user guide, FAQ,online tutorial, etc etc etc, but couldn't find anything mentioning about this topic...
thanks

[genie]

How are these clients connecting - through Wingate proxies or NAT?
Can you send me your Wingate machine routing table, please?

[pisidoubleu]

nope...no NAT...just simply plain proxy...hope this would help...

...thanks

[genie]

Then you need to add those internal public IPs on your Wingate machine routing table - otherwise routing would send packets, destined to these machine, through your default gateway.

[pisidoubleu]

where do i have to add it sir ?...on the wwwproxy ? or is there is any guide on how to add this public IPs on the net that I could refer to ? thanks

[genie]

No, you can do it from the command line on your wingate machine, like that:

Let's suppose you client public IP address is x.x.x.x. Now, in the command line window you type:

route -p add x.x.x.x mask 255.255.255.255 192.168.1.4

if you want to delete this route you type:

route delete x.x.x.x

[pisidoubleu]

ok I havent ask my Net Admin to try this yet...but just curious...by doing this, am I still bound by the restriction set on da proxy ( for example set on the proxy, you cannot use P2P downloading software like Limewire or torrent, because of the port is closed ) ? or is this configuration would just let my PC to go through the network like there was no proxy at all ?
thanks

[genie]

Well, it depends. If your client is forced to use proxy because there is no other way through to the outside worlds, then the answer is yes, there are still the restrictions - only proxies would be able to access outside hosts on behalf of the clients. However, if your client computers have other way to go through, then it won't stop them.

[pisidoubleu]

oh...ok here's the situation...we are given certain range of fixed(public IP) by the ISP...for example (214.203.15.1-214.203.15.110)...and previously i have been using the manually configured ip of 214.203.12.101...whereas the other PC on the network have been using the private IP assign by DHCP 192.168.x.x...

router (214.203.15.1) <- server(214.203.15.2) <-mypc(214.203.15.101)
<-network(192.168.x.x)

this is the previous setting with software FreeProxy installed on the server, with my gateway of course 214.203.15.1...

ip: 214.203.15.101
subnet: 255.255.255.0
gateway: 214.203.15.1

but after installing Gatekeeper to replace the FreeProxy, my PC can no longer access the Net with the same setting, how could that be possible ? that's what Im trying to solve here. current setting I believe would be like this right ?:

router (214.203.15.1) <- server(214.203.15.4) <-mypc(192.168.x.x)

which shows that I have to use the private address like the others...

[genie]

Ok, a couple of questions:

You have .101 gateway through .1 machine - it means that the server does not control your PC traffic and does not route it. If you want to use proxy, you have to make sure that there is a route back from .1 gateway which does not go through .2 machine or .2 has a route to .101.

As an alternative you can configure Wingate to see .101 machine as a DMZ machine.

[pisidoubleu]

ok, I have asked my Net Admin to add those command line that you've suggest, but we add those command line directly in the command prompt of the Gatekeeer machine, with my network setting of
ip:214.203.15.101
subnet:255.255.255.0
gateway:214.203.15.1
is this setting correct ? or is the command should be aded through other way on the Gatekeeper setting (routing table) ?
thanks

[genie]

Yeap, that's pretty much it - but, mind you, this will allow your client machine to use Wingate proxy but in order to pump all traffic from the client machine through your Wingate server you have to set the default route on the client machine pointing to the Wingate server (.2).

[pisidoubleu]

ok, sorry for being a network naive i am, but where or how is it i am going to do that ?

you have to set the default route on the client machine pointing to the Wingate server (.2).

you mean by changing my gateway from .1 to .2 ?
thanks

[genie]

Aye, that's pretty much what I mean. It will change your public IP client traffic, though.

[pisidoubleu]

hi, it's me again, ok...here's what we've already did..
server with Gatekeeper:
(to the router)
ip:214.203.15.4
subnet:255.255.255.0
gateway:214.203.15.1
(internal)
ip:192.168.1.4
gateway:none

mypc:
ip:214.203.15.101
subnet:255.255.255.0
gateway:214.203.15.4

all this with the command of:
route -p add x.x.x.x mask 255.255.255.255 192.168.1.4
already added in the Gatekeeper machine via command prompt

and what about the setting on the IE ?

I've already try both with the Use a proxy server check and unchecked...but still to no avail..anything else I miss ?
Thanks.