2013/2/3 Jukka Rissanen <[email protected]>: > Hi, > > On 2 February 2013 15:02, Yevhen Kyriukha <[email protected]> wrote: >> My VPN server already push information about routes like: >> server 10.10.10.0 255.255.255.0 >> and >> push "route 10.10.10.0 255.255.255.0 vpn_gateway" >> >> If I use openvpn without connman the behavior is correct (routes are >> replaced only if I push "redirect-gateway" from the server). > > This sounds like a bug. > Can you do following: > > - start vpnd with "connman-vpnd -n -d" and direct the output to a file > - start test/monitor-vpn and direct the output to a file > - connect to your vpn (you should see server pushed routes in debug > output and also in monitor output) > - after successful connection run test/vpn-get to see if we are really > missing the ServerRoutes > > > Cheers, > Jukka
Ok, I did these steps and here's what I got:
When I run "connman-vpnd -n -d" program closes immediately (you can
find output in "connman-vpn.log" file that is attached). Is it
correct? Seems that system activates connman-vpnd by dbus.
In output of 'monitor-vpn' I see the following line:
ServerRoutes = [[{ ProtocolFamily=4 Netmask=255.255.255.0
Network=10.10.10.0 Gateway=10.10.10.81 }][{ ProtocolFamily=4
Netmask=255.255.255.0 Network=10.10.10.0 Gateway=10.10.10.81 }]]
And output of 'vpn-get' contains following:
ServerRoutes = [[{ ProtocolFamily=4 Netmask=255.255.255.0
Network=10.10.10.0 Gateway=10.10.10.81 }][{ ProtocolFamily=4
Netmask=255.255.255.0 Network=10.10.10.0 Gateway=10.10.10.81 }]]
But 'route -n' gives me the same picture that I was talking before
(vpn is a default route iface).
connman-vpn.log
Description: Binary data
_______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
