VPN with same subnet 1

[strych9]

I have a VPN setup for my home when i am away i VPN to take care of things. Recently i was somewhere that had the same subnet as i did. And i could not see my network.

My IPs are 192.168.0.x and the network i was on was 192.168.0.x the 2 IPs i had were 192.168.0.3 and 192.168.0.9

every request i made to my home network fail. How can i fix this.

 

[substitute]

I've never been able to get round this one. There are several IP problems that would stop messages getting through.

As a support engineer I have to connect to loads of different systems routinely. I deal with the problem by making my home network subnet address so weird that I never get a clash. In my experience most systems use the 192.168.x.x address range, generally 192.168.1.x. Lately some companies have recognised this and supply equipment with a default of 192.168.0.x or 192.168.2.x. A few sysadmins with grandiose plans choose 172.(16-31).x.x for a bigger network. Nearly everyone uses a subnet mask of 255.255.255.0.

For my home system I chose random numbers in 10.x.x.x, like 10.136.217.x. with a subnet mask of 255.255.255.0 The probability of a clash is microscopic.

Ian.

 

[jaymcgraw]

I've run into this before and have been able to get around it by creating a route in Windows after connecting:

route add 192.168.0.0 mask 255.255.255.0 192.168.0.9 metric 1

(192.168.0.9 being the VPN interface IP address)

This tells Windows to route all traffic (METRIC 1 is lowest cost) for the 192.168.0.0/24 network through the 192.168.0.9 interface. By adding this route, however, you lose the ability to communicate with devices on your LAN. It works with our VPN anyway.

 

[dberg35]

Something else is remote desktop, you could use that to gain access while away.