Hi all,
General situation:
I have a "client1" connecting via an UMTS USB-modem (tun0= 192.168.1.8) to my openvpn "server" (tun0=192.168.1.1).
On the ethernet interface (192.168.2.1) on "client1" I connected a "video server" (192.168.2.2) and a "laptop1" (192.168.2.3).
They both getting the IP address from the dhcp-server installed on "client1". On my "server" I have "/ccd/client1" file in which I configured the static IP address (192.168.1.8) and "push route" for the 192.168.2.0 network. Furthermore I enabled IP-forwarding on client1. I'm able to ping from "laptop1" my "server" over the openvpn channel and vica versa.
Now I have a WindowsXP "client2" connecting also via an UMTS USB-modem (tun0= 192.168.1.6) to my openvpn infrastructure. This client can ping the "server" and "client1" since "client-to-client" on server is activated.
Problem:
I'm not able to ping the 192.168.2.0 network from "client2" side. I tried to add a route on "client2" with the command:
"route -p add net 192.168.2.0 netmask 255.255.255.0 gw 192.168.1.8 metric 30 if 2 (0x2 = openvpn interface on winxp).
This route is not accepted by client2.
Any suggestions to solve this problem?
Tks
TamTam
Routing problem between two umts clients
Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech
Forum rules
Please use the [oconf] BB tag for openvpn Configurations. See viewtopic.php?f=30&t=21589 for an example.
Please use the [oconf] BB tag for openvpn Configurations. See viewtopic.php?f=30&t=21589 for an example.
-
tamtam
- OpenVpn Newbie
- Posts: 1
- Joined: Wed Nov 11, 2009 10:16 am
-
mwandelaar
- OpenVPN Super User
- Posts: 219
- Joined: Mon Nov 23, 2009 8:24 pm
Re: Routing problem between two umts clients
As far as i can see the problem right now is pretty easy:
"client1" can reach both networks as it is connected to both networks, thus knowing the route to both networks.
"client2" can reach your 192.168.1.0/24 network, being the vpn-network, but it does not know where the 192.168.2.0/24 network is. Adding the route to the client is half way solving the problem. For adding the route (i'm not working on Windows, so i'm not familiar with the command-structures there), leave the metric and interface out. The system should know where it can find 192.168.1.8.
When that's working, you need to take care "laptop1" and "video server" know where to find the 192.168.1.0/24 network, if the ethernetinterface on "client1" isn't allready there default gateway. And offcource "client1" needs to be setup to do routing (echo 1 > /proc/sys/net/ipv4/ip_forward on linux)
Does this solve your problem?
Cheers,
Max
"client1" can reach both networks as it is connected to both networks, thus knowing the route to both networks.
"client2" can reach your 192.168.1.0/24 network, being the vpn-network, but it does not know where the 192.168.2.0/24 network is. Adding the route to the client is half way solving the problem. For adding the route (i'm not working on Windows, so i'm not familiar with the command-structures there), leave the metric and interface out. The system should know where it can find 192.168.1.8.
When that's working, you need to take care "laptop1" and "video server" know where to find the 192.168.1.0/24 network, if the ethernetinterface on "client1" isn't allready there default gateway. And offcource "client1" needs to be setup to do routing (echo 1 > /proc/sys/net/ipv4/ip_forward on linux)
Does this solve your problem?
Cheers,
Max