Filip_Ruszkowski
asked on
Arp resolution problem
My problem is ... peculiar... So, I have a linux box (actually it's booted off floppies - bootdisk & rootdisk) and when I try to resolve an ip address (for instance I type: ping 195.116.101.80) nothing happens. I have put up a sniffer and I noticed that really weird arp request packets are being sent out, look at this:
eth src: 00:c0:13:14:15:16 (OK - my hw)
eth dst: FF:FF:FF:FF:FF:FF (OK - brdcst)
packet arp request (OK)
sender hw: 00:00:00:00:00:00 (?)
sender ip: 0.0.0.0 (?)
target hw: 00:00:00:00:00:00 (?)
target ip: 0.0.0.0 (?)
what the hell... ???
I usually just bring my interface up with a normal:
ifconfig eth0 195.116.101.1
the "noarp" flag is _not_ set. (even if it was no arp frames would have been sent). I have kernel version 2.2.6, and the distibution is slack 4.0. Honestly I don't know what the mechanism for resolving arp is (kernel? what syscall?). I have taken a look at /etc/nsswitch.conf - but it seems ok. I have no clue :( The worst thing is, that it was all working fine not long ago...
regards,
Filip
P.S. If I missed any important info, please let me know
PSS: I just realized at other times I get totaly random values like:
sender hw: 05 00 00 00 00 10
sender ip: 0.0.1.0
target hw: 00 00 e4 51 00 00
target ip: 228.97.0.0
I realize that something is messed up big time, if anyone can help, I'll be really glad!
eth src: 00:c0:13:14:15:16 (OK - my hw)
eth dst: FF:FF:FF:FF:FF:FF (OK - brdcst)
packet arp request (OK)
sender hw: 00:00:00:00:00:00 (?)
sender ip: 0.0.0.0 (?)
target hw: 00:00:00:00:00:00 (?)
target ip: 0.0.0.0 (?)
what the hell... ???
I usually just bring my interface up with a normal:
ifconfig eth0 195.116.101.1
the "noarp" flag is _not_ set. (even if it was no arp frames would have been sent). I have kernel version 2.2.6, and the distibution is slack 4.0. Honestly I don't know what the mechanism for resolving arp is (kernel? what syscall?). I have taken a look at /etc/nsswitch.conf - but it seems ok. I have no clue :( The worst thing is, that it was all working fine not long ago...
regards,
Filip
P.S. If I missed any important info, please let me know
PSS: I just realized at other times I get totaly random values like:
sender hw: 05 00 00 00 00 10
sender ip: 0.0.1.0
target hw: 00 00 e4 51 00 00
target ip: 228.97.0.0
I realize that something is messed up big time, if anyone can help, I'll be really glad!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Can you post the tcpdump output? You can run it on any of the machines you are testing it with.
ASKER
ehm...
First of all, I got it to work. I figured out the the problem lay on the kernel-bootdisk(kernel: 2.2.6). I tried /bootdisk1.44/net.i on the slackware distro and it worked with the same old rootdisk. I then recompiled the kernel several times (and put it on the bootdisk) and tried to match it to the net.i config file (/kernels/net.i/config). If I took the config straight from net.i it actually didn't compile. I then turned off math emulation and all the exprimental stuff and it did compile, I put on floppy booted, and what? - I got the same arp problem. I then compiled the 2.2.14 kernel (the same options turned on I had before) and it worked fine - so it is really hard to say what wqas going on I tested the problem on 2 different 3com cards and a Realtek which otherwise worked fine with linux.
So, thanx for the feedback, but I got it to work myself - still not knowing what the reason for this behavior was. The points go to kiffney. Well, I'm glad it's working :)
First of all, I got it to work. I figured out the the problem lay on the kernel-bootdisk(kernel: 2.2.6). I tried /bootdisk1.44/net.i on the slackware distro and it worked with the same old rootdisk. I then recompiled the kernel several times (and put it on the bootdisk) and tried to match it to the net.i config file (/kernels/net.i/config). If I took the config straight from net.i it actually didn't compile. I then turned off math emulation and all the exprimental stuff and it did compile, I put on floppy booted, and what? - I got the same arp problem. I then compiled the 2.2.14 kernel (the same options turned on I had before) and it worked fine - so it is really hard to say what wqas going on I tested the problem on 2 different 3com cards and a Realtek which otherwise worked fine with linux.
So, thanx for the feedback, but I got it to work myself - still not knowing what the reason for this behavior was. The points go to kiffney. Well, I'm glad it's working :)
ASKER
as said before, I'm glad it's working.