From 2fab9f06a5870944c4ce58bb5812c41879debc36 Mon Sep 17 00:00:00 2001 From: Dimitri Papadopoulos <3350651-DimitriPapadopoulos@users.noreply.gitlab.com> Date: Wed, 6 Apr 2022 09:49:30 +0200 Subject: [PATCH] Adjust verbosity level of Fortinet-related logging iBecause these messages do not convey an actual error status, use PRG_INFO instead of PRG_ERR. Signed-off-by: Dimitri Papadopoulos <3350651-DimitriPapadopoulos@users.noreply.gitlab.com> --- fortinet.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fortinet.c b/fortinet.c index bd422c88..f0c97a2a 100644 --- a/fortinet.c +++ b/fortinet.c @@ -394,12 +394,12 @@ static int parse_fortinet_xml_config(struct openconnect_info *vpninfo, char *buf check_ip_src = atoi(s); if (!xmlnode_get_prop(xml_node, "tun-user-ses-timeout", &s)) dropped_session_cleanup = atoi(s); - vpn_progress(vpninfo, PRG_ERR, + vpn_progress(vpninfo, PRG_INFO, _("Server reports that reconnect-after-drop is allowed within %d seconds, %s\n"), dropped_session_cleanup, check_ip_src ? _("but only from the same source IP address") : _("even if source IP address changes")); } else - vpn_progress(vpninfo, PRG_ERR, + vpn_progress(vpninfo, PRG_INFO, _("Server reports that reconnect-after-drop is not allowed. OpenConnect will not\n" "be able to reconnect if dead peer is detected. If reconnection DOES work,\n" "please report to \n")); -- 2.49.0