You're welcome.
In case I was too cryptic, that was the cause of your "neighbour table overflow" errors. It wasn't a driver bug, a hardware error, hub or switch negotiation, RIP malfunctions, frame collisions, or cabling problems. Yes, it was an overflowing ARP table, but that was in turn just a result of the underlying cause: /dev/lo being invalid.
Rick Moen
rick@linuxmafia.com