-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Segfault with "multihome" option and dco enabled #390
Comments
fix sent to the mailing list: https://patchwork.openvpn.net/project/openvpn2/patch/20230815231555.6465-1-a@unstable.cc/ |
Removing "multihome" option |
cron2
pushed a commit
that referenced
this issue
Sep 10, 2023
Although it's a combination of options that is not really useful, when specifying --multihome along with --proto tcp and DCO is enabled, OpenVPN will crash while attempting to access c2.link_socket_actual (NULL for the TCP case) in order to retrieve the local address (in function dco_multi_get_localaddr()) Prevent crash by running this code only if proto is UDP. The same check is already performed in socket.c/h for the non-DCO case. Github: fixes #390 Change-Id: I61adc26ce2ff737e020c3d980902a46758cb23e5 Signed-off-by: Antonio Quartulli <a@unstable.cc> Acked-by: Gert Doering <gert@greenie.muc.de> Message-Id: <20230815231555.6465-1-a@unstable.cc> URL: https://www.mail-archive.com/openvpn-devel@lists.sourceforge.net/msg26953.html Signed-off-by: Gert Doering <gert@greenie.muc.de> (cherry picked from commit 0793eb1)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The server is running in TCP mode, the "multihome" option is declared in the config and the ovpn_dco_v2 kernel module is loaded. When a client then connects to the server, openvpn gives a segfault and crashes.
This crash can be prevented by one of the following actions:
Expected behavior
Clients can connect without the server crashing.
To Reproduce
Server config:
Version information (please complete the following information):
Logs and debug
Gdb stackstrace:
Server logs with --verb 9: https://gist.github.com/MertenF/3fadb7a74d580c697bc182a5ac0e86af
The text was updated successfully, but these errors were encountered: