SecureFishNet

Wed, 2015/08/26 - 18:53

Update to 1.5-2 -> reboot -> run Sequrefishnet and "start" -> shows "connected".

Nevertheless, I can't access my home network.

What can I try, which was still working at 1.4-4.

Ronny

Wed, 2015/08/26 - 19:20

One question : Can you stop the connection and restart it now ?

But in anycase I need log from command:

"openvpn --user nobody --group nobody --config config_name.conf --verb 4"

Just remove all the data you don't want to give me like IPs and such...

Wed, 2015/08/26 - 20:13

I must still test Reconnect.

"openvpn" with user "nobody" gives me an error "Permission denied" because my ".key"-files are only readable by root. Requires the program now other permissions?

Wed, 2015/08/26 - 20:21

New version to test again ;-)

Wed, 2015/08/26 - 20:19

You can test without those... As in "openvpn --config config_name.conf --verb 4" . (Openvpn itself need to be launched as root. )

Wed, 2015/08/26 - 20:53

Wow, how fast you make the updates! Connection to the home network works with 1.5-4 again. :-)

After I stopped the connection, the network no longer works ("ping google.de" show "unknown host"). When I choose 'flush', the network is working again.

Restarting VPN work until after a 'flush'. Without 'Flush' is 'starting' and after long time 'Resolve' appears. Unfortunately, it is the starting not interrupt with 'Stop' as grayed out.

Thu, 2015/08/27 - 09:41

Found that problem, strange that it happens only very rarely with my setup.

It's dns problem and it is only triggered by my OVPNdaemon when switching the DNS to normal mode. And the bug is not even in my code...

Unfortunately I have no fix for that at the moment.

By the way "flush" does allmost the same thing as "stop" just more forcefully. And you can use "flush" even when "stop" is grayed out.

Wed, 2015/08/19 - 17:29

As far as I can say from the comments here, I seem to have the same issue like ronny_b. Appliation doesn't react and keeps showing "starting". My .ovpn files work well on dekstop Linux using OpenVPN - I haven't tested them yet using command line on Sailfish, but will do + futher testing with your app.

Older versions didn't solve the issue.

Wed, 2015/08/19 - 17:52

So is it working ones and not again too ? Or not at all ? Because "starting" there doesn't really mean anything...

Wed, 2015/08/19 - 19:15

Thanks for your answer and sorry for the unlcear comment. It's actually a bit different, as I can't establish a connection at all. When I set up a new connection and press start button, it says "starting" and "disconnected" within a second. After using Flush-option, it leads to a constant turning circle and "starting" indication (and stop button appears). But the VPN connection is not established - static key option doesn't make a difference.

I've tested it with 2 different ovpn files (different gateways, same keys) and Jolla device is running on SF 1.1.7.27. I will try it again as soon as possible.

Wed, 2015/08/19 - 19:20

Sounds like different thing... Is your paths of certificates and keys absolute( something like "/home/nemo/client.key") ? Or maybe you should reboot... Version 1.4-4 has some fixes that might help.

Wed, 2015/08/19 - 19:49

Yes keys are in the right place and "openvpn --config "vpnconfiguartionfile.ovpn" using terminal works perfectly. My last tests happend with v1.4-4 and reboot makes no difference.

In case I can do something else on my device which might help your development, please let me know. But no hurry :) If I can make it work somehow I'll let you know, thanks for your help!

Wed, 2015/08/19 - 19:56

Ok I need log from command:

"openvpn --user nobody --group nobody --config config_name.conf --verb 4"

Just remove all the data you don't want to give me like IPs and such...

Wed, 2015/08/19 - 21:21

What I realized is that it fails to start openvpn (command line) without being root. Maybe that has something to do with it? Unfortunately my knowledge hits a limit there.

I get following error:

Wed Aug 19 20:07:40 2015 us=506400 ERROR: Cannot open TUN/TAP dev /dev/net/tun: Permission denied (errno=13)
Wed Aug 19 20:07:40 2015 us=506613 Exiting due to fatal error

Anyways, I'll send you both logtexts via Openrepos contact form (I assume that will go to your email address) once I'm in front of my computer.

Thu, 2015/08/20 - 12:20

Does it work now with 1.5-1 ?

Thu, 2015/08/20 - 08:40

Received...

Normal user can't open tun/tap device. Thats why there is daemon handling that (and routing).

And thanks for logs.

Sat, 2015/08/22 - 12:04

Thanks for the explanation and also for the update! Unfortunately no success in my case. I also removed the app (incl. user data) and reinstalled it + reboot. I'm sorry... :-/ I wished I had the knowledge to help!

In case I can send you other log files or try out stuff, please let me know.

Wed, 2015/08/12 - 20:37

Hello,

unfortunately all versions of the program don't work with me after 1.0.4. I can start only once the connection and also access on my network. After I broke the connection, I can reconnect me until after a restart of the device to the network. The program displays otherwise just "starting", no further reaction. The remote site is a FritzBox with OpenVPN (Freetz) in connection with certificates with me.

Ronny

Thu, 2015/08/13 - 12:44

Well there's bugs in 1.0-4 ... But you can use flush(routing back to normal), which should make it work again.

But what interests more is why newer versions doesn't work.

What version of sailfish to you have ?

Is the device Jolla or something else ?

Does the gui start at all or ... ?

Did you reboot the device after installing ?

Fri, 2015/08/14 - 20:37

I had also already tried the option "routing back to normal", unfortunately, does not help.:-(

I have a Jolla phone with 1.1.7.25.

Yes, the GUI is starting. When I click on "start" the screen displays 'starting' and turns on until I press 'stop'. Only after a restart of the phone I can connect again exactly one time. In a second connection attempt is again only 'Starting' is displayed.

Ronny

Fri, 2015/08/14 - 21:09

Ok so it gets stuck very early if "starting" is last message. Connected is what should read when connected...

And you have tried version 1.4-2 ?

Sat, 2015/08/15 - 09:56

So, a test with V1.4-2:

- End old Securefishnet

- Update to 1.4-2

- Start new Securefishnet

- Touch "Start"

- Securefishnet shows "Starting" -> "Auth" -> "Connected" :-)

- Touch "Stop"

- Securefishnet shows "Disconnected"

- Touch "Start"

- Securefishnet shows "Starting" to I press again on "Stop" :-(

Only when I touch "Flush (routing back to normal)" the additional entry in the routing table is cleared. Now I can again make a new connection. :-)

But how can I reach that resets the routing table when you exit the connection automatically, which has in the old version works reliably?

Ronny

Sat, 2015/08/15 - 10:44

Ok I was looking at wrong part of the code...

Do you have developer mode on ? If so you could check if openvpn is still in process list when you click stop after successfull connection.

Or command as root "journalctl -rx|grep OVPNdaemon|head" (log in reverse order). There should be "OK_STOPPED" and "STATE,DISCONNECTED,"

Sat, 2015/08/15 - 11:23

When VPN is connected:

[nemo@Jolla ~]$ ps -ef | grep openvpn
nobody 3509 3498 0 10:16 ? 00:00:00 /usr/sbin/openvpn --user nobody --group nobody --config /etc/openvpn/vpn.conf --dev p2p5 --dev-type tun --verb 4 --management-query-passwords --auth-retry interact --management-hold on --persist-tun --auth-user-pass --persist-key --management 127.0.0.1 4445

After touch "Stop" is no openvpn in process list. Here the log:

[nemo@Jolla ~]$ sudo journalctl -rx|grep OVPNdaemon|head
Aug 15 10:20:33 Jolla OVPNdaemon[4149]: "STATE,DISCONNECTED,"
Aug 15 10:20:33 Jolla OVPNdaemon[4149]: "OK_STOPPED"
Aug 15 10:20:28 Jolla OVPNdaemon[4149]: "STATE1,OPENVPN_STARTED,"
Aug 15 10:20:28 Jolla OVPNdaemon[4149]: "MANAGEMENT:192.168.100.1,VPNGW,"
Aug 15 10:20:28 Jolla OVPNdaemon[4149]: rtt min/avg/max/mdev = 4.548/4.548/4.548/0.000 ms
Aug 15 10:20:28 Jolla OVPNdaemon[4149]: 1 packets transmitted, 1 received, 0% packet loss, time 0ms
Aug 15 10:20:28 Jolla OVPNdaemon[4149]: --- 192.168.100.1 ping statistics ---
Aug 15 10:20:28 Jolla OVPNdaemon[4149]: 64 bytes from 192.168.100.1: icmp_req=1 ttl=64 time=4.54 ms
Aug 15 10:20:28 Jolla OVPNdaemon[4149]: PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data.
Aug 15 10:20:28 Jolla OVPNdaemon[4149]: Do you want to ping broadcast? Then -b

Sat, 2015/08/15 - 11:34

OK looks fine...

This time after clicking "stop" as root command "killall -9 OVPNdaemon" and wait few seconds and try start again, does it work then ?

Sat, 2015/08/15 - 12:45

When I after clicking "Stop" kill OVPNdaemon, it will be restarted. Nevertheless the connection can be only after "Flush (routing back to normal)" start again.

Sat, 2015/08/15 - 12:49

I meant does it need anything else than killing the daemon to start the connection again?

Or do you need to do "flush" ?

Sat, 2015/08/15 - 13:02

When I kill the daemon, it will restart automatically.

When I then start the connection, it hangs anyway at the message "Starting".

Sat, 2015/08/15 - 13:24

Ok. Just wondering why that part of code is not broken for everybody... Because I haven't seen that behavior in long time after I fixed it...

Anyway I have enough info, will check the code and see if there is something that I didn't see last time.

girishpadia

Wed, 2015/06/03 - 19:37