Re: Random packets loss under x86_64 - routing?

linux-os
2005-01-17T14:27:56Z

On Mon, 17 Jan 2005, Peter Kruse wrote:

> Hello,
>
> thanks for your reply
>
> linux-os wrote:
> >
>> When they 'disappear', use `arp -d hostname` to delete the
>> entry from the ARP tables. Then see if you can ping it.
>> It is possible that the destination machine got re-routed
>> and the new router's HW address wasn't updated in the
>> ARP tables. If this is the case, I don't know hot to 'fix'
>> it, but it's a new data-point. When you have dynamic routing,
>> there needs to be some way to update the ARP tables even though
>> they eventually expire.
>
> There is no router between sender and destination host,
> they are on the same subnet and connected on the same switch.
>

I suggest that you may __think__ that there is no router.... But
for instance, I can't talk to my own printer here because
of some configuration changes made by the "Net Naz^M^M^M
Wizards" here. Same network, same wire. It gets "redirected".
Basically, everything on this wire is proxy-arped by the
default-route machine. There are duplicate packets on the
wire and redirections everywhere.

You can look at your ARP table with:

`cat /proc/net/arp`

>> The fact that `ping -r` works seems to show that the ARP table
>> has stale entries in it.
>>

The `ping -r` working shows that there were is either a bad
ARP table entry or too small a netmask so the device isn't
really on your network.

>
> Even directly after reboot when the arp table is empty?
>
> Peter
>

Just check it out. You'd be surprised what you may find.
Look at the ARP-table entry. Try to ping something that
doesn't respond. Look at the table again. That will tell
you what's happening. It's likely that there is an ARP
table entry from some 'router' that has been set to
proxy-ARP whatever it sees on the wire.

Cheers,
Dick Johnson
Penguin : Linux version 2.6.10 on an i686 machine (5537.79 BogoMips).
Notice : All mail here is now cached for review by Dictator Bush.
98.36% of all statistics are fiction.