After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 357971 - aliases hostname to 127.0.0.1 unconditionally
aliases hostname to 127.0.0.1 unconditionally
Status: RESOLVED WONTFIX
Product: gnome-system-tools
Classification: Deprecated
Component: network-admin
2.15.x
Other Linux
: Normal normal
: ---
Assigned To: Carlos Garnacho
Carlos Garnacho
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2006-09-27 14:24 UTC by Vassilis Pandis
Modified: 2012-11-24 20:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Vassilis Pandis 2006-09-27 14:24:40 UTC
Hello,

this is a bug reported by an Ubuntu user. You can find the original bug report at http://launchpad.net/bugs/24874 :

"I want to use my laptop as a server in a couple of different locations. In each
of these locations, it gets a different IP address and knows a different set of
static hosts, but has the same hostname. The services I run (a certain
implementation of JavaSpaces) rely on the hostname, and it being aliased to the
network IP address.

So, the most natural thing for me to do is define the right locations, and just
switch between them using network-admin. This results in errors, because
network-admin aliases hostname to 127.0.0.1 unconditionally -- Some of the
services send the hostname's IP address to clients for further communication,
and 127.0.0.1 is not the right address.

I've researched enough (and can read enough Perl) to see that the culprit code
is in network.pl, circa line 4000 -- the function
gst_network_ensure_loopback_statichost. I don't know enough Perl to fix it.

What I'd like to see is: if the hostname is already defined as a static host,
don't add it to the loopback interface."


Thanks in advance,
Comment 1 André Klapper 2012-11-24 20:29:08 UTC
According to its developer(s), gnome-system-tools is not under active development anymore. Functionality has been mostly integrated into GNOME Control Center / "[System] Settings".

It is unlikely that there will be any further active development.

Closing this report as WONTFIX as part of Bugzilla Housekeeping - Please feel
free to reopen this bug report in the future if anyone takes the responsibility
for active development again.