I'm disappointed that my fix hasn't been implemented yet. I suppose most
people running local tcpip servers have already kludged their hosts
files and so don't encounter this problem...

Local clients that connect to "standard" local servers (such as bind and
ntpd) seem to historically hardcode either "localhost" or "127.0.0.1" as
the address of their local server. This works because the ubuntu/debian
default /etc/hosts file defines 127.0.0.1 as localhost and so the
definition will be available no matter what the network interfaces might
look like at the time.

However, any client that takes a less stone-age approach (especially
java programs) will use their own hostname to address their local
server. The new-format default hosts file will ALWAYS resolve the local
hostname to 127.0.1.1. UNLESS we provide an interface that corresponds
to this "new" local address, the server will never know it should be
listening on that address! My fix defines a secondary address for the
loopback interface, so the local server will discover it and listen on
it.

Since opening this bug, ifupdown-0.6.8ubuntu29.1 has been released and
it still does not implement my fix. Therefore, I have attached an
improved patch for the latest version of the package. Please would
someone apply it?

-- 
network servers do not listen on 127.0.1.1
https://bugs.launchpad.net/bugs/604283
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to