> i discover it was triggerd when i was doing a nmap on a class B network
> but i can't reproduce it
> and i haven't got an other error since my mail
> so i think is the nmap which makes so mut's arp call's that it is
> overflowing the arp table
It is pretty easy to overflow it. You should generate more than
2048 requests per arp resolution timeout (1sec) to dead hosts.
If you did this that time, then you achieved exactly the effect,
which you expected. 8) No extensions will help here, you hit natural
limit and the further increasing arp table size will result in complete
congestion of ethernet with broadcast ARPs.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
Please read the FAQ at http://www.tux.org/lkml/