-
Notifications
You must be signed in to change notification settings - Fork 54
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
Halp - I can't get it to connect :sadface: #143
Comments
Hi, After some fiddling I have some more feedback. Requesting a tunnel from the command line works fine:
^C shuts it down gracefully:
Thanks! |
FWIW, here are the contents of the gui log;
...the connection conf file;
and main.conf:
|
Same bug here ...
But openfortigui ...
|
Hi,
Using openfortigui, I get a smattering of errors in the log file which ultimately lead to an immediate disconnect.
I am using version 0.9.0, running on top of openfortivpn 1.12.0-1, Ubuntu 20.04; kernel v5.4.0-54-generic.
The client makes the initial connection to my workplace VPN successfully, it asks for certificate approval, authenticates successfully and negotiates the DNS server settings successfully. However, it then gives a buffer overflow error and halts the connection immediately. Thereafter, when trying to connect, it prompts for an OTP (I have no idea why or where I'd get it). There is also a weird "unable to log out" error that crops up during initial certificate negotiation.
As a point of reference, I also have the legacy 64bit FortiClient SSLVPN 4.0.2333 installed, and it just works. I enter the server address, username and password and away it goes. I'd keep using it but the new client seems to have plenty of nice QoL features which I'd like to have.
I have left all the settings for the connection at their defaults, that is:
Set Routes: yes
Half Internet Routes: no
Set DNS : yes
Insecure SSL: no
Debug: y/n - it makes no difference and gives no useful info that I can see (but I might be wrong)
Realm: empty
PPPD stuff: disabled and all empty
Herewith some loggery:
If I try and connect once more, it asks for an OTP, if I enter a blank (or pulled-from-nethers) OTP and submit, the log file looks like this:
I am not in control of the hardware at work (and don't have any access to it) so could not tell you firmware versions and whatnot. All I know is, the old one works out of the box but the new one doesn't and I don't know how to fix it or what questions to ask to start fixing it. I also don't know if it's an issue with gui or the underlying openvpn implementation.
Any assistance would be greatly appreciated!
Thanks and regards,
Rhianne
PS _ I tried running it as root too, no change.
The text was updated successfully, but these errors were encountered: