Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 Aug 1998 19:05:03 +0200 (CEST)
From:      Barry Bierbauch <pivrnec@vszbr.cz>
To:        freebsd-current@FreeBSD.ORG
Subject:   /kernel: arpresolve: can't allocate llinfo
Message-ID:  <Pine.BSF.3.96.980817185350.1348B-100000@coredump.int.tele.dk>

next in thread | raw e-mail | index | archive | help
Howdy...

I had been running a -current snap from last November, which usually
worked well, but sometimes, after a few weeks of uptime, it would
disappear as seen from the outside world, while being reachable locally.
At the same time, I would see the following messages in /var/log/messages,
which, coincidentally, I'm seeing again with a snapshot from
3.0-19980802-SNAP....

Aug 17 12:11:15 marley /kernel: arpresolve: can't allocate llinfo for 195.178.72
.111rt
Aug 17 12:11:46 marley inetd[157]: chargen from 131.114.21.10
Aug 17 12:12:21 marley inetd[157]: chargen from 131.114.21.10
Aug 17 12:13:21 marley inetd[157]: chargen from 131.114.21.10
Aug 17 12:19:21 marley last message repeated 2 times
Aug 17 12:27:21 marley inetd[157]: chargen from 131.114.21.10
Aug 17 12:28:19 marley /kernel: arpresolve: can't allocate llinfo for 195.178.72
.111rt
Aug 17 12:34:04 marley /kernel: arpresolve: can't allocate llinfo for 195.178.72
.111rt
Aug 17 12:36:05 marley last message repeated 803 times
Aug 17 12:41:44 marley last message repeated 4612 times
Aug 17 12:41:44 marley /kernel: arpresolve: can't allocate llinfo
Aug 17 12:41:44 marley /kernel: for 195.178.72.111rt
Aug 17 12:41:44 marley /kernel: arpresolve: can't allocate llinfo for 195.178.72
.111rt
Aug 17 12:42:15 marley last message repeated 514 times
Aug 17 12:44:16 marley last message repeated 1682 times
Aug 17 12:54:17 marley last message repeated 9008 times
Aug 17 13:04:17 marley last message repeated 7611 times
Aug 17 13:14:17 marley last message repeated 5513 times
[etc.]

The IP address is the router acting as gateway to the real world.  I'm
running routed, and I've added a configuration line, among others,
options         NMBCLUSTERS=4096

This machine has only been up for just over a day now when these messages
are appearing in force, and there has been once or twice when I've seen
these messages earlier with this recent snap, although uptime has never
been more than a few days before it wedges solid.


Any suggestions?

I think I'll be disabling routed and adding this host as the default
gateway for the upcoming reboot which should return me to the net...


Thanks,
Barry Bouwsma, Mendelova Univerzita v Brne, Czech Republic
<ag786@yfn.ysu.edu>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980817185350.1348B-100000>