[ale] Name resolutoin in the WM (fixed)

[Michael B. Trausch]

JK wrote:
> Michael B. Trausch wrote:
>>
>> Anybody know what the 127.0.1.1 is there for?  The file was
>> automatically generated by the setup program... but it is not associated
>> with any addresses on any interfaces, and yet answers pings from
>> localhost.  Confused.
> 
> Just out of curiosity, what's the output of "ip addr list lo"?
> You may have an alias on that interface.
> 

fd0man at pepper:~[0]$ ip addr list lo
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
fd0man at pepper:~[0]$ ifconfig lo
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:29 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2164 (2.1 KiB)  TX bytes:2164 (2.1 KiB)

fd0man at pepper:~[0]$

Does not appear to have any aliases.  Just to make sure that I was
reading the output correctly, I aliased my ath0 interface:

fd0man at pepper:~[1]$ ifconfig
ath0      Link encap:Ethernet  HWaddr 00:11:F5:E4:1D:5C
          inet addr:192.168.0.101  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::211:f5ff:fee4:1d5c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:27408 errors:39042 dropped:0 overruns:0 frame:39042
          TX packets:31863 errors:8 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:200
          RX bytes:6867532 (6.5 MiB)  TX bytes:2974954 (2.8 MiB)
          Interrupt:217 Memory:e0260000-e0270000

ath0:0    Link encap:Ethernet  HWaddr 00:11:F5:E4:1D:5C
          inet addr:192.168.0.194  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:217 Memory:e0260000-e0270000

fd0man at pepper:~[0]$ ip addr list ath0
9: ath0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 200
    link/ether 00:11:f5:e4:1d:5c brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.101/24 brd 192.168.0.255 scope global ath0
    inet 192.168.0.194/24 brd 192.168.0.255 scope global secondary ath0:0
    inet6 fe80::211:f5ff:fee4:1d5c/64 scope link
       valid_lft forever preferred_lft forever
fd0man at pepper:~[0]$

So, no, no aliases on the 'lo' interface.  Even more confusing to me.

>
> IIRC there used to be a prominent warning in Slackware's
> default /etc/hosts, to the effect that if any host name
> but "localhost" was assigned to 127.0.0.1, then a variety
> of things would break.  Unfortunately, I don't recall the
> details, and don't have immediate access to a Slackware box.
> Anyway, it's possible FC5 is assigning the 127.0.1.1
> address (as well as 127.0.0.1) to lo in order to avoid
> that scenario.
> 

I remember that warning, though I always pretty well blatantly ignored
it.  :-)  I never suffered any breakage, at least that I can recall.

	- Mike

-- 
"Fate: Protects fools, children, and ships called /Enterprise/."
                               -- William T. Riker, ST:TNG, "Contagion"


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature