From: Joseph Morales on
We're experimenting with deploying SUSE 10 SP3 systems and adding them to a
Windows domain and DNS. Oddly, when we register in DNS, it gets registered
under two address: the real IP address, and the address 127.0.0.2. Also, an
ip addr command shows that the loopback device lo has two addresses:
127.0.0.1 and 127.0.0.2.

The above behavior is just on SP3. On SUSE 10 SP2, the lo device has only
the 127.0.0.1 address, and the system is able to register correctly in DNS.

Has anyone ever seen this behavior? Do you know what the 127.0.0.2 address
signifies, or how to get rid of it?

Thanks, Joseph


From: Vlad_Inhaler on
On Apr 20, 1:33 am, "Joseph Morales" <joseph.mora...(a)unisys.com>
wrote:
> We're experimenting with deploying SUSE 10 SP3 systems and adding them to a
> Windows domain and DNS. Oddly, when we register in DNS, it gets registered
> under two address: the real IP address, and the address 127.0.0.2. Also, an
> ip addr command shows that the loopback device lo has two addresses:
> 127.0.0.1 and 127.0.0.2.
>
> The above behavior is just on SP3. On SUSE 10 SP2, the lo device has only
> the 127.0.0.1 address, and the system is able to register correctly in DNS.
>
> Has anyone ever seen this behavior? Do you know what the 127.0.0.2 address
> signifies, or how to get rid of it?
>
> Thanks, Joseph

Firstly, so do I. I have two network cards and the following entries
in /etc/hosts:
127.0.0.1 localhost
127.0.0.2 machine.mydomain machine
192.168.1.2 machine machine
192.168.1.3 othermachine.mydomain othermachine
192.168.1.11 laptop.mydomain laptop
(ok, I lie - names and ip-addresses changed because I felt like it)

I do not have any problems here, Samba, NFS and IP-Forwarding to the
'net all work fine. 'machine' also acts as a bind caching server, I
don't use Windows domains.

One other point, alt.os.linux.suse is the english-language group, this
one is 99% German language. Not that anyone is unhappy with your
presence :-)
From: Joseph Morales on
Thanks, G�nther and Joe.

"G�nther Schwarz" <strap(a)gmx.de> wrote in message
news:8369j4F5j6U1(a)mid.individual.net...
> Simply edit the /etc/hosts file. Could you post the local part of this
> file as well as the output of 'ping localhost'?

It turns out that editing the /etc/hosts file doesn't help this particular
problem. However, I received a suggestion from another friend that did the
trick. I edited the /etc/sysconfig/network/ifcfg-lo file and deleted the
entry for 127.0.0.2. Then I did a service network restart and was able to do
the dns register. This time the system registered with only the correct
address.

After that I restored the 127.0.0.2 address to the ifcfg-lo file again and
once more restarted the network service. So the 127.0.0.2 loopback is still
available if some app needs it some day.

Regards, Joseph