OpenVPN on ICS (Android 4, without root) - now even easier!

jimp

It works fine for me with TLS enabled. It embeds the TLS key in the inline config I export/import and it shows up fine.

charlie0440

Ignore my previous error. I didn't have the latest client export package. I have now updated to v0.20.

New problem; When I click to download the "Inline Configuration" I get a single .ovpn file (as expected). But if I open it with notepad it only contains the following line:
/tmp/client.tar

Exporting using the other options seems to produce valid .ovpn files, but not the inline config. Any idea?

jimp

Interesting - let me test it here and get back to you.

jimp

ok give it 5-10 mins and when 0.21 shows up, reinstall the pkg.

charlie0440

jimp your a star. All connected working perfectly. Man you work fast ;D

charlie0440

I have found a bug or maybe its not a bug but my own naming error (just thought I would mention it).

So I added one VPN and it connected fine. Added a second which is near identical to the first.

first file has this line:
tls-remote charlie

second file has this line:
tls-remote Road Warrior Server Cert

On importing I got an error reading config file:
Option tls-remote has 4 parameters, expected between 1 and 1

I'm sure I can just rename my cert from "Road Warrior Server Cert" to "RWcert" and it will be fine as my other .ovpn file is only a single parameter.

jimp

if you edit the config and put "Road Warrior Server Cert" in quotes (just like that) does it work?

charlie0440

yeh it does, obvious really. Thanks

jimp

ok I'll enclose that in quotes when I update the exporter next time

jimp

Here comes 0.22 with that in quotes…should fix it up.

th3r3isnospoon

This works great! Thanks for the update.

This works on Jelly Bean 4.1.1 as well.

-th3r3isnospoon

phil.davis

Note this thread in Packages http://forum.pfsense.org/index.php/topic,52600.0.html that indicates that putting the string in quotes does not work for some client platforms. Needs a bit of investigation to see exactly what syntax is valid for which clients.

jimp

Perhaps, the real fix is of course to not use spaces in CA/cert names to begin with, but either way, it should work with the quotes I thought.

We may just need a newer build of OpenVPN in the export package and that may be sufficient.

charlie0440

@jimp:

Perhaps, the real fix is of course to not use spaces in CA/cert names to begin with, but either way, it should work with the quotes I thought.

I do agree. Not sure why that one cert of mine had a space in it, none of the others do. As a linux user I don't normally use spaces.