- Apr 4, 2014
- 640
- 0
- 0
Im seeing if I can set up this network with a VPN connection.
Basically we have one network (top in the following diagram) where are headquarters are. This one has a 192.168.100.x range. That's all great. The problem is when we set up a VPN connection with a client.
(All WAN IPs are fake/made up on the spot)
The diagram would be that.
I am physically at the top half of the diagram. As you can see, my VPN server is 192.168.100.199 In the VPN tunnel it has a IP of 10.10.10.1
On the bottom half, there is a remote client which I do not have physical access to NOR do I have networking access to (basically impossible to touch any networking configuration on that side).
Those remote VPN clients should never have access to my network or other networks on that VPN network. That is why there is a 172.16.x.x network. This network has 172.16.9.x and another client would have 172.16.7.x, 172.16.2.x and so on....
I split the networks so they cannot see each other while I can see them (thru the 10.10.10.x tunnel and routing).
The bottom side would be the typical example of a client. He has a machine running Windows Embedded Standard 7 with 2 NICS: His network is set up as 192.168.10.x and one of the machines would be 192.168.10.9 and the OpenVPN client running on that machine would have the assigned IP of 10.10.10.9 BUT I would also like it to have a IP of 172.16.9.1 on ANOTHER NIC (NIC2) on that WES7 machine. Below it would be another machine running Windows CE with 172.16.9.10 directly connected to that NIC2.
When I generate the client configuration using Webmin on the OpenVPN server, I do something like this:
I have been able to configure this network before but we are now using WES7 machines while before we were using this: http://www.netmodule...ine-router.html I cant change the configuration for "better" as it all has to stay compatible between the NB1600 and the WES7
I hope some of you have some great ideas to implement so I can try them out. Thank you.
Basically we have one network (top in the following diagram) where are headquarters are. This one has a 192.168.100.x range. That's all great. The problem is when we set up a VPN connection with a client.
(All WAN IPs are fake/made up on the spot)

The diagram would be that.
I am physically at the top half of the diagram. As you can see, my VPN server is 192.168.100.199 In the VPN tunnel it has a IP of 10.10.10.1
On the bottom half, there is a remote client which I do not have physical access to NOR do I have networking access to (basically impossible to touch any networking configuration on that side).
Those remote VPN clients should never have access to my network or other networks on that VPN network. That is why there is a 172.16.x.x network. This network has 172.16.9.x and another client would have 172.16.7.x, 172.16.2.x and so on....
I split the networks so they cannot see each other while I can see them (thru the 10.10.10.x tunnel and routing).
The bottom side would be the typical example of a client. He has a machine running Windows Embedded Standard 7 with 2 NICS: His network is set up as 192.168.10.x and one of the machines would be 192.168.10.9 and the OpenVPN client running on that machine would have the assigned IP of 10.10.10.9 BUT I would also like it to have a IP of 172.16.9.1 on ANOTHER NIC (NIC2) on that WES7 machine. Below it would be another machine running Windows CE with 172.16.9.10 directly connected to that NIC2.
When I generate the client configuration using Webmin on the OpenVPN server, I do something like this:

I have been able to configure this network before but we are now using WES7 machines while before we were using this: http://www.netmodule...ine-router.html I cant change the configuration for "better" as it all has to stay compatible between the NB1600 and the WES7
I hope some of you have some great ideas to implement so I can try them out. Thank you.