Hi Daniel, On 04/26/2012 03:08 PM, Daniel Wagner wrote:
[wagi@freakazoid connman]$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 10.1.0.5 0.0.0.0 UG 0 0 0 vpn0 10.1.0.1 10.1.0.5 255.255.255.255 UGH 0 0 0 vpn0 10.1.0.5 0.0.0.0 255.255.255.255 UH 0 0 0 vpn0 10.1.0.5 0.0.0.0 255.255.255.255 UH 0 0 0 vpn0 85.25.128.10 0.0.0.0 255.255.255.255 UH 0 0 0 vpn0 85.25.255.10 0.0.0.0 255.255.255.255 UH 0 0 0 vpn0 172.16.0.0 0.0.0.0 255.255.240.0 U 0 0 0 wlan0 172.16.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 wlan0 194.2.0.20 172.16.0.1 255.255.255.255 UGH 0 0 0 wlan0
I have setup similar network as you have (one client with connman and with openvpn), wlan AP (acting as a router) and behind that an openvpn server and behind the server a host that I can ping.
When I connect to AP and then start openvpn, I get similar list as you but I also have host route to server via gateway setup automagically (you do not have that route in the list above). So in irc you mentioned that you had to manually say "ip route add 85.25.146.15 via 172.16.0.1" but when I am doing similar command, kernel says that route already exists (as expected).
So this is a bit mysterious now, Patrik and I were trying to figure out what routes are missing but I was probably too optimistic when saying that there is a solution to this :(
I could try to figure out from connman debug log if I can spot anything suspicious if you can send the log file to me, and please also describe the network elements with ip addresses of your network.
Cheers, Jukka _______________________________________________ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
