changing Internet IP

[stobby256]

Hi everyone,

I have a 10.217.x.x network south side of my Wingate... 192.168.0.x North - which faces the internet.

As I am connecting via the VPN, and Some default routers DHCP settings use 192.168.0.x, this would screw up my VPN altogether.

What I need to do is change my 192.168.0.x to a subnet something like 192.168.200.x. Yes I'm OK with doing that, if not I should be taken out and shot.

My question is, that last time I change the north IP address, there appeared to be some static route stuck somewhere that had to be deleted.... I think it was Adrien who dialled in and worked that one out. The result was that any internet connection was slow and email would not connect via IMAP/POP/SMTP at all!

So, what would be the procedure of changing the IP address and clearing any routes in wangate so it all works well?

[damien]

I'm having same (?) problem.
I'm using an VPN connection from another provider and each time this VPN connect, I loose all incoming traffic to wingate (SMTP, WEB SERVER)

What I do is launching a scheduled task (every 5 mn) with the following shell command :

route add 0.0.0.0 mask 0.0.0.0 192.168.1.1 metric 1

So when VPN sets his own routes, they are replaced by this new one.
Outgoing traffic goes through vpn
Incoming traffic is redirect to wingate server

It works... but it would be great if there was a way to fix routes in wingate

Hope it helps

Best regards

[adrien]

Hi

if you're going to replace the default route that gets created by the VPN software, is there instead a setting you can use to not use the default gateway on the VPN?

Or there may be some metric you can set on the VPN virtual adapter to make its default route less preferred to the one it is currently superceding?

regards

Adrien de Croy

[stobby256]

Not using WinGate VPN at all...

Just plain vanilla... but the last time I changed IP between the incoming router and Wingate, Wingate created some odd routes with dual gateways, so reluctant to do it again...

[adrien]

Hi

I'm pretty sure WinGate didn't create those odd routes, they were created by something else.

There are only 2 circumstances where WinGate will create a route into the OS

1. RIP update from some other RIP sender, when WinGate is configured to be a RIP listener (VPN settings).
2. When a client computer connects from another subnet and relied on a default gateway to access that subnet, WinGate will create a subnet route back through the router.

In the second case, it will never create a default route.
in the first case, it may create a default route if that is what is published by the RIP sender.

In your case, I don't believe ether of these scenarios were happening, and I believe the default routes were being created by the OS for some reason. The OS creates routes for a number of reasons:

* ICMP redirect packets
* learned reduced MTU to a path
* DHCP
* R&RAS

We have seen in a number of cases Routing and Ras doing similar things.

Regards

Adrien

[stobby256]

Thanks Adrien!