Switch to full style
Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems
Post a reply

routing Issue

Sep 28 07 1:21 am

Hello All

I have Wingate 6.22 running with a 10.1.1.x internal network and 2 network cards, using 10.1.1.20 as the wingate machine. I have to intergrate an ANX VPN Tunnel unsing an cisco router and 2 Nokia IPSec Devices. The ANX IPs are in the 166.xxx.xxx.32 range with a subnet mask of 255.255.255.240. I have the cisco router and the nokia devices connected to a 3 comm switch and the switch connected to the internal network. The cisco router is connected to the ANX External Network through a seperate T1 line, i cannot ping any of the 166.xxx.xxx.xxx ip address from the internal network. I would like to be able to use this VPN Tunnel from any computer on the internal network. Any help would be apercated .

Thanks

Lee Boughey

Oct 01 07 10:55 pm

I have tried to keep below simple because I do not totally comprehend your network description - i.e. made the other side of VPN is 192.168.1.0/32 and did not include the nokia's. I am also wary that some VPN's work differently - routing based or virtual adapters that you dial up so the advice below is just for an example - but to help further I would need to see a basic network diagram.



So does it look like this?

3Com Switch ---------- 166.xx.xx.32 <Cisco> T1 to other side of VPN
|
|
|------------------------- 10.1.1.20 <WinGate> x.x.x.x (internet)
|
|
|------------------------- 10.1.1.100 <LAN Client with Gateway to WinGate>


In that scenario the WinGate server will need to first know how to connect to the 166.xx.xx.32 address, because otherwise it will send the packet out its default gateway.

route add 166.xx.xx.32 MASK 255.255.255.255 10.1.1.20


And then it will need to know the subnet of the network at the other side so to route to it via the 166 address - so if the other side was 192.168.1.0/24 then you would need to do this route

route add 192.168.1.0 MASK 255.255.255.0 166.xx.xx.32


The Cisco router may need a route added to it so it can deliver to 10.1.1.x addresses via the 166.xx.xx.32 interface.

*those Windows route commands would need a -p put on the end to make them persistent after reboot.
Post a reply