Date: Tue, 18 Aug 1998 14:15:12 -0700 (PDT) From: Doug White <dwhite@resnet.uoregon.edu> To: Barry Bouwsma <ag786@yfn.ysu.edu> Cc: freebsd-current@FreeBSD.ORG Subject: Re: /kernel: arpresolve: can't allocate llinfo Message-ID: <Pine.BSF.4.00.9808181414301.19286-100000@resnet.uoregon.edu> In-Reply-To: <Pine.BSF.3.96.980818084333.2081A-100000@coredump.int.tele.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 18 Aug 1998, Barry Bierbauch wrote: > On 17 Aug 1998, some BoZo masquerading as Barry Bierbauch drooled: > > > 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 > > And just as a followup, when I logged into that machine from the local > netwerk and did a netstat, here's what I saw: > > su-2.02# netstat -nr > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif Expire > default 195.178.72.111 UGc -9358 4337645 vx0 > 127.0.0.1 127.0.0.1 UH 1 4328 lo0 > 195.178.72 link#1 UC 1 376 vx0 > [...] > > Hmmm. Your system seems to be confused about your router, or you have some seriously runaway TCP processes; refs somehow completely rolled over. :) llinfo problems usually stem from bad routing or netmasking. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major 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.4.00.9808181414301.19286-100000>