Date: Sun, 30 Aug 1998 22:56:49 +0200 (CEST) From: Barry Bierbauch <pivrnec@vszbr.cz> To: Doug White <dwhite@resnet.uoregon.edu> Cc: freebsd-current@FreeBSD.ORG Subject: Re: /kernel: arpresolve: can't allocate llinfo Message-ID: <Pine.BSF.3.96.980830224317.20349D-100000@coredump.int.tele.dk> In-Reply-To: <Pine.BSF.4.00.9808181414301.19286-100000@resnet.uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 18 Aug 1998, Doug White wrote: > > > 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: > > > > Destination Gateway Flags Refs Use Netif Expire > > default 195.178.72.111 UGc -9358 4337645 vx0 > > 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. Yeah, well, last week I got the machine rebooted with a static route to the Real World. Destination Gateway Flags Refs Use Netif Expire default 195.178.72.111 UGSc 106 4615 vx0 127.0.0.1 127.0.0.1 UH 1 655120 lo0 195.178.72 link#1 UC 0 0 vx0 [...] Just a few minutes ago, it decided to pull the same stunt, becoming invisible to part of the world, while being reachable from other parts. There's no messages about anything like this anywhere in the logs or dmesg output. I have to wonder about this `Use' figure, what with having been up almost a week now, Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll vx0 1500 <Link> 00.60.97.36.98.5d 155191266 55 165208024 0 118 The local netwerk is reachable, as are some remote hosts on the other side of the default gateway: traceroute to nimloth.ics.muni.cz (147.251.6.16), 30 hops max, 40 byte packets 1 195.178.72.111 (195.178.72.111) 1.296 ms 1.171 ms 1.040 ms 2 nimloth.ics.muni.cz (147.251.6.16) 1.764 ms * 1.522 ms traceroute to news-fra.maz.net (194.163.252.233), 30 hops max, 40 byte packets 1 195.178.72.111 (195.178.72.111) 1.538 ms 1.039 ms 1.023 ms 2 raa-main.ten34.ces.net (195.178.64.65) 7.297 ms 6.485 ms 6.463 ms 3 cz.DE-1.ten-34.net (193.203.227.21) 17.927 ms 17.991 ms 17.835 ms 4 de-2.DE-1.ten-34.net (193.203.227.25) 18.900 ms 18.867 ms 18.800 ms 5 frankfurt6.att-unisource.net (195.206.64.61) 135.695 ms 19.802 ms 19.815 ms [...] While certain other sites which had access a few minutes earlier are unreachable: traceroute to news-feed.inet.tele.dk (194.182.148.154), 30 hops max, 40 byte packets 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * *^C traceroute to news.eecs.umich.edu (141.212.99.3), 30 hops max, 40 byte packets 1 * *^C Naturally, from one of these outside machines, the target machine appears not to be there: 13 frankfurt6.att-unisource.net (195.206.64.42) 55.840 ms 55.850 ms 53.199 ms 14 DE.ten-34.net (195.206.64.62) 60.322 ms 61.143 ms 56.761 ms 15 de-1.DE-2.ten-34.net (193.203.227.26) 62.131 ms 56.252 ms 56.065 ms 16 ten-34cz-DE.ces.net (193.203.227.22) 74.731 ms 67.026 ms 69.588 ms 17 rbm2-main.ten34.ces.net (195.178.64.70) 72.156 ms 76.913 ms 73.910 ms 18 * * * 19 * * * 20 * * * I might try very carefully ifconfig'ing the interface down and back up to see if that helps, or manually deleting and adding the default route, but something tells me that even with a static route like this, I shouldn't be seeing this. Again, this is a -current snap from early August, to be updated Real Soon Now, maybe. Barry Bouwsma 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.980830224317.20349D-100000>