on Fri, Jul 08, 2005 at 07:28:23AM +0000, Malthe Borch ([EMAIL PROTECTED]) wrote: > Hello ng, --- > > Recently our firewall (running debian woody testing) began having > difficulties on the outbound uplink, injecting lots of these errors into > the syslog: > > Jul 7 22:43:30 localhost kernel: Neighbour table overflow. > > It's quite serious, because at the same time, in timeslots of approx. a > minute I get these fallouts: > > vladka:/var/log# ping www.uni-c.dk > connect: No buffer space available > > The fallouts typically last 2-3 minutes, and as far as I can see they're > not exclusive, i.e. it can happen to one destination and not another. > > Also, it doesn't seem to have anything to do with iptables. > > I have no idea how to proceed. Could it be a hardware failure?
You've managed to disable your loopback network device and/or nuke its config from /etc/network/interfaces. You should have the following lines in this file: ------------------------------------------------------------------------ # The loopback interface auto lo iface lo inet loopback ------------------------------------------------------------------------ ...ensure these exist. Run 'ifup lo' (as root). Running 'ifconfig lo' should return something like the following, with the starred line being critical. If you don't have a network address (127.0.0.1) there, you've got a problem: lo Link encap:Local Loopback * inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:3518761 errors:0 dropped:0 overruns:0 frame:0 TX packets:3518761 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:778152216 (742.1 MiB) TX bytes:778152216 (742.1 MiB) Peace. -- Karsten M. Self <kmself@ix.netcom.com> http://kmself.home.netcom.com/ What Part of "Gestalt" don't you understand? D00D PL33Z 1 N33D CH347 C0D35 FOR GC0NF !!!
signature.asc
Description: Digital signature