Your message dated Sun, 10 Jan 2016 19:39:37 +0100
with message-id <[email protected]>
and subject line Re: Bug#617268: Acknowledgement (ifupdown: network servers do
not listen on 127.0.1.1)
has caused the Debian Bug report #617268,
regarding ifupdown: network servers do not listen on 127.0.1.1
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
617268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617268
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ifupdown
Version: 0.6.8ubuntu29.2
Severity: normal
I opened a ubuntu bug against ifupdown 8 months ago, and supplied a fix.
Despite the issue turning up
in questions, it has not been passed upstream to the debian maintainers of the
package. Therefore,
I am trying to do it myself.
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/604283
Briefly: when http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=316099 was
fixed, it changed the
assignment of the hostname in /etc/hosts to the ip address 127.0.1.1. However,
this ip address is
never assigned to a local interface. Any server process that tries to listen on
all interfaces will
not know it should listen on 127.0.1.1. Any client that tries to connect to a
local server using the
hostname will timeout (although "localhost" will work).
My solution is to make ifupdown.nw create a virtual interface lo:0 with the
address 127.0.1.1 immediately
after creating lo with the address 127.0.0.1. (and take it down before lo).
My suggested patch was generated against the latest debian sid source for
ifupdown-0.6.10.
--- original//ifupdown.nw 2011-03-05 20:01:09.000000000 +0000
+++ briansPatch//ifupdown.nw 2011-03-05 20:02:29.000000000 +0000
@@ -3887,11 +3887,13 @@
This method may be used to define the IPv4 loopback interface.
up
- ifconfig %iface% 127.0.0.1 up
+ ifconfig %iface% 127.0.0.1 up
+ ifconfig %iface%:0 127.0.0.1 up
route add -net 127.0.0.0 if ( mylinuxver() < mylinux(2,1,100) )
down
- ifconfig %iface% down
+ ifconfig %iface%:0 down
+ ifconfig %iface% down
@
<<inet methods>>=
-- System Information:
Debian Release: squeeze/sid
APT prefers lucid-updates
APT policy: (500, 'lucid-updates'), (500, 'lucid-security'), (500, 'lucid')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-29-generic (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages ifupdown depends on:
ii debconf [debconf-2.0] 1.5.28ubuntu4 Debian configuration management sy
ii libc6 2.11.1-0ubuntu7.8 Embedded GNU C Library: Shared lib
ii lsb-base 4.0-0ubuntu8 Linux Standard Base 4.0 init scrip
ii net-tools 1.60-23ubuntu2 The NET-3 networking toolkit
ii netbase 4.35ubuntu3 Basic TCP/IP networking system
ii upstart [upstart-job] 0.6.5-8 event-based init daemon
ifupdown recommends no packages.
Versions of packages ifupdown suggests:
ii dhcp3- 3.1.3-2ubuntu3 DHCP client
ii iprout 20091226-1 networking and traffic control too
ii ppp 2.4.5~git20081126t100229-0ubuntu3 Point-to-Point Protocol (PPP) - da
-- debconf information excluded
--- End Message ---
--- Begin Message ---
I'm closing this bug, since I don't think this has been an issue for the
last several years. If I'm wrong, feel free to reopen the bug and
elaborate.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <[email protected]>
signature.asc
Description: Digital signature
--- End Message ---
