Wingate with DSL modem

[sretlaw]

Hi,

I have been successfully using Wingate 5.2.3 with a cable modem for quite some time. However, DSL is a lot cheaper, so I am trying to switch from cable internet access to DSL. Apparently I have lost some grey matter since I installed Wingate a while back. Turning 40 sucks.

The main difference I see between the two services, is that my DSL modem has an IP address of 192.168.0.1 (when viewed from the Wingate machine) whereas the cable modem did not have an IP address. Also, the DSL modem gets assigned an IP address ffom my ISP that the world sees (currently something like 65.12.138.190).

I have the standard 2 NIC setup: one going to the DSL modem (previously the cable modem), and the other for my internal network. My Wingate machine has an IP address of 192.168.0.6.

When I go to the Gatekeeper on the Wingate machine, I see the IP addresses 127.0.0.1 and 192.168.0.6 in the "bound" area of the Bindings tab, and the IP address 65.12.138.190 under the "available" area. This is true under the Services area (FTP Proxy, WWW Proxy, etc.) and the System area (DHCP, Winsock, etc.).

The Wingate firewall blocks all attempts to connect to the Internet through the DSL modem, with messages like, "The firewall has blocked a connection attempt to 65.12.138.190 by [some internet IP address]....".

So, what is the easiest way to get the DSL modem working? Do I simply double click on the available IP address (65.12.138.190) to move it up to the bound area? And should I do this by Service, or System, or both?

Thanks in advance for your help.

[adrien]

Hi

What is the IP address of the other network card on your WinGate machine?

By default, WinGate willl consider the IP of 192.168.0.1 to be an internal adapter. I am picking that your other adapter has a private IP address as well.

WinGate will only NAT from an internal adapter to an external one (you can change this under Options->Advanced->Network Interfaces in WinGate 5.x, or in the Network Connections tab in WinGate 6.0). Also, make sure that both adapters don't both have IP addresses in the same subnet, i.e. if they are both 192.168.0.x then there will be a routing problem. It may be easier to renumber the IP address of the network interface on the DSL modem and the WinGate machine's interface connected to that, than to renumber the rest of your network.

Also - the DSL modem must have a NAT built-in already, so another option would be to get WinGate to simply route between the two subnets. This would require both interfaces on the WinGate machine to be deemed internal/trusted, and a route to exist on the DSL modem to point back to the other subnet via the WinGate machine.

Adrien

[sretlaw]

The adapter connecting to the DSL modem is:

IP: 192.168.1.64
Gateway: 192.168.0.1
Subnet: 255.255.0.0
Assigned by DHCP

The adapter to my LAN is:

IP: 192.168.0.6
Gateway: 255.255.255.0

I went into the Extended Networking and enabled support for multiple subnets, but still not working.

[trialtester2999]

This is just a follow up on the problem with the PPPOE adapter which seem to not support Wingate. Is there a workaround on this issue?

[MattP]

Hi Sretlaw,

It looks like your adapter addresses are a little messed up. Because you have your LAN set to the 192.168.0* range you'll want to keep that the same.

You should change the internal IP address of the DSL modem to a different subnet, the external NIC of your WinGate server is already on the .1 subnet so you may as well stick with this.

So you should have the following:
DSL Modem:
external IP address-assigned by ISP
internal IP address-192.168.1.1

WinGate server external NIC(to the DSL modem)
IP address-192.168.1.64
Subnet mask-255.255.255.0
default gateway-192.168.1.1

WinGate server internal NIC(to the LAN)
IP address-192.168.06
subnet mask-255.255.255.0
default gateway-(left blank)

If you go to options>advanced and select the network interfaces tab you should set the external interface (192.168.1.64) to public yes trusted no

Regards,

Matt

[sretlaw]

Hi Matt,

Unfortunately, I can't change the internal IP address of the modem from 192.168.0.1, and I can't change the subnet mask either.

I can change any settings on the LAN I need to. Any guidance you can give me there to get it all working would be greatly appreciated.

Thanks.

[genie]

You just change your LAN address to soemthing like 192.168.1.x - that should be enough to resolve the problem.

[MattP]

Hi,

I think Genie actually meant 192.168.2.* or something else, anything but the 192.168.1.* subnet that the connection to the modem is on.

Matt

[sretlaw]

Matt,

I modified all of my LAN IP addresses to the 192.168.2.* format and still can't get to the Internet, except from the Wingate machine.

The firewall in Wingate keeps blocking trafic from the DSL modem (192.168.0.1) to the WinGate server external NIC to the DSL modem (192.168.1.64).

I appreciate all of your help. Any final suggestions before I cancel the DSL service?

[MattP]

Hi,

Can you go to options>advanced and check that your internal NIC is showing as public no trusted yes?

Can you clarify your network settings now? As I understand it your LAN is configured on the 192.168.2.* subnet, then your WinGate server connects to the DSL modem with an IP address of 192.168.0.1.

There should not be any problems with this. Are you still seeing firewall hits, are any of the hits coming from your internal address range? If you go the bindings what do you see now?

Can you verify that support for multiple subnets is enabled in the Extended Networking menu?

Thanks,

Matt

[sretlaw]

Hi Matt,

I went to the advanced options and tried both NIC cards with all options (rebooting between changes).

Yes, the LAN had the 192.168.2.* subnet and the DSL modem 192.168.0.1.

Multiple subnets were enabled. Bindings look ok.

I kept seeing the firewall blocking all traffic from the DSL modem (192.168.0.1).

Finally, I just went out and got a cable/DSL router, modified PC's on the LAN to use DHCP with the router, disabled all services in Wingate, and rebooted eveything. It worked.

I'm still not sure why Wingate was having problems.

Thanks for your help.