Skip to content
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

Double layer openvpn problem after upgrade to 19.1 #3236

Closed
ofit opened this issue Feb 15, 2019 · 6 comments
Closed

Double layer openvpn problem after upgrade to 19.1 #3236

ofit opened this issue Feb 15, 2019 · 6 comments
Labels
support Community support

Comments

@ofit
Copy link

ofit commented Feb 15, 2019

Hello guys.
Problem 1

I use Double layer Openvpn on Opnsense, but after upgrading the system to 19.1 at boot does not use OpenVPN_1 tunnel. That means it use only OpenVPN_2 not OpenVPN_2 inside OpenVPN_1. If stop and start OpenVPN_2 it is work ok, OpenVPN_2 inside OpenVPN_1. Please fix this bug. Thanks

Double layer Openvpn -> OpenVPN_2 inside OpenVPN_1

Post on forum.opnsense.org
https://forum.opnsense.org/index.php?topic=11650

Problem 2
From #3259

I use Double layer Openvpn on Opnsense, but when WAN changing IP (i mean reconnecting) OpenVPN_2 not start inside OpenVPN_1. OpenVPN_1 up ok. I need manually start OpenVPN_2 almost every time.
I think bug because OpenVPN_2 do not wait until OpenVPN_1 up and stop at all. Please fix this bug. Thanks

This bug was on 19.1 and 18.7+ versions.
Double layer Openvpn -> OpenVPN_2 inside OpenVPN_1
OpenVPN_1 and OpenVPN_2 use UDP and AES
WAN is pppoe connetion that recconnect and get new ip one time in 2-3 days

Post on forum.opnsense.org
https://forum.opnsense.org/index.php?topic=11829

@AdSchellevis AdSchellevis added the support Community support label Feb 15, 2019
@fichtner
Copy link
Member

@ofit
Copy link
Author

ofit commented May 5, 2019

Why is it close? OPNsense 19.1.7-amd64 still have this bugs.

@AdSchellevis
Copy link
Member

@ofit
Copy link
Author

ofit commented May 5, 2019

Ok. And what i should do? Create it again? or did something else?

@AdSchellevis
Copy link
Member

If your planning to work on "it" yourself, you can always ask to reopen, but as long as there's nobody working on it, it doesn't make sense to keep it open endlessly. (not the support tag as well)

@ofit
Copy link
Author

ofit commented May 5, 2019

ok. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support Community support
Development

No branches or pull requests

3 participants