-
Notifications
You must be signed in to change notification settings - Fork 326
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added daemon run mode #835
base: master
Are you sure you want to change the base?
Conversation
c4edc56
to
b5626fd
Compare
Why not use systemd instead? |
Because our system is pure embedded one without systemd and with read-only fs ;) |
Hello @mobrembski, why not writing a small wrapper on your system, to daemonize openfortivpn?
Almost all systems have their services/daemons manager (systemd is an example), so a deamon mode in openfortivpn wouldn't be used much, and would probably too basic for most uses (auto-restart on crash, etc.) |
Well, maybe it's a good idea :) i will have a look :) thanks! |
@mobrembski Indeed we'd rather not add functionality in openfortivpn if the same can be achieved by a small script. That said, if you feel changes in openfortivpn are required to obtain extra functionality, we're happy to hear about it. |
This is a feature that I would find very useful and it is included in other command line VPN tools we use. That said, we would be open to using a "small script" if that was straightforward. However, across all the tickets mentioned, I have struggled to understand and get any working as expected. @adrienverge are you able to expand on the Other implementations I have seen have for example a |
@charlietomo The conf file question seems orthogonal to sending openfortivn to the background. You need to read about the command line options. |
I have read the documentation and prefer to use a It seems I am not the only one expecting this feature and struggling to make it work through other means, although I understand it is not a feature that wants to be included. If you have any time to write a brief explanation of your command that would be very much appreciated. |
You still need to read the command line options to learn how to reference your conf file. As for what |
@charlietomo I'm not sure what the PS:
I doubt that. How to use a config file is at the very top of the man page: |
Apologies I think I may not have worded my question well and misunderstood @DimitriPapadopoulos reply re "The conf file question seems orthogonal to sending openfortivn to the background." I have read the documentation and have multiple successfully working config files. What I do not have is a successful "send to background" mode, which is what this thread was started about (not by me). @DimitriPapadopoulos thank you for the link to the wiki. That may be worth linking to from the @adrienverge I'm not the original poster and only commented after you detailed the command, which I assumed you may have used or had knowledge of, which you might have been able to share. I have searched and used the various comments in other threads, but to date have not been successful. I will go back to searching and experimenting. |
the to supply a config file just put the usual For completeness: |
Many thanks. I will experiment with this whilst reading further, but your explanation was very useful. |
nohup and systemd are not a replacement for background mode in some cases. As soon as 2FA is enabled it needs to stay in foreground until the user has entered the token and then it can daemonize. This is also how --daemon in openvpn works. |
True, see also #791. Meanwhile 2FA is not implemented. |
I have a connection where I either get the token via EMail or SMS so 2FA is definitely working - I use it all the time. |
Yes, SAML is not working, sorry. Still it's best implemented together with a patch for #791. |
4ee28f2
to
b5626fd
Compare
b5626fd
to
6e69ff7
Compare
As title says, adding daemon mode to run tunnel in background, like most servers do.