Introduce connection state for reconnecting peer in p2p
PATCH 1/1 Introduce connection state for reconnecting peer in p2p
We introduce this state to make the reconnecting of a client more obvious and what is called again instead of making it implicit. The new state CAS_RECONNECT_PENDING is between CAS_WAITING_OPTIONS_IMPORT and CAS_CONNECT_DONE as we need to redo some of the steps of the connection setup, so this new state is going a "half step" back in the state machine.
We also do no longer generate data channel keys for untrusted session. This is done for clarity but also to allow them being generated after the session has become actually active.
These changes allow a reconnect in p2p mode with DCO to work as the initial reconnect working.
--- src/openvpn/forward.c | 19 +++++++++++++---- src/openvpn/init.c | 6 ++++++ src/openvpn/ssl.c | 46 +++++++++++++++++++++++----------------- src/openvpn/ssl.h | 1 + src/openvpn/ssl_common.h | 5 +++++ 5 files changed, 53 insertions(+), 24 deletions(-)
src/openvpn/forward.c +15 -4
@@ -174,7 +174,14 @@ check_tls(struct context *c)const int tmp_status =tls_multi_process (c->c2.tls_multi, &c->c2.to_link, &c->c2.to_link_addr,get_link_socket_info (c), &wakeup); -if (tmp_status ==TLSMP_ACTIVE ) + +if (tmp_status ==TLSMP_RECONNECT ) + { +event_timeout_init (&c->c2.wait_for_connect,1 , now); +reset_coarse_timers (c); + } + +if (tmp_status ==TLSMP_ACTIVE || tmp_status ==TLSMP_RECONNECT ) {update_time ();interval_action (&c->c2.tmp_int);
@@ -196,9 +203,15 @@ check_tls(struct context *c)interval_schedule_wakeup (&c->c2.tmp_int, &wakeup); -/* Our current code has no good hooks in the TLS machinery to update +/* +* Our current code has no good hooks in the TLS machinery to update * DCO keys. So we check the key status after the whole TLS machinery * has been completed and potentially update them +* +* We have a hidden state transition from secondary to primary key based +* on ks->auth_deferred_expire that DCO needs to check that the normal +* TLS state engine does not check. So we call the \c check_dco_key_status +* function even if tmp_status does not indicate that something has changed. */ check_dco_key_status (c);
@@ -302,7 +315,6 @@ check_push_request(struct context *c)static void check_connection_established (struct context *c) { -if (connection_established (c)) {/* if --pull was specified, send a push request to server */
@@ -337,7 +349,6 @@ check_connection_established(struct context *c)event_timeout_clear (&c->c2.wait_for_connect); } - }bool
src/openvpn/init.c +6 -0
@@ -2219,7 +2219,13 @@ do_up(struct context *c, bool pulled_options, unsigned int option_types_found) } } } + } +/* This pats needs to be run in p2p mode (wihout pull) when the client +* reconnects to setup various things (like DCO and NCP cipher) that +* might have changed from the previous client. */ +if (!c->c2.do_up_ran || (c->c2.tls_multi && c->c2.tls_multi->multi_state ==CAS_RECONNECT_PENDING )) + {if (c->mode ==MODE_POINT_TO_POINT ) {/* ovpn-dco requires adding the peer now, before any option can be set,
src/openvpn/ssl.c +26 -20
61 lines not on this page · raw message
src/openvpn/ssl.h +1 -0
@@ -212,6 +212,7 @@ void tls_multi_free(struct tls_multi *multi, bool clear);#define TLSMP_INACTIVE 0#define TLSMP_ACTIVE 1#define TLSMP_KILL 2 +#define TLSMP_RECONNECT 3/* * Called by the top-level event loop.
src/openvpn/ssl_common.h +5 -0
@@ -551,7 +551,12 @@ enum multi_status {CAS_PENDING_DEFERRED_PARTIAL ,/**< at least handler succeeded but another is still pending */ CAS_FAILED ,/**< Option import failed or explicitly denied the client */ CAS_WAITING_OPTIONS_IMPORT ,/**< client with pull or p2p waiting for first time options import */ +CAS_RECONNECT_PENDING ,/**< session has already successful established (CAS_CONNECT_DONE) +* but has a reconnect and needs to redo some initialisation, this state is +* similar CAS_WAITING_OPTIONS_IMPORT but skips a few things. The normal connection +* skips this step. */ CAS_CONNECT_DONE, + };
Signature · 1 line
2.37.1 (Apple Git-137.1)
This fixes the "tls/p2p reconnect with DCO breaks" problem that has haunting us for the last months, and does not break anything else - subjected to excessive client/server testing on Linux with/without DCO, FreeBSD with/without DCO, and things look mostly good now.
This is:
- on *Linux*, all p2p reconnect problems are gone.
- on *FreeBSD*, I can see that it instanciates a new peer, but ping echo reply packets never arrive at the client - I assume that this is due to ovpn(4) having no p2p mode, so "kernel goes multipoint, and is confused about IP/peer-id mapping" - we might need a "delete peer" call, or kernel-side fixes.
It *also* fixes the long-standing P2P NCP reconnection issue where "connect with AES-256-GCM, ctrl-c, reconnect with only BF-CBC" would lead to a confused peers (without any DCO involved). Now, this just works. Party!
I wouldn't claim to understand all the fine grained details, but the general approach "take note on reconnect that parts of do_up() need to be redone, and later do that" seems logical, and the code is fairly non-hacky.
I've taken the liberty to fix a few more comments ("wihout pull" etc).
Your patch has been applied to the master branch.
commit 6c24767aa5e068ba8a4328c9efec1c01d43d6d9f
Author: Arne Schwabe Date: Wed Nov 30 17:57:05 2022 +0100
Introduce connection state for reconnecting peer in p2p
Signed-off-by: Arne Schwabe <[email protected]...>
Acked-by: Gert Doering <[email protected]...>
Message-Id: <[email protected]...>
URL: https://www.mail-archive.com/[email protected]/msg25595.html
Signed-off-by: Gert Doering <[email protected]...>--
kind regards,
Gert Doering