-
Notifications
You must be signed in to change notification settings - Fork 647
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
OpenConnect Startup - deletion failed for interface #1359
Comments
|
I have the same problem and the same messages in error log in my test installation: OpenConnect could not start automaticly after startup. I use the last version 19.7.3. What is the problem? I also tried to setup OPNsense without explicitly assigning the interface A manual start is no problem: @mimugmail: Can you have a look at the issue next time, please? THX |
|
Having the same here (OPNsense 21.7.1-amd64):
|
This looks like a different error, did you assign the interface? |
|
Definitely, and If I try to connect it manually once opnsense is up, it works perfectly, without any issue. Or, to be exact, I always need to connect twice to be connected. The first attempt fails everytime. Maybe it's due to the fact there's Okta 2FA on the server side - and even if I do the 2FA, it fails for the first time from unknown reason... |
|
Can you follow the display output during startup? |
|
Definitely, I will put the output here in the evening, I cannot reboot the firewall during the workday. |
|
Here the complete log during the startup; normally I am just asked to supply 2FA (to confirm the access in Okta application) during the openconnect is started; shortly after that, when the machines is booted up I can even see that the IP for that VPN connection (ocvpn0) has been assigned, but then it probably fails somehow and disconnects...
|
|
It seems your default gateway is not available during startup so openconnect fails. |
|
@minugmail I also have the same problem, the Note I can receive Okta Push Verify for OpenConnect (AnyConnect) MFA so the connection between client and VPN server should be fine. I also have issue that after I think the issue is similar to #866, but I can't figure out how to fix it |
|
This issue has been automatically timed-out (after 180 days of inactivity). For more information about the policies for this repository, If someone wants to step up and work on this issue, |
|
You should reopen this because it is still a problem.
Go to system->Diagnostics->Services and start OpenConnect and it works perfectly. I did notice that after openconnect starts the system attempts to start openvpn. Open VPN is not configured on my system, why would it try to start? On another subject, the password for the VPN is stored in both the config and in a secrets file in CLEAR TEXT. That's not good at all! |
I'm getting this error on startup, which appears to prevent OpenConnect from starting. I have to start it manually.
I'm trying to understand how best to NAT. In this documentation, it states to use the OpenConnect "interface" (which doesn't show up as an Interface, but does show up under Firewall Rules). However, in other places 1, 2, it is suggested creating an interface and locking it. But then you end up with two things under Firewall rules. I just need this thing to be persistent after reboot where it starts up automatically and NAT rules apply.
The text was updated successfully, but these errors were encountered: