______ ______________ c me 4 movies _________________
\ DAVID AUGSBURGER edit e-mail address
Ok... I don't really have any problems with my machine when it comes to
networking. However, I've noticed some strange behavior. First off, what
should the inet address for the local loopback device be? Mine is currently
at 127.0.0.0. I remember reading somewhere that this was a Bad Thing.
However, I can telnet to 127.0.0.0 just fine. Here is my ifconfig:
lo Link encap:Local Loopback
inet addr:127.0.0.0 Bcast:127.255.255.255 Mask:255.0.0.0
UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
RX packets:89 errors:0 dropped:0 overruns:0
TX packets:89 errors:0 dropped:0 overruns:0
However, localhost in my /etc/hosts is defined as 127.0.0.1. As follows:
cerebus:~/$ cat /etc/hosts
127.0.0.1 cerebus.bellatlantic.net cerebus
So I can also telnet to 127.0.0.1 as well. And when I telnet to 127.0.0.1,
the number of packets transmitted and recieved changes for my loopback. So
it appears that the loopback device is at 127.0.0.0 AND 127.0.0.1. Is this
correct? If not, what am I doing incorrectly?
3. Which is correct for loopback, 127.0.0.0 or 127.0.0.1?
5. LinuxPPC kernel 2.1.127 versus Linux kernel 2.1.129?
6. Network timeouts on suse 9.3 after upgrade from 9.1
7. 2.4.20-rc1-ac1 kernel BUG at page_alloc.c:127!
8. What does the future look like for more advanced file systems on FBSD?
9. Kernel only accepts keys 1..127
10. Kernel 2.1.127 and BootX 1.0b6 problems...
11. kernel 2.1.127 power off problem
12. AsanteFast 10/100 NIC under LinuxPPC w/ 2.1.127 kernel
13. CDROM problems with kernels >= 2.1.11x (With 2.1.127 as well)