SFOS 2.1 openvpn --dev-type tap not possible

answered 2017-07-27 15:18:48 +0300

V10lator
1045 ●41 ●61 ●59

I'm playing with this since a few days and in fact a tap tunnel is possible but it has drawbacks. Anyway, the --dev-type argument gets setted by connman-vpnd, so just add a line containing OpenVPN.DeviceType=tap to /var/lib/connman/provider_[YOUR_VPN_NAME]_merproject_org/settings.

Now to the drawbacks: Connman does create a new wired ethernet config (/var/lib/connman/ethernet_[RANDOM_MAC]_cable/settings) when the VPN activates but doesn't do anything with it. My guess is that the connman version is simply too outdated (SailfishOS uses 1.31 while TUN/TAP support is officially there since 1.32: https://01.org/connman/blogs/pflykt/2016/connman-1.32 ). Untill they update you could start a DHCP client manually. To do that create a new folder /home/nemo/dhcpHack and in there a file called udhcpc.script witht he following content:

#!/bin/sh

[ -z "$1" ] && echo "Error: should be called from udhcpc" && exit 1

case "$1" in
        deconfig)
                /sbin/ifconfig $interface 0.0.0.0
                ;;
        renew|bound)
                /sbin/ifconfig $interface $ip $BROADCAST $NETMASK

                if [ -n "$router" ] ; then
                        echo "deleting routers"
                                while route del default gw 0.0.0.0 dev $interface ; do
                                        :
                                done

                                for i in $router ; do
                                        route add default gw $i dev $interface
                                done
                fi

                for i in $dns ; do
                        echo ignoring dns $i
                done
                ;;
esac

exit 0

Now execute:

/usr/sbin/udhcpc -i vpn0 -f -v -s /home/nemo/dhcpHack/udhcpc.script -R

Lastly the drawbacks:

• DNS servers will be ignored.
• The hostname won't be told with the DHCP request.
• No IPv6 support.