Warning Potential Route Subnet Conflict

[docdom]

Untangle was suggested to me for handling point to point VPN connections between my main office and satelite office.

I have Untangle 9.2.1 installed on the following hardwire:

Intel E6600
Asus P5B Deluxe
2x1GB G.Skill DDR2-800
Seagate 320GB 7200.10 HD
External Interface - Intel Gigabit CT Desktop Adapter
Internal Interface - Onboard Marvell Gigabit LAN
Setup in Bridge Mode

I have Untangle installed and up and running at my home to test and learn before I deploy this at my main office. The big difference between my house and my main office is I have a VerizonFIOS internet connection at the house with a dynamic IP and have to use the ActionTec supplied router since I have TV with my FIOS package.

I have 1194 and 443 forwarded to the Untangle IP as well as a static route from the VPN Pool (172.16.0.0) to the Untangle Box. I also have DynDNS running on my home server and I use my dyndns address to connect to my Untangle VPN since the IP changes.

I am able to connect to my VPN no problem as you can see in the below screenshot but cannot see any hosts on my home network once connected. I am new to VPN's and have my company setup using RDP on a Server 2008 machine for many years with not issue to run our company database (property management) software.

I have alot of complaints about having to connect to RDP just to use the database so I would like to setup a site to site or client to site VPN connection then map a network drive once connected to our main database server at our main office with the database software installed on the remote client that accesses the database through the mapped drive. (not sure if this is the best way to do it)

Now, when I connect to the VPN I cannot see any resources/hosts on my home network and I see this message in the VPN Status Log: Thu May 17 17:29:15 2012 WARNING: potential route subnet conflict between local LAN [192.168.1.0/255.255.255.0] and remote VPN [192.168.1.0/255.255.255.0]
Also you can see in the second screenshot below that Windows Network and Sharing recognizes the connection as an Unidentified Connection Public

Is this the reason why I cant see any resources on my home network when connecting to it through the VPN client remotely?

I do have the same Gateway IP of 192.168.1.1 on both the remote network router and my home network router.

Any help anyone could provide my I would greatly appreciate it. If I can get this working at my home in test phase then my company will purchase the pay version of Untangle to support roughly 20 VPN connections daily. Also, I have a COMCAST business class 25/10 static IP internet connection at both my main offfice and satelite office so I will use Untangle as the router directly from the Comcast modem (much easier to setup then my home FIOS dynamic IP setup).

Thank you in advance

OpenVPN Client Connection Log



Windows Network & Sharing

[dmorris]

stop spamming the forums. If you need 5 posts. Post them here.

192.168.1.* can not be in two places. You need to use something in one place, and something else in another.

[docdom]

Sorry, was trying to get the screenshots here for you to better help me. Thanks for the heads up.

[docdom]

Trying to get 5 posts to post the screenshot

[docdom]

And a few of those posts are legitimate, I thought that information was very helpful

[docdom]

Thanks again for your help

[dmorris]

You windows machine is refusing to add a route for 192.168.1.* through the VPN because this would likely make the local network (and possibly your own gateway) unreachable because its the same network. You'll need to use another subnet.

[docdom]

So changing one of the 2 networks two this: 192.168.168.X should work??

I pretty much figured that but am a bit confused on how to fix this? Any more detailed information? Go into my router at either home or remote location and change DHCP address distribution pool to give out IP's starting with 192.168.168.x ??

Thank you for the help

[dmorris]

Yes, You'll need to reconfigure everything on one network. The router and any statically configured hosts.
If its an untangle, just change the internal IP, and the DHCP settings, and reboot the hosts (or just renew their leases)

Yep, it sucks, but everybody learns this painful lesson at some point.

[docdom]

Thank you for the help, I pretty much figured this but wanted to confirm before making the changes.

Will test now and report back with how I made out.

Sent from my HTC EVO 4G using Tapatalk 2