Date: Mon, 17 Aug 1998 12:32:01 -0700 (PDT) From: Tom <tom@uniserve.com> To: Barry Bouwsma <ag786@yfn.ysu.edu> Cc: freebsd-current@FreeBSD.ORG Subject: Re: /kernel: arpresolve: can't allocate llinfo Message-ID: <Pine.BSF.3.96.980817123018.20836C-100000@shell.uniserve.ca> In-Reply-To: <Pine.BSF.3.96.980817185350.1348B-100000@coredump.int.tele.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 17 Aug 1998, Barry Bierbauch wrote: > 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 You should probably disable the chargen service in /etc/inetd.conf It doesn't seem to have much these days, except to allow outsiders to use your system to launch DoS of attacks. While you are doing that, disable the echo service too. Tom 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.980817123018.20836C-100000>