On 3/3/07, Mark Ryden <markryde@xxxxxxxxx> wrote:
Hi Mulyadi , 1) It works also after "ifdown lo". 2) I also tried setting "inet addr:128.0.0.1 Mask:255.0.0.0" in /etc/sysconfig/network-scripts/ifcfg-nic and than "ping 128.0.0.1" and it also send a resoonse to ping. So my question is still the same : who does answer me ? there is no handling of recieve interrupts in that module. What causes the packet which is sent to 128.0.0.1 to give this answer ? where is this mechanism implemented in the kernel ?
Though I'm no linux networking internals expert, yet I read a thread some time back: http://www.mail-archive.com/linux-net@xxxxxxxxxxxxxxx/msg00985.html The crux of the thread was, that instead of tying the IP addresses to the INTERFACE (eth0 / lo etc), Linux actually associates the IP address with the SYSTEM itself. So if you ping for an IP address that belongs to the machine itself, the request will never go to the driver. Rather, a layer above the driver will take care of it. I hope it helps, Rajat -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
