Re: Neighbour table overflow (No buffer space available)
on Fri, Jul 08, 2005 at 07:28:23AM +, 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: loLink 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 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
Neighbour table overflow (No buffer space available)
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? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
neighbour table overflow, lo device is up
Hello, on my system, pentium with intel d845gbvl mainboard, 3com 3c905C-TX Fast Ethenet (module 3c59x) I get a lot of the following error messages: ... NET: 1044 messages suppressed. Neighbour table overflow. Neighbour table overflow. ... Loopback device is up and running. ifconfig shows: eth0 Link encap:Ethernet HWaddr 00:02:2E:F0:62:34 inet addr: xxx Bcast: xxx Mask:255.255.240.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:113730 errors:0 dropped:0 overruns:1 frame:0 TX packets:26685 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:17595330 (16.7 MiB) TX bytes:5291304 (5.0 MiB) Interrupt:11 Base address:0xdc00 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:3127 errors:0 dropped:0 overruns:0 frame:0 TX packets:3127 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:175868 (171.7 KiB) TX bytes:175868 (171.7 KiB) Changing the network card to an other type didn't help. Has anybody an idee? Any help is greatly appreciated, Christian -- Dr. Christian Hähnel Uni Mannheim, Seminar für Statistik, L7, 3-5 68163 Mannheim http://www.schall-und-rauch.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: neighbour table overflow
On Mar 05 2002, Gabriel Verhooghe wrote: > "neighbour table overflow". What is this about? It probably means that you don't have the loopback interface configured. See if "ifconfig -a" shows the lo interface (it should have the IP address 127.0.0.1). []s, Roger... -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Rogério Brito - [EMAIL PROTECTED] - http://www.ime.usp.br/~rbrito/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
neighbour table overflow
I installed Debian GNU/Linux 3.0 (pre). From time to time the kernel displays the following message on my terminal: "neighbour table overflow". What is this about?
Re: neighbour table overflow from woody install easily fixed
Paul Scott wrote: Hi, The subject says most of it. I have not even finished the dselect process of the install and I am getting "neighbour table overflow". /etc/network/interfaces has no entries at this point. Easily fixed by adding loopback. Thanks, Paul
neighbour table overflow from woody install
Hi, The subject says most of it. I have not even finished the dselect process of the install and I am getting "neighbour table overflow". /etc/network/interfaces has no entries at this point. TIA, Paul Scott
Re: SIOCSIFADDR & neighbour table overflow
On Fri, Feb 16, 2001 at 13:52:51 -0800, Michael K. O'Brien wrote: > % ifconfig lo 127.0.0.1 > SIOCSIFADDR: Bad file descriptor Known problem. Downgrade to the "net-tools" package from "Testing". HTH, Ray -- ART A friend of mine in Tulsa, Okla., when I was about eleven years old. I'd be interested to hear from him. There are so many pseudos around taking his name in vain. - The Hipcrime Vocab by Chad C. Mulligan
SIOCSIFADDR & neighbour table overflow
Hola~ I try to keep up with unstable (I run apt-get dist-upgrade about once a week). Anyway, after a power failure, my machine is not in a happy state. Trying to run ifconfig I receive: % ifconfig lo 127.0.0.1 SIOCSIFADDR: Bad file descriptor lo: unknown interface: Bad file descriptor Running "ifconfig -a" lists "lo" as a valid interface. I'm using the 3c59x driver. Which, for loopback, I wouldn't think would matter. Anyway, has anyone having problems? MO -- Michael O'Brien Tools Pixar [EMAIL PROTECTED] Censorship is the mother of metaphor. -Jorges Luis Borges
Re: [SOLVED] : Re: Linux tries to talk to nameserver when accessing localhost (was Re: neighbour table overflow with Woody)
"Eric G . Miller" wrote on 01/01/2001 (21:02) : > This would contradict the man page for host.conf which explicitly says > the arguments must be separated by commas. I tried it both ways and > found no difference for either local or remote lookups. However, I'm > not sure if /etc/nsswitch.conf doesn't obsolete this file... Either > way, it would seem to be at least a documentation bug for host.conf. Which version of libc6 are your running? Also according to: http://docs.rinet.ru:8080/LiSys/lsg30.htm There should be no comma or punctuation. The bug report has been diverted to the man pages :-) -- Preben Randhol --- http://www.pvv.org/~randhol/ -- «For me, Ada95 puts back the joy in programming.»
Re: [SOLVED] : Re: Linux tries to talk to nameserver when accessing localhost (was Re: neighbour table overflow with Woody)
On Mon, Jan 01, 2001 at 02:51:48PM +0100, Preben Randhol wrote: > > /etc/host.conf ??? > > > > order hosts,bind > > multi on > > It turns out that /etc/host.conf with > > order hosts bind > multi on > > works. > > NOTICE that there is no comma (or punctuation) between hosts and bind. > Otherwise it won't work. This would contradict the man page for host.conf which explicitly says the arguments must be separated by commas. I tried it both ways and found no difference for either local or remote lookups. However, I'm not sure if /etc/nsswitch.conf doesn't obsolete this file... Either way, it would seem to be at least a documentation bug for host.conf. -- Eric G. Miller
[SOLVED] : Re: Linux tries to talk to nameserver when accessing localhost (was Re: neighbour table overflow with Woody)
"Eric G . Miller" wrote on 31/12/2000 (01:32) : > On Sun, Dec 31, 2000 at 01:09:32AM +0100, Preben Randhol wrote: > > Preben Randhol <[EMAIL PROTECTED]> wrote on 30/12/2000 (21:57) : > > > Apparently I did something else as well as it stopped working :-( > > > > That is when I'm not on the net, the machine still tries to talk to the > > nameservers I have set up in resolv.conf when I write : > > netscape http://localhost/ > > and it then hangs for a long time as it cannot connect to the > > nameservers. > > > > If I write netscape http://127.0.0.1/ it works. > > > > # cat /etc/hosts > > 127.0.0.1 localhost localhost.localdomain > > > > # cat /etc/resolv.conf > > nameserver 193.212.1.11 > > nameserver 193.212.1.10 > > > > Any hints much appreciated! > > /etc/host.conf ??? > > order hosts,bind > multi on It turns out that /etc/host.conf with order hosts bind multi on works. NOTICE that there is no comma (or punctuation) between hosts and bind. Otherwise it won't work. -- Preben Randhol -- http://www.pvv.org/~randhol/ -- +---+ "There was, I think, never any reason to believe in any innate | ! | superiority of the male, except his superior muscle." +---+ -- Bertrand Russell, Ideas That Have Harmed Mankind (1950)
Re: Linux tries to talk to nameserver when accessing localhost (was Re: neighbour table overflow with Woody)
Preben Randhol <[EMAIL PROTECTED]> wrote on 31/12/2000 (01:44) : and nsswitch.conf : % cat nsswitch.conf # /etc/nsswitch.conf # # Example configuration of GNU Name Service Switch functionality. # If you have the `glibc-doc' and `info' packages installed, try: # `info libc "Name Service Switch"' for information about this file. passwd: compat group: compat shadow: compat hosts: files dns networks: files protocols: db files services: db files ethers: db files rpc:db files netgroup: nis -- Preben Randhol -- http://www.pvv.org/~randhol/ -- +---+ "There was, I think, never any reason to believe in any innate | ! | superiority of the male, except his superior muscle." +---+ -- Bertrand Russell, Ideas That Have Harmed Mankind (1950)
Re: Linux tries to talk to nameserver when accessing localhost (was Re: neighbour table overflow with Woody)
"Eric G . Miller" wrote on 31/12/2000 (01:32) : > On Sun, Dec 31, 2000 at 01:09:32AM +0100, Preben Randhol wrote: > > Preben Randhol <[EMAIL PROTECTED]> wrote on 30/12/2000 (21:57) : > > > Apparently I did something else as well as it stopped working :-( > > > > That is when I'm not on the net, the machine still tries to talk to the > > nameservers I have set up in resolv.conf when I write : > > netscape http://localhost/ > > and it then hangs for a long time as it cannot connect to the > > nameservers. > > > > If I write netscape http://127.0.0.1/ it works. > > > > # cat /etc/hosts > > 127.0.0.1 localhost localhost.localdomain > > > > # cat /etc/resolv.conf > > nameserver 193.212.1.11 > > nameserver 193.212.1.10 > > > > Any hints much appreciated! > > /etc/host.conf ??? > > order hosts,bind > multi on Sorry, yes it looks like that. -- Preben Randhol -- http://www.pvv.org/~randhol/ -- +---+ "There was, I think, never any reason to believe in any innate | ! | superiority of the male, except his superior muscle." +---+ -- Bertrand Russell, Ideas That Have Harmed Mankind (1950)
Re: Linux tries to talk to nameserver when accessing localhost (was Re: neighbour table overflow with Woody)
On Sun, Dec 31, 2000 at 01:09:32AM +0100, Preben Randhol wrote: > Preben Randhol <[EMAIL PROTECTED]> wrote on 30/12/2000 (21:57) : > > Apparently I did something else as well as it stopped working :-( > > That is when I'm not on the net, the machine still tries to talk to the > nameservers I have set up in resolv.conf when I write : > netscape http://localhost/ > and it then hangs for a long time as it cannot connect to the > nameservers. > > If I write netscape http://127.0.0.1/ it works. > > # cat /etc/hosts > 127.0.0.1 localhost localhost.localdomain > > # cat /etc/resolv.conf > nameserver 193.212.1.11 > nameserver 193.212.1.10 > > Any hints much appreciated! /etc/host.conf ??? order hosts,bind multi on -- Eric G. Miller
Linux tries to talk to nameserver when accessing localhost (was Re: neighbour table overflow with Woody)
Preben Randhol <[EMAIL PROTECTED]> wrote on 30/12/2000 (21:57) : > Apparently I did something else as well as it stopped working :-( That is when I'm not on the net, the machine still tries to talk to the nameservers I have set up in resolv.conf when I write : netscape http://localhost/ and it then hangs for a long time as it cannot connect to the nameservers. If I write netscape http://127.0.0.1/ it works. # cat /etc/hosts 127.0.0.1 localhost localhost.localdomain # cat /etc/resolv.conf nameserver 193.212.1.11 nameserver 193.212.1.10 Any hints much appreciated! -- Preben Randhol -- http://www.pvv.org/~randhol/ -- +---+ "There was, I think, never any reason to believe in any innate | ! | superiority of the male, except his superior muscle." +---+ -- Bertrand Russell, Ideas That Have Harmed Mankind (1950)
Re: neighbour table overflow with Woody
Preben Randhol <[EMAIL PROTECTED]> wrote on 30/12/2000 (18:26) : > > I found the error. I had edited the wrong file and commented out auto lo > in /etc/network/interfaces Apparently I did something else as well as it stopped working :-( -- Preben Randhol -- http://www.pvv.org/~randhol/ -- +---+ "There was, I think, never any reason to believe in any innate | ! | superiority of the male, except his superior muscle." +---+ -- Bertrand Russell, Ideas That Have Harmed Mankind (1950)
Re: neighbour table overflow with Woody
Preben Randhol <[EMAIL PROTECTED]> wrote on 30/12/2000 (18:14) : > I can connect to the outside world, but i cannot connect to localhost > neither with ssh nor netscape. If I connect to my machine with either > from another machine it works. I also get neighbour table overflow in > the /var/log/messages. > > Can somebody please give me a hint of what might be the problem as I > have tried a lot of things now, but I cannot pin the problem down. The > only thing I found out was that the 2.2.18 kernel made my isdn system > unstable so I went back to 2.2.15. > > All this worked when I had potato, but after upgrading to woody things > started to break. I found the error. I had edited the wrong file and commented out auto lo in /etc/network/interfaces Sorry about that. -- Preben Randhol -- http://www.pvv.org/~randhol/ -- +---+ "There was, I think, never any reason to believe in any innate | ! | superiority of the male, except his superior muscle." +---+ -- Bertrand Russell, Ideas That Have Harmed Mankind (1950)
neighbour table overflow with Woody
I can connect to the outside world, but i cannot connect to localhost neither with ssh nor netscape. If I connect to my machine with either from another machine it works. I also get neighbour table overflow in the /var/log/messages. Can somebody please give me a hint of what might be the problem as I have tried a lot of things now, but I cannot pin the problem down. The only thing I found out was that the 2.2.18 kernel made my isdn system unstable so I went back to 2.2.15. All this worked when I had potato, but after upgrading to woody things started to break. Thanks in advance. -- Preben Randhol -- http://www.pvv.org/~randhol/ -- +---+ "There was, I think, never any reason to believe in any innate | ! | superiority of the male, except his superior muscle." +---+ -- Bertrand Russell, Ideas That Have Harmed Mankind (1950)
Re: neighbour table overflow
On Fri, 6 Oct 2000, Marek Habersack wrote: > ** On Oct 06, Robert Lazzurs scribbled: > > On Thu, 5 Oct 2000, Marek Habersack wrote: > > > > > ** On Oct 05, Robert Lazzurs scribbled: > > > > > > > > > I have now compiled and installed a custom 2.2.17 kernel as I > > > > > > thought it > > > > > > might have been a problem with the kernel image that debian > > > > > > provides, but > > > > > > it is not! > > > > > > > > > > > > Any help would be vvvnice :) > > > > > Check whether you have the lo network interface up. If not - start > > > > > it. This > > > > > should cure your problem. > > > > > > > > > > marek > > > > > > > > I have tried, but it does not appear to be setup, have you any ideas on > > > > how I can do this? > > > What Debian distro are you using? > > > > > > marek > > > > Potato, thanks again - Rab > OK. there are two ways of doing it: > > 1. Check out whether you have the /etc/networ/interfaces file. If it's >there, just add the following line at the top of it: > >iface lo inet loopback > >After doing so, execute the following command line as root: > >ifup -a > > 2. If #1 isn't working for you for some reason, you can use the older >approach: > >Check whether you have the /etc/init.d/network script. If it's there >try putting the following lines at the top (below the shebang): > >ifconfig lo 127.0.0.1 >route add -net 127.0.0.0 > >From now on on every startup the lo interface should be configured and >running. You can type those commands without restarting the machine, of >course. > > > hope that helps > > marek (sorry for the late reply) Yea, it did, everything is working fine now, thanks very much, you are proof that the community does work when someone like me needs help. Thanks again, take care - Rab -- Robert Lazzurs | "You can't stop me you know who I am The Lazzurs Administration | This justifies now just what I am +44 7092 157408 | You crucify me, won't lay by my side [EMAIL PROTECTED] | And know you'll need me until I die" AIM:lazzurs ICQ:66324927| -==- Yahoo:arl666_uk MSN:arl666 | Boycott HackSDMI
Re: neighbour table overflow
** On Oct 06, Robert Lazzurs scribbled: > On Thu, 5 Oct 2000, Marek Habersack wrote: > > > ** On Oct 05, Robert Lazzurs scribbled: > > > > > > > I have now compiled and installed a custom 2.2.17 kernel as I thought > > > > > it > > > > > might have been a problem with the kernel image that debian provides, > > > > > but > > > > > it is not! > > > > > > > > > > Any help would be vvvnice :) > > > > Check whether you have the lo network interface up. If not - start it. > > > > This > > > > should cure your problem. > > > > > > > > marek > > > > > > I have tried, but it does not appear to be setup, have you any ideas on > > > how I can do this? > > What Debian distro are you using? > > > > marek > > Potato, thanks again - Rab OK. there are two ways of doing it: 1. Check out whether you have the /etc/networ/interfaces file. If it's there, just add the following line at the top of it: iface lo inet loopback After doing so, execute the following command line as root: ifup -a 2. If #1 isn't working for you for some reason, you can use the older approach: Check whether you have the /etc/init.d/network script. If it's there try putting the following lines at the top (below the shebang): ifconfig lo 127.0.0.1 route add -net 127.0.0.0 From now on on every startup the lo interface should be configured and running. You can type those commands without restarting the machine, of course. hope that helps marek pgpLLh1KUj5jh.pgp Description: PGP signature
Re: neighbour table overflow
On Thu, 5 Oct 2000, Marek Habersack wrote: > ** On Oct 05, Robert Lazzurs scribbled: > > > > > I have now compiled and installed a custom 2.2.17 kernel as I thought it > > > > might have been a problem with the kernel image that debian provides, > > > > but > > > > it is not! > > > > > > > > Any help would be vvvnice :) > > > Check whether you have the lo network interface up. If not - start it. > > > This > > > should cure your problem. > > > > > > marek > > > > I have tried, but it does not appear to be setup, have you any ideas on > > how I can do this? > What Debian distro are you using? > > marek Potato, thanks again - Rab -- Robert Lazzurs | "You can't stop me you know who I am The Lazzurs Administration | This justifies now just what I am +44 7092 157408 | You crucify me, won't lay by my side [EMAIL PROTECTED] | And know you'll need me until I die" AIM:lazzurs ICQ:66324927| -==- Yahoo:arl666_uk MSN:arl666 | Boycott HackSDMI
Re: neighbour table overflow
** On Oct 05, Robert Lazzurs scribbled: > > > I have now compiled and installed a custom 2.2.17 kernel as I thought it > > > might have been a problem with the kernel image that debian provides, but > > > it is not! > > > > > > Any help would be vvvnice :) > > Check whether you have the lo network interface up. If not - start it. This > > should cure your problem. > > > > marek > > I have tried, but it does not appear to be setup, have you any ideas on > how I can do this? What Debian distro are you using? marek pgpo6PIrwcIcF.pgp Description: PGP signature
Re: neighbour table overflow
On Thu, 5 Oct 2000, Marek Habersack wrote: > ** On Oct 05, Robert Lazzurs scribbled: > > Hello, I am a potato user, and I have setup my system fairly minimal, > > nothing but c/c++ dev, x with icewm, gnome-libs, and apache and exim. > > > > I keep getting the above message, but I cannot track the reason, it > > happens when I access remote sites, for instance, when I ping my self, or > > mess about with my pop server (I had that setup yesterday, I have trashed > > my machine once trying to fix this, long story) > > > > I have now compiled and installed a custom 2.2.17 kernel as I thought it > > might have been a problem with the kernel image that debian provides, but > > it is not! > > > > Any help would be vvvnice :) > Check whether you have the lo network interface up. If not - start it. This > should cure your problem. > > marek I have tried, but it does not appear to be setup, have you any ideas on how I can do this? Thanks again - Rab -- Robert Lazzurs | "You can't stop me you know who I am The Lazzurs Administration | This justifies now just what I am +44 7092 157408 | You crucify me, won't lay by my side [EMAIL PROTECTED] | And know you'll need me until I die" AIM:lazzurs ICQ:66324927| -==- Yahoo:arl666_uk MSN:arl666 | Boycott HackSDMI
Re: neighbour table overflow
** On Oct 05, Robert Lazzurs scribbled: > Hello, I am a potato user, and I have setup my system fairly minimal, > nothing but c/c++ dev, x with icewm, gnome-libs, and apache and exim. > > I keep getting the above message, but I cannot track the reason, it > happens when I access remote sites, for instance, when I ping my self, or > mess about with my pop server (I had that setup yesterday, I have trashed > my machine once trying to fix this, long story) > > I have now compiled and installed a custom 2.2.17 kernel as I thought it > might have been a problem with the kernel image that debian provides, but > it is not! > > Any help would be vvvnice :) Check whether you have the lo network interface up. If not - start it. This should cure your problem. marek pgpj9WUQ2R2TC.pgp Description: PGP signature
neighbour table overflow
Hello, I am a potato user, and I have setup my system fairly minimal, nothing but c/c++ dev, x with icewm, gnome-libs, and apache and exim. I keep getting the above message, but I cannot track the reason, it happens when I access remote sites, for instance, when I ping my self, or mess about with my pop server (I had that setup yesterday, I have trashed my machine once trying to fix this, long story) I have now compiled and installed a custom 2.2.17 kernel as I thought it might have been a problem with the kernel image that debian provides, but it is not! Any help would be vvvnice :) (please cc, as I am not on the list) -- Robert Lazzurs | "You can't stop me you know who I am The Lazzurs Administration | This justifies now just what I am +44 7092 157408 | You crucify me, won't lay by my side [EMAIL PROTECTED] | And know you'll need me until I die" AIM:lazzurs ICQ:66324927| -==- Yahoo:arl666_uk MSN:arl666 | Boycott HackSDMI
Re: neighbour table overflow
Alec Smith wrote: > It should be in /etc/network/interfaces See the attached file for an > example. > > On Fri, 2 Jun 2000, Dietmar wrote: > > > I recently install potato on my new box and finally realized that the > > kernel issued "neighbour table overflow". I figered out that this was > > because my internet loopback device was not activated though part of the > > kernel. ifconfig lo 127.0.0.1 fixes everything. > > I finally want to know where this (or whatever activates loopback) needs > > to be placed in the course of the debian boot files. > > > > Any advice would be fine, Dietmar > > > > > > -- > > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > > > > > # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) > > # The loopback interface > iface lo inet loopback > > # The first network card - this entry was created during the Debian > installation > # (network, broadcast and gateway are optional) > iface eth0 inet static > address 130.108.229.38 > netmask 255.255.255.0 > network 130.108.229.0 > broadcast 130.108.229.255 > gateway 130.108.229.1 Just before I insert this into my /etc/network (this file doesn't exist on my box) - Could you ckeck which package installed /etc/network/interfaces on yours?
neighbour table overflow
I recently install potato on my new box and finally realized that the kernel issued "neighbour table overflow". I figered out that this was because my internet loopback device was not activated though part of the kernel. ifconfig lo 127.0.0.1 fixes everything. I finally want to know where this (or whatever activates loopback) needs to be placed in the course of the debian boot files. Any advice would be fine, Dietmar
Re: "Neighbour table overflow" in potato boot-up
On Fri, Mar 24, 2000 at 09:55:55AM -0600, Alberto Brealey G. wrote: > > i did a not-so-fresh install of potato last week (first installed base slink > cause i have a bootable cdrom, then upgraded it to potato and installed the > other packages). the machine worked fine in the office for a couple of days, > then i moved it to another building, and the first time i tried to boot it > up, it hangs with 'Neighbour table overflow' messages just before starting > inetd (after klogd i believe). As I recall, the above error message is cause by having no loopback device. > by the way, the box -when it was working- took a long time to start up > inetd. i think i remember a message in the mailing list telling someone this > was because the llopbak wasn't being initialized. is this it? any other > ideas? Don't know about a slow inetd startup: but it is the reason for the 'neighbour table overflow'. Boot single user and fix /etc/network/interfaces (the new and proper way) or /etc/init.d/network for the old way. -- Brian Moore | Of course vi is God's editor. Sysadmin, C/Perl Hacker | If He used Emacs, He'd still be waiting Usenet Vandal | for it to load on the seventh day. Netscum, Bane of Elves.
"Neighbour table overflow" in potato boot-up
i did a not-so-fresh install of potato last week (first installed base slink cause i have a bootable cdrom, then upgraded it to potato and installed the other packages). the machine worked fine in the office for a couple of days, then i moved it to another building, and the first time i tried to boot it up, it hangs with 'Neighbour table overflow' messages just before starting inetd (after klogd i believe). by the way, the box -when it was working- took a long time to start up inetd. i think i remember a message in the mailing list telling someone this was because the llopbak wasn't being initialized. is this it? any other ideas? TIA Alberto Brealey [EMAIL PROTECTED]
