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 ? Regards, Mark On 3/2/07, Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx> wrote:
Hi ... > > Now what I do not understand is: > when I ran > ping 127.0.0.2 > I got: > PING 127.0.0.2 (127.0.0.2) 56(84) bytes of data. > 64 bytes from 127.0.0.2: icmp_seq=1 ttl=64 time=0.046 ms > 64 bytes from 127.0.0.2: icmp_seq=2 ttl=64 time=0.040 ms > > who does answer me ? there is no handling of recieve interrupts in > that module. > What causes the packet which is sent to 127.0.0.2 to give this answer ? > where is this mechanism implemented in the kernel ? A speculation you can consider.... it could be the interface "lo" that is replying. IIRC, every address that begins with 127. prefix is actually understood by the OS network stack as request to "chat" with the default loop back address. You may try it by yourself, try something like this while you nic module isn't loaded: ping 127.1.1.1 ping 127.1.2.3 and so on. So, assuming I am right, try to down the "lo" interface 1st and see if you get your nic module running as expected. regards, Mulyadi
-- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
