X2Go Bug report logs - #1594
X2Go Windows Client fails to connect to hostname resolving to both IPv4 and IPv6

Package: x2goclient; Maintainer for x2goclient is X2Go Developers <x2go-dev@lists.x2go.org>; Source for x2goclient is src:x2goclient.

Reported by: me@jcn50.com

Date: Thu, 24 Nov 2022 16:35:02 UTC

Severity: normal

Merged with 1592, 1593

Full log


Message #5 received at submit@bugs.x2go.org (full text, mbox, reply):

Received: (at submit) by bugs.x2go.org; 24 Nov 2022 16:30:21 +0000
From me@jcn50.com  Thu Nov 24 17:30:19 2022
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=0.7 required=3.0 tests=BAYES_50,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,SPF_HELO_NONE,URIBL_BLOCKED autolearn=ham
	autolearn_force=no version=3.4.2
Received: from first-ie.quantumhosting.cloud (first-ie.quantumhosting.cloud [52.212.242.166])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 5D0A55DA7F
	for <submit@bugs.x2go.org>; Thu, 24 Nov 2022 17:30:19 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=jcn50.com;
	s=default; h=Content-Transfer-Encoding:Content-Type:Message-ID:Subject:To:
	From:Date:MIME-Version:Sender:Reply-To:Cc:Content-ID:Content-Description:
	Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:
	In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe:
	List-Post:List-Owner:List-Archive;
	bh=0A4N5n8oWEN3O7DQgS/I7f/+3nNZft3T5Cq5M4hNDm0=; b=raSCLDUFm+3IBmqAt3kKlchQVh
	qG5i1hYNHLew5yu1Ac7hIu5p5n57Hw7GUHpltr0PRC6+pnUDhZzZ0wO94TXyG/mza4VkFSTF+N9DJ
	r7g6PbJGlqBEsEfGFkuuyH+/ETGldUtZzeq6pk5U6hAt3TtkZDGK2lXmqJFw43PuLf6vKUpSdoSJC
	uYdMo1AoMRWznqtrbOK6NzocKSGxqNKDP5SwbJYmJ+dUr8hQ3znjl7IhwLpokqlu1NQl62ALf2hxH
	f1bmqZo2AYpI+SBEZqkQxKf97uh6i1e9zUM9l0qlCmmar/YtgLbdS/kiVi5OHZGGcqR8JNin5uStA
	eSIR6StQ==;
Received: from [::1] (port=43010 helo=first-ie.quantumhosting.cloud)
	by first-ie.quantumhosting.cloud with esmtpa (Exim 4.95)
	(envelope-from <me@jcn50.com>)
	id 1oyF7F-005SsY-Bb
	for submit@bugs.x2go.org;
	Thu, 24 Nov 2022 16:30:18 +0000
MIME-Version: 1.0
Date: Thu, 24 Nov 2022 16:30:18 +0000
From: me@jcn50.com
To: submit@bugs.x2go.org
Subject: X2Go Windows Client fails to connect to hostname resolving to both
 IPv4 and IPv6
User-Agent: Roundcube Webmail/1.5.2
Message-ID: <848bd51d229e2c5929c61ea5c00927d9@jcn50.com>
X-Sender: me@jcn50.com
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - first-ie.quantumhosting.cloud
X-AntiAbuse: Original Domain - bugs.x2go.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jcn50.com
X-Get-Message-Sender-Via: first-ie.quantumhosting.cloud: authenticated_id: me@jcn50.com
X-Authenticated-Sender: first-ie.quantumhosting.cloud: me@jcn50.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Package: X2Go Windows Client
Version: 4.1.2.2

I have a hostname that has both 1x IPv4 address (A records) and 1x IPv6 
address (AAAA records). The client fails to connect (connection timeout 
error exact message: "Timeout connecting to $HOSTNAME") if I use the 
hostname. However if I enter the IPv4 or the IPv6 instead of the 
hostname: it works!

Proposed solution: it should try to connect/resolve to the IPv6 first, 
then the IPv4.

Regards,
Chris.


Send a report that this bug log contains spam.


X2Go Developers <owner@bugs.x2go.org>. Last modified: Thu Mar 28 11:54:20 2024; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.