SecureFishNet

Ok, thank You.

kaulian

Tue, 2016/04/12 - 13:14

Thanks for the new release and the "autoconnect on data or wifi" nice feature

sebsikora

Tue, 2016/01/12 - 03:31

Hi, problem here, and fix.

(apologies if this appears twice, buggy connection)

- Couldn't connect to Mulvad VPN using SecureFishNet.

- Tried using openvpn from command line - didn't work - couldn't find auto-resolv-conf

- Found this post - https://talk.maemo.org/showthread.php?t=92276 - in which author describes process for setting up connection using openvpn. Points out that once following the steps to copy the resolv updater scripts into the correct location, their filenames may not match those that appear in your VPN config file.

- I checked, mine did not. I edited the file as stated in the post and openvpn connection then worked from command line.

- I reopened SecureFishNet and could now connect in this manner also.

Happy hunting.

Mon, 2016/01/18 - 12:19

You should NOT use any up/down/resolver-scripts. And config that does not work with openvpn directly is likely to fail(because openvpn is used here too).

You really should remove that resolv-updater from your config because sailfishOS's connectionmanager(=connman) really hates when somebody changes that file(/etc/resolv.conf) and connection sometimes stops working after that. And I mean all connections to anywhere.

But nice that you found temp fix...

sebsikora

Mon, 2016/01/25 - 22:21

Do you mean that the openvpn config should contain no references to the client up and down scripts at all? From a fresh install Openvpn would not connect, with the original paths in it's config. If I simply remove the references, rather than 'correct' them, it should work?

Sat, 2016/01/30 - 13:39

I mean in context of sailfish or any other system which is controlled by some kind of network manager, in this case connman. You should NOT use any of those scripts which do something to network connection. It is just generally bad idea, but if know what you are doing then...

So just remove or comment out the lines in config unless you absolutely need them. Or something strange might happen... Or not ;-)

caprico

Wed, 2015/11/18 - 02:26

Really great app! Just gave it again a try after it didn't work a couple versions ago. Everything's perfect now :-) Thanks for figuring out the issues. I look forward to use SecureFishNet from now on.

jaekkay

Sun, 2015/11/15 - 22:12

After upgrading to version 1.6-4, the application says it is connected but browser still shows actuall IP instead of VPN IP. It seems routing is not working as it should.

Mon, 2015/11/16 - 09:44

Check with 1.6-5. Contains some fixes for that.

Tue, 2015/11/17 - 09:35

This version fixes my route problems too!

jaekkay

Mon, 2015/11/16 - 11:48

Thanks, it is working fine with 1.6-5.

Ingvix

Fri, 2015/11/13 - 01:29

The app says it's connected but when I check my ip from duckduckgo on the browser it gives my own IP. What's the problem?

Mon, 2015/11/16 - 09:45

Check with 1.6-5. Contains some fixes for that.

Ingvix

Tue, 2015/11/17 - 12:13

Working for me too now.

kaulian

Sun, 2015/11/08 - 13:58

Hi,
Thanks for this application

is there a possibility to start connexion at launch ? or with cmd line ?

i would like to start vpn always when phone use mobile data. i think use situation to monitoring the change of connexion but i dont know how to auto connect to the vpn.

thanks

Wed, 2015/11/11 - 13:28

No way to use this like that right now, but maybe later as an option in settings page or commandline or something...

xcablex

Wed, 2015/10/21 - 16:57

Hey,

first of all thank you very much for coding a sailfish app!

just installed SecureFishNet. I can't connect to my VPNs. Using the Terminal with "openvpn blabla.ovpn" works fine as long I'm root.

In SecureFishNet I push Start and it switches from Starting to Disconnected immediatly.

Some comments earlier you said "Normal user can't open tun/tap device. Thats why there is daemon handling that (and routing)."

Could there be the problem?

Any idea?

Thu, 2015/10/22 - 17:00

Test with version 1.6-2.

Wed, 2015/10/28 - 10:12

Tested it with 1.6-2 on 2.0.0.10: No routes built. When starting openvpn by hand as root everything works fine (including v6)

Wed, 2015/10/28 - 10:31

Can't parse "No routes built."

If you mean you don't see added routes when you execute "route" that is kind of expected, because routes are in different routing table...

And if you had read description of this app you'd know that ipv6 is not working... So no news there...

Wed, 2015/10/28 - 14:13

Quite simple: If you start openvpn by hand as nemo (not devel-su) you can see the daemon running. In openvpn's stdout you can see that the connection is not established now because you cannot create tun interface. An ip route shows the internet router as default gateway. There is no tun0 interface. So "no routes built" because missing tun0 and missing tunnel.

If you startup openvpn as root you can see the daemon running. In openvpn's stdout you can see that the connection is established. ip addr shows the default route to your openvpn interface (e.g. some 10.x.x.x address as gateway) and a tun0 interface. Routes built.

Now with Securefishnet:

The openvpn daemon is running. There is no tun0 interface and the default route is the internet router. Looks like openvpn without root and "no routes built" IMHO it is a permission problem.

Sometimes there are two routes (10..x.x.y/31 networks to mask out the default gateway) - > So I wrote "Routes" built.

Wed, 2015/10/28 - 14:26

Look for p2p5 interface as my app overrides device name for reasons I am not explaining here.

And if you want to look at routes after starting connection just "ip route show table 4" as they are there.

And no permission problems... you just don't know what to look for.

Wed, 2015/10/28 - 16:01

hm table 4 no default route into vpn device p2p5 either though set in ui.

Wed, 2015/10/28 - 17:25

Execute "securefishnet-gui" from commandline as user nemo and start connection and check if the ips that it prints are something they should be.

Wed, 2015/10/28 - 21:56

Ahem, I just upgraded to your version 1.6-3 and it is working again. Thank you for your effords and building this nice tool.

naytsyrhc

Thu, 2015/10/08 - 23:46

I have some problems since some update of openssl that enforces not to use MD5. Exporting OPENSSL_ENABLE_MD5_VERIFY=1 before starting openvpn in terminal works though. So is there a possibility to pass such Environment within your app? And: the UI is slightly misplaced in 1.1.9.28 (i.e. sfos2). Maybe you can fix that?

Fri, 2015/10/09 - 11:26

You can add environment variables to /etc/systemd/system/OVPNdaemon.service

Environment="LANG=en_US.UTF-8" "OPENSSL_ENABLE_MD5_VERIFY=1"

BUT BE CAREFULL !!!

After changing that (as root):

systemctl daemon-reload

systemctl restart OVPNdaemon

naytsyrhc

Sat, 2015/10/10 - 22:33

That worked perfectly. Thanks!

ronny_b

Mon, 2015/08/24 - 20:34

Hello,

I have tested the version 1.5-1. With this version I get no access to my home network. Unfortunately, there was no change with my problem. I'm first back to 1.4-4. :-(

Ronny

Tue, 2015/08/25 - 10:02