Good Morning Samuel,
On Wed, Oct 27, 2010 at 02:05:49AM +0200, Samuel Ortiz wrote:
> Hi Daniel,
>
> On Tue, Oct 26, 2010 at 03:54:23PM +0200, Daniel Wagner wrote:
> > Hi,
> >
> > yet another update on this patch. OpenVPN is now running, but I'm
> > struggling with the settings. The OpenVPN server settings seems
> > broken. I can ping the server address (10.1.0.1) from my client
> > (10.1.0.6). But everything else doesn't work yet. Some more debugging
> > needed here :)
> >
> > Another thing I found out is that if there is no netmask set on the
> > provider, connman does not setup the route. Don't know if this a bug
> > in connman or in my setup.
> Although your OpenVPN server should probably provide you with a proper
> netmask, I just pushed a patch to have ConnMan being less pedantic about the
> netmask. So your routes should be set now (Which might also fix the problem
> you're describing in the first paragraph), could you please try ?
OpenVPN only pushes a netmask for tap devices not for tun devices:
--up cmd
Shell command to run after successful TUN/TAP device open (pre
--user UID change). The up script is useful for specifying
route commands which route IP traffic destined for private
subnets which exist at the other end of the VPN connection into
the tunnel.
For --dev tun execute as:
cmd tun_dev tun_mtu link_mtu ifconfig_local_ip ifconfig_remote_ip
[ init | restart ]
For --dev tap execute as:
cmd tap_dev tap_mtu link_mtu ifconfig_local_ip ifconfig_netmask [
init | restart ]
and vpn.c sets up a tun device.
> The patch looks good to me otherwise, except for the Makefile.plugins hack.
> Marcel told me he will try to find out why we're linking twice when a source
> file is defined twice in builtin_sources.
Thanks. Most likely I would have to spend a week to figure out what's
going on. So any help is highly appreciated.
cheers,
daniel
_______________________________________________
connman mailing list
connman@connman.net
http://lists.connman.net/listinfo/connman
