SecureFishNet
SecureFishNet is OpenVPN client manager for
Sailfish. You can manage openvpn connection with it. It requires
Openvpn and that will be downloaded from repository. (If not you can
do it with “pkcon install openvpn”).
You need normal openvpn configuration file.
This package contains daemon and securefishnet-gui.
PushUpMenu:
- “flush”. In case of something broke routing and network does not work.
This reverses every change this program made to routing. If network still does not work after this, reboot is your friend.
IPv6 does not work correctly.
Category:
Application versions:
Changelog:
2.2-1
- bug fixes ( on connection handling etc.)
- changes underneath to fix issues
2.1-17
- bug fixes + aarch64 version
2.1-15
- fix for bug introduced by last version
2.1-14
- small timing and dns related bugs fixed
2.1-12
- routing fix for android 8 container
- packaging fix
- jollas systemctl changed location in system so minor fix for some of the functionality
2.1-11
- Fixes for 3.1.0.11
2.1-9
- Dns is not always ready instantly so add small delay
2.1-8
- fix for bug in compat mode/static Key handling
2.1-7
- Fix for various DNS and routing related issues
2.1-5
- Fix for changes in SFOS 2.2.1.18 ( UI opened twice because of the way autostart was made (used when VPN is selected to start at boot) )
2.1-4
- fixes for 2.2.0.29
- fix for default gateway not persistent in connection change
2.1-2
- fixes for 2.1.1.26 (not tested with earlier OS versions)
2.0-7
- bug fixes
- ui tweaks
- connection changing logic improved
2.0-5
- bug fixes
- ui tweaks
- more than 3 connections or conffiles
- rewrite of connection changing logic ( again )
1.9-5
- bug fixes
1.9-2
- lots of new features (check config page)
- rewrite of connection changing logic ( only tested with SFOS 2.0.1.7 )
1.6-5
- fixed bug with routing not always working as it should
1.6-4
- bug fixes
1.6-3
- bug fixes
1.6-2
- Lots of minor tweaks
- UI fixes
- more icon sizes = bigger rpm...
- i486 build (not tested on real device but runs fine on emulator)
1.5-4
- and more old bugs fixed... huh...
1.5-3
- more bug fixes
1.5-2
- bug fixes
- You should reboot AFTER installing this as there might be some unwanted leftovers (in routing table) from earlier versions.
1.5-1
- bug fixes
- tcp connection handling improvements and other internal changes
1.4-4
- bug fixes
1.4-2
- new filepicker
- uses less memory
- loads faster
1.3-2
- bug fixes
- better roaming logic
1.2-4
- Some roaming fixes
- UI fixes
- "Static Key" in config dialog might help if connection doesn't start (at all)
1.2-2
- Roaming logic is removed from UI and daemon handles that now so you can close UI and it should still roam
- bug fix for routing
1.0-4
- bug fixes
1.0-2
- fix for minor bug in roaming
- less memory used
- fix for gw not being set with newer openvpn
1.0-1
- UIs internal logic rewrite
- Added connection detection
- Fixed reconnect with openvpn
- Added restart of connection when changing networks ( wlan <-> mobile )
- After UI start status of connection is now shown (If connection is/was up). Roaming logic is in UI so changing networks won't work when UI is closed.
0.9-5
- ui fixes
0.9-3
- ui fixes
0.8-5
- more bug fixes
0.8-4
- fixes bug: dns forwarding in android apps
0.8-2
- MicroSD button in filepicker might actually work now ;-)
- Wait longer for response from openvpn
0.8-1
- Landscape
0.7-2
- Bug fixes
0.7-1
- Small UI improvements
- Encryption is now used on username and passwords when saved ( light encryption only )
0.6-3
- Bug fixes
0.6-2
- Bug fixes
- You can now execute script with PushUpMenu ( user nemo )
0.6-1
- Support for username/password
- Rewrite of everything but UI
0.4-2
- Minor bug fix
0.4-1
- Added support for password encrypted keys ( in config )
- Bug fixes
0.2-3
- Bug fixes
0.2-2
- Bug fixes
- UI improvements
0.1-2 - initial release
Comments
naytsyrhc
Wed, 2014/04/02 - 22:57
Permalink
yes it does say SUCCESS,192.168.253.18,[My servers public IP]. And yes, I have adjusted all paths (otherwise it wouldn't say SUCCESS I presume). I can also see correct logs for successful authentication in server logs. My routing table looks quite ok as well. I can also ping my p-t-p counterpart at 192.168.253.17. But that's it. My resolv.conf is untouched and I'm unable to connect to VPN hosts (neither by IP address , I'll get 'no route to host' error message ). So, something must still be wrong, either routing config or dns or both).
korppi
Wed, 2014/04/02 - 23:09
Permalink
Ok so most of it is working. Do you have Default gw switch below stop button? Or is it gray and you can't check it?
naytsyrhc
Wed, 2014/04/02 - 23:15
Permalink
No. There is no button below start/stop. I only have an area with a busy-indicator showing "busy", below that the SUCCESS,IP,IP line, below that two buttons "Stop" "Config". That's it. Default gw is the correct trail however. I did the following manually to get it to work:
route add [My servers public IP] gw [My routers IP] wlan0
And I entered the IP address of our VPNs DNS manually as first entry in resolv.conf.
After that I was able to "sail" the VPN.
Ray_Ven
Sat, 2014/03/29 - 01:50
Permalink
I'm really looking forward to have an openvpnclient! Unfortunately atm I cannot use this client... My Cert is passwordprotected as well and there's no option for that. But keep up your work! Really looking forward to use it!
Ray
Pages