Your message dated Sun, 5 Jun 2005 03:32:07 +1000 (EST)
with message-id <[EMAIL PROTECTED]>
and subject line Bug#311968: I'm sorry a problem of my ISP
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; 4 Jun 2005 14:08:37 +0000
>From [EMAIL PROTECTED] Sat Jun 04 07:08:37 2005
Return-path: <[EMAIL PROTECTED]>
Received: from (localhost.localdomain) [86.125.50.61]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DeZKG-0004H6-00; Sat, 04 Jun 2005 07:08:36 -0700
Received: from edwin by localhost.localdomain with local (Exim 4.44)
id 1DeZJi-0001rH-R4
for [EMAIL PROTECTED]; Sat, 04 Jun 2005 17:08:02 +0300
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Torok Edwin <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: apache2-common: can't be accessed from ipv4 clients in default
configuration
X-Mailer: reportbug 3.8
Date: Sat, 04 Jun 2005 17:08:02 +0300
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-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: apache2-common
Severity: important
Tags: patch
If I run apache2 using it's default config, it binds to the ipv6 address,
even though
I haven't set up an ipv6 connection (sit0 is down, only eth0, ppp0, and lo is
up).
Thus a client who knows only ipv4 (i.e. a windows user), cannot connect to
my server.
A possible fix to this problem is, that by default the file ports.conf should
contain this:
Listen 0.0.0.0:80
However I don't know what effect will this have on IPV6 connections. But
given the fact that
most often people will use ipv4 addresses on their servers, or at home, I think
that it would be
best to make the default configuration to bind to ipv4, and if somebody wishes
to use ipv6
he'll just have to change the config file. Of course this opinion could be
wrong.
The best in my opinion would be if it would accept connections on both ipv4
and ipv6,
but that's not happening in the default config.
In order for it to be accessed from ipv4, the postinstall script should be
changed like this
Instead of: echo "Listen 80" >> /etc/apache2/ports.conf
Should be: echo "Listen 0.0.0.0:80" >> /etc/apache2/ports.conf
So here is the patch file:
----------------BEGIN PATCH--------------------
--- apache2-common.postinst 2005-06-04 17:02:23.919988360 +0300
+++ ../../fix/apache2-2.0.54/debian/apache2-common.postinst 2005-06-04
17:04:06.111452896 +0300
@@ -17,7 +17,7 @@
NO_PORT_80=`$NETSTAT -lnt | awk '{print $4}' | grep ':80$'` || true
if [ -n "$NO_AF_INET" -o -n "$NO_PORT_80" ]; then
echo "NO_START=1" >> /etc/default/apache2
- echo "Listen 80" >> /etc/apache2/ports.conf
+ echo "Listen 0.0.0.0:80" >> /etc/apache2/ports.conf
if [ -n "$NO_AF_INET" ]; then
echo "netstat is unable to query the state of your
listening TCP ports. This could be because you don't have TCP support in your
kernel (unlikely), or because you do not have the /proc filesystem mounted. To
be on the safe side, we're assuming that port 80 is in use."
fi
----------------CUT HERE-----------------------
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-k7
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
---------------------------------------
Received: (at 311968-done) by bugs.debian.org; 4 Jun 2005 17:32:38 +0000
>From [EMAIL PROTECTED] Sat Jun 04 10:32:38 2005
Return-path: <[EMAIL PROTECTED]>
Received: from loki.0c3.net [69.0.240.48]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DecVi-0006Z3-00; Sat, 04 Jun 2005 10:32:38 -0700
Received: from localhost
([127.0.0.1] helo=mail.0c3.net ident=www-data)
by loki.0c3.net with esmtp (Exim 4.34)
id 1DecVD-0000w5-30
for [EMAIL PROTECTED]; Sat, 04 Jun 2005 11:32:07 -0600
Received: from 203.49.196.168
(SquirrelMail authenticated user adconrad)
by mail.0c3.net with HTTP;
Sun, 5 Jun 2005 03:32:07 +1000 (EST)
Message-ID: <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Date: Sun, 5 Jun 2005 03:32:07 +1000 (EST)
Subject: Re: Bug#311968: I'm sorry a problem of my ISP
From: "Adam Conrad" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
User-Agent: SquirrelMail/1.5.1 [CVS]
MIME-Version: 1.0
Content-Type: text/plain;charset=UTF-8
Content-Transfer-Encoding: 8bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: [EMAIL PROTECTED]
X-SA-Exim-Scanned: No (on loki.0c3.net); SAEximRunCond expanded to false
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=-5.0 required=4.0 tests=BAYES_01,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Torok Edwin wrote:
>
> It seems it all was a problem with my ISP.
Closing, then.
... Adam
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
