Routing and RIP

Forum for all technical support and trouble shooting of the WinGate VPN.

Moderator: Qbik Staff

Routing and RIP

Postby ingo » May 31 08 11:31 pm

Hello all. Good luck with the Super 14 Final over there in NZ!

I've got a Server on one end of test network. I've installed your latest version (WinGate6.2.2.1137-USE.EXE) and the Host node VPN network is on a 192.168.0.0 /24 subnet (HOST IP = 192.168.0.55)
I've got another Wingate machine (same version) acting as the VPN client installed on another network (192.168.1.0/24) behind a third party router (VPN CLient = 192.168.1.57)
The port forwarding has been setup on the router on my end and receiving incoming requests ok. When the "client" attempts to connect, the SSL handshake is made and the connection is established. No problems there...

However my routing is not working yet (i.e it's saying not accessible)
What I've tried so far:-

I've got RIP listening running on the client. (Qbik RIPv2 Client 1.doc and the RIPClient.exe)
The router has got OSPF switched on by default (I swopped the router for another one just in case and recreated the rules)
I've added a persistent static route manually on the host (192.168.1.0 MASK 255.255.255.0 192.168.0.10)

My routing table on the host node said the following before i added the above route
"View routes that will be exported when Local Network is selected"
192.168.0.0 255.255.255.0 192.168.0.55 Local network (published forced)
192.168.0.55 255.255.255.255 127.0.0.1 Local Machine (Published)

After I added the route it read.

192.168.0.0 255.255.255.0 192.168.0.55 Local network (published forced)
192.168.0.55 255.255.255.255 127.0.0.1 Local Machine (Published)
192.168.1.0 255.255.255.0 192.168.0.10 Local Network (Published)

The Client node is reporting the following with regards to the Host's published networks
Behind NAT trnaslated
192.168.0.0 /255.255.255.0
192.168.0.55 /255.255.255.255
192.168.1.0 /255.255.255.0 (ignored / local conflict)

Would somebody please tell how stupid I am as I ought to know this but clearly can't fathom this one out

Many thanks in advance

ingo
ingo
 
Posts: 1
Joined: May 31 08 9:59 pm

Re: Routing and RIP

Postby logan » Jun 03 08 11:13 pm

Routing is the most trickiest of subjects regarding VPN, so no-one can blame you for fumbling a bit.

I think your problem is happening mainly because of the custom persistent route you added on the server (192.168.1.0 MASK 255.255.255.0 192.168.0.10). What exactly is located at 192.168.0.10, because it will be receiving all of your VPN traffic because your WinGate VPN joiner network is using the 192.168.1.0 network.

When the computers on your host network try to connect the client network, these packets will be redirected to 192.168.0.10 by WinGate because of the persistent route on the Host computer. When the computers on the joiner network try to connect to the host network, the packets should be reaching the host computers fine, but when the host computers try to send a reply back to the joiner network, again the packets will end up being routed to 192.168.0.10 instead of the remote WinGate VPN.

If the 192.168.1.x route has been added to the WinGate VPN for a reason, I think you may need to change the joiner network to a different IP range. e.g. 192.168.2.x. Or remove the persistent route from the VPN host.
logan
Qbik Staff
 
Posts: 671
Joined: Oct 19 06 2:49 pm
Location: Auckland, New Zealand


Return to WinGate VPN

Who is online

Users browsing this forum: No registered users and 4 guests

cron