I think all is fine until I try to route all traffic through VPN - I cannot ping google.com or it’s IP address (216.58.209.46) and basically the VPN does not work.
Here’s my routing table before starting the tunnel:
Thanks - I edited /etc/sysctl.conf and enabled the changes with sysctl -p /etc/sysctl.conf. Then I restarted the device to be extra sure the changes are applied.
Unfortunately, it didn’t solve the problem.
Any suggestion where to dig in?
after these changes my PPTP client started working correctly.
Now my question to developers (@sam_nazarko and @DBMandrake) is: will this setup work long term, or will I have any problems?
I’d really love to see the PPTP client work with ConnMan, but I’m rather a beginner in linux world, so if someone can guide me, I can continue troubleshooting the connman and my pptp setup.
To be sure that the changes are used try this command, and if it say’s “1” then its used…:
cat /proc/sys/net/ipv4/ip_forward
this command is not helping you , pptp does this on it’s own. “sudo route add default dev ppp0”
there should be no need.
i think your problem is that you have set this up like it was on the internet and having/using the same IP as the server(that need iptabels for forwarding), you should give it it’s now range for pptp.
here is my pptp.conf:
localip 10.0.1.126
remoteip 10.0.1.100-200
all in all i don’t think this is a problem with either OSMC or connman.
if you want more help please add your pptp.conf file and pptpd-options file.
Thanks for your help - however, I don’t have these files you ask for in /etc/ppp - these are the files I have: chap-secrets ip-down.d ip-up.d ipv6-down.d ipv6-up.d options.pptp peers ip-down ip-up ipv6-down ipv6-up options pap-secrets
Please note, that I don’t have my own VPN server - I’m just trying to connect to remote service (hideipvpn.com)
I think the issue is that ConnMan keeps modifying the routing table. After establishing the VPN connection and executing the following command (to route all traffic through VPN): sudo route add default dev ppp0 I end up with two default routes, right?:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp0
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
I just got SSTP-client installed yesterday (for having never used linux before that was quiet a project).
It seems to get a local ip on my home network and I can see on my windows server that it’s connected. However I have the same problem as above, can’t access anything on the network, can’t ping either outside the network or other devices on the network. So I take it it’s the routing probelm mentioned above but it seems the thread just died out.
Well I’m only interested in SSTP and not PPTP therefore the usage of the SSTP-client.
My windows server with the VPN server side only runs with SSTP for the security reaons, and I like that it uses the 443 port which will be accessible from most places.
So I’m still very much interested in a workaround…
When using the SSTP-client, if I go into systeminfo within Kodi and then network I see the correct ip-adress (VPN), correct subnet, but the gateway is completely empty. I take it this is the problem but I don’t know how to fix so the gateway is to my home router?
, pptp does this on it’s own.