Your message dated Wed, 18 May 2005 16:28:55 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#295968: xinetd: Can't make xinetd listen on more than 1
specified IP
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 maintonly) by bugs.debian.org; 19 Feb 2005 11:48:03 +0000
>From [EMAIL PROTECTED] Sat Feb 19 03:48:02 2005
Return-path: <[EMAIL PROTECTED]>
Received: from (ADSLGate.WG) [212.117.93.205]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1D2T5e-0000CG-00; Sat, 19 Feb 2005 03:48:02 -0800
Received: from rabe by ADSLGate.WG with local (Exim 3.35 #1)
id 1D2T5b-0005wy-00; Sat, 19 Feb 2005 12:47:59 +0100
From: "Ralf G. R. Bergs" <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: xinetd: Can't make xinetd listen on more than 1 specified IP
X-Mailer: reportbug 1.50
Date: Sat, 19 Feb 2005 12:47:59 +0100
Message-Id: <[EMAIL PROTECTED]>
Sender: "Ralf G. R. Bergs,,," <[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-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: xinetd
Version: 1:2.3.4-1.2
Severity: wishlist
For security reasons, I'd like to make xinetd listen only on my
two internal interfaces. However, it's only possible to use "bind"
once, so I can only specify ONE internal interface.
I'd like to be able to specify multiple "bind" directives, or to
list more than one IP address in one bind line.
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux Server 2.4.26 #1 Sat Apr 17 18:26:22 CEST 2004 i586
Locale: LANG=C, LC_CTYPE=C
Versions of packages xinetd depends on:
ii dpkg 1.9.21 Package maintenance system for Deb
ii libc6 2.2.5-11.8 GNU C Library: Shared libraries an
ii libwrap0 7.6-9 Wietse Venema's TCP wrappers libra
ii netbase 4.07 Basic TCP/IP networking system
---------------------------------------
Received: (at 295968-done) by bugs.debian.org; 18 May 2005 14:28:57 +0000
>From [EMAIL PROTECTED] Wed May 18 07:28:57 2005
Return-path: <[EMAIL PROTECTED]>
Received: from itesec.hsc.fr [192.70.106.33]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DYPXc-0002iC-00; Wed, 18 May 2005 07:28:57 -0700
Received: from carioca.hsc.fr (carioca.hsc.fr [192.70.106.67])
by itesec.hsc.fr (Postfix) with ESMTP
id DA52D21557; Wed, 18 May 2005 16:28:55 +0200 (CEST)
Received: by carioca.hsc.fr (Postfix, from userid 1000)
id 9F7287422E; Wed, 18 May 2005 16:28:55 +0200 (CEST)
Date: Wed, 18 May 2005 16:28:55 +0200
From: Thomas Seyrat <[EMAIL PROTECTED]>
To: "Ralf G. R. Bergs" <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
Subject: Re: Bug#295968: xinetd: Can't make xinetd listen on more than 1
specified IP
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
Organization: Debian Project
X-Operating-System: Debian/GNU/* 3.1 - Linux 2.6.11.7 ppc
X-GPG-Fingerprint: B26A 9FE7 83DD 721C 90F8 9B5E F38E 02FC 07AC F6FA
User-Agent: Mutt/1.5.9i
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-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
X-Spam-Level:
[ Sorry for the delay :) ]
On February 19, 12:47 (+0100), Ralf G. R. Bergs wrote:
> I'd like to be able to specify multiple "bind" directives, or to
> list more than one IP address in one bind line.
This is not supported upstream. As a workaround you can use several
service definitions with the different bind adresses. For instance:
service ftp
{
socket_type = stream
wait = no
user = root
instances = 10
log_on_success += DURATION HOST
log_on_failure += HOST
bind = 192.168.1.1
}
service ftp
{
socket_type = stream
wait = no
user = root
instances = 10
log_on_success += DURATION HOST
log_on_failure += HOST
bind = 192.168.1.2
}
Cheers,
--
Thomas Seyrat
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
