From: Jussi Laakkonen <jussi.laakkonen@jolla.com>
To: connman@lists.linux.dev
Subject: [PATCH 2/2] vpn: Handle ENOLINK error in connect callback
Date: Tue, 17 Aug 2021 18:14:43 +0300 [thread overview]
Message-ID: <20210817151443.32305-3-jussi.laakkonen@jolla.com> (raw)
In-Reply-To: <20210817151443.32305-1-jussi.laakkonen@jolla.com>
Add handling of ENOLINK error that is reported back by vpnd when a VPN
cannot be connected because connmand is in offline state. ENOLINK has
to be handled similarly to EINPROGRESS as it is not a real error in the
actual VPN connection.
---
plugins/vpn.c | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/plugins/vpn.c b/plugins/vpn.c
index d708d1ff..bc025c0c 100644
--- a/plugins/vpn.c
+++ b/plugins/vpn.c
@@ -491,6 +491,9 @@ static int errorstr2val(const char *error) {
if (g_strcmp0(error, CONNMAN_ERROR_INTERFACE ".AlreadyConnected") == 0)
return -EISCONN;
+ if (g_strcmp0(error, CONNMAN_ERROR_INTERFACE ".NoCarrier") == 0)
+ return -ENOLINK;
+
if (g_strcmp0(error, CONNMAN_ERROR_INTERFACE ".OperationCanceled") == 0)
return -ECANCELED;
@@ -538,7 +541,12 @@ static void connect_reply(DBusPendingCall *call, void *user_data)
if (err == -ECANCELED) {
DBG("%s connect canceled", data->path);
connman_provider_set_autoconnect(data->provider, false);
- } else if (err != -EINPROGRESS) {
+ /*
+ * ENOLINK (No carrier) is not an error situation but is caused
+ * by connman not being online when VPN is attempted to be
+ * connected.
+ */
+ } else if (err != -EINPROGRESS && err != -ENOLINK) {
connman_error("Connect reply: %s (%s)", error.message,
error.name);
DBG("data %p cb_data %p", data, cb_data);
--
2.20.1
next prev parent reply other threads:[~2021-08-17 15:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 15:14 [PATCH 0/2] Implement connmand state monitoring to vpnd Jussi Laakkonen
2021-08-17 15:14 ` [PATCH 1/2] vpn-provider: Implement connmand online state checking Jussi Laakkonen
2021-08-17 16:55 ` Daniel Wagner
2021-08-18 9:21 ` Jussi Laakkonen
2021-08-18 10:31 ` [PATCH v2 " Jussi Laakkonen
2021-08-19 12:11 ` Jussi Laakkonen
2021-08-19 12:30 ` Daniel Wagner
2021-08-19 12:38 ` Santtu Lakkala
2021-08-19 13:06 ` Daniel Wagner
2021-08-19 12:40 ` Jussi Laakkonen
2021-08-29 18:27 ` Daniel Wagner
2021-08-30 6:59 ` Jussi Laakkonen
2021-08-30 8:11 ` Daniel Wagner
2021-08-20 13:05 ` [PATCH v3 " Jussi Laakkonen
2021-08-17 15:14 ` Jussi Laakkonen [this message]
2021-08-20 13:06 ` [PATCH v2 2/2] vpn: Refactor connect_reply() and handle NoCarrier -> ENOLINK error Jussi Laakkonen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210817151443.32305-3-jussi.laakkonen@jolla.com \
--to=jussi.laakkonen@jolla.com \
--cc=connman@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).