3: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
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 a
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
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 addre
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?
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
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
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
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 descripto
"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 d
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.
> Otherwi
"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, t
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"'
"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, t
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
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 the
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.or
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
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
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
> > > > >
** 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 debia
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!
> > > >
> > > > An
** 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 networ
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
** 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
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
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 overfl
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 wher
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
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 wa
30 matches
Mail list logo
