Your message dated Mon, 28 Nov 2005 12:54:13 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#338954: when 2 tinc node have the same name ping is longer
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 14 Nov 2005 01:35:17 +0000
>From [EMAIL PROTECTED] Sun Nov 13 17:35:17 2005
Return-path: <[EMAIL PROTECTED]>
Received: from 81-174-32-47.f5.ngi.it ([81.174.32.47] helo=chiapas.alca.le.it)
by spohr.debian.org with esmtp (Exim 4.50)
id 1EbTFd-0000vr-JE
for [EMAIL PROTECTED]; Sun, 13 Nov 2005 17:35:17 -0800
Received: by chiapas.alca.le.it (Postfix, from userid 1000)
id F064F200E76; Mon, 14 Nov 2005 02:35:13 +0100 (CET)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: ripley <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: when 2 tinc node have the same name ping is longer
X-Mailer: reportbug 3.8
Date: Mon, 14 Nov 2005 02:35:13 +0100
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: tinc
Version: 1.0.3-4
Severity: normal
In the deployment of a tinc-based network 2 node may have the same
name if they are connected to the vpn with different vpn entry point
(a tinc "server" connected to the vpn).
This setup don't generate any error but the ping became
slower (as all the routing in general) so some connection
became unstable.
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.27-2-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages tinc depends on:
ii debconf 1.4.30.13 Debian configuration management sy
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii liblzo1 1.08-1.2 A real-time data compression libra
ii libssl0.9.7 0.9.7e-3 SSL shared libraries
ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime
-- debconf information:
* tinc/restart_on_upgrade: false
---------------------------------------
Received: (at 338954-done) by bugs.debian.org; 28 Nov 2005 11:54:14 +0000
>From [EMAIL PROTECTED] Mon Nov 28 03:54:14 2005
Return-path: <[EMAIL PROTECTED]>
Received: from postduif.warande.net ([145.97.193.212])
by spohr.debian.org with esmtp (Exim 4.50)
id 1EghaI-0003uu-Eb
for [EMAIL PROTECTED]; Mon, 28 Nov 2005 03:54:14 -0800
Received: from 163pc223.sshunet.nl (163pc223.sshunet.nl [145.97.223.163])
by postduif.warande.net (Postfix) with ESMTP id 726B017B4B1;
Mon, 28 Nov 2005 12:54:13 +0100 (CET)
Received: from xar.sliepen.oi ([EMAIL PROTECTED] [127.0.0.1])
by xar.sliepen.oi (8.13.5/8.13.5/Debian-3) with ESMTP id jASBsD3n001243
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
Mon, 28 Nov 2005 12:54:13 +0100
Received: (from [EMAIL PROTECTED])
by xar.sliepen.oi (8.13.5/8.13.5/Submit) id jASBsD6E001242;
Mon, 28 Nov 2005 12:54:13 +0100
Date: Mon, 28 Nov 2005 12:54:13 +0100
From: Guus Sliepen <[EMAIL PROTECTED]>
To: ripley <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#338954: when 2 tinc node have the same name ping is longer
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="rmUrFcWP4LYae1gV"
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
X-oi: oi
User-Agent: Mutt/1.5.11
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
--rmUrFcWP4LYae1gV
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Nov 14, 2005 at 08:39:26AM +0100, Guus Sliepen wrote:
> > In the deployment of a tinc-based network 2 node may have the same
> > name if they are connected to the vpn with different vpn entry point
> > (a tinc "server" connected to the vpn).
> >=20
> > This setup don't generate any error but the ping became
> > slower (as all the routing in general) so some connection
> > became unstable.
>=20
> The manpage tinc.conf(5) says: "Each tinc daemon should have a name that
> is unique in the network which it will be part of." Tinc does see it as
> an error if two tinc daemons have the same name, but there is no way to
> resolve the issue. Both tinc daemons will start fighting for their
> resources, broadcasting their claims to all other daemons. This is what
> causes all daemons to slow down. The solution is to follow the manpage
> and make sure each tinc daemon is uniquely named.
Since I believe this is not a bug in tinc, and you haven't responded, I
am closing this bug. If you disagree, please reopen this bug and
elaborate.
--=20
Met vriendelijke groet / with kind regards,
Guus Sliepen <[EMAIL PROTECTED]>
--rmUrFcWP4LYae1gV
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDiu/lAxLow12M2nsRAmm0AJ0UlNDh006HI59Yghme1oZKwTHWLwCgrPkx
5MzgS+3UR8+Bt3kFi/vH178=
=q7NI
-----END PGP SIGNATURE-----
--rmUrFcWP4LYae1gV--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
