From owner-freebsd-questions Thu Mar 21 13:43:55 2002 Delivered-To: freebsd-questions@freebsd.org Received: from fep03-mail.bloor.is.net.cable.rogers.com (fep03-mail.bloor.is.net.cable.rogers.com [66.185.86.73]) by hub.freebsd.org (Postfix) with ESMTP id 667F237B41A for ; Thu, 21 Mar 2002 13:43:36 -0800 (PST) Received: from hyperion ([24.156.109.151]) by fep03-mail.bloor.is.net.cable.rogers.com (InterMail vM.5.01.04.06 201-253-122-122-106-20020109) with ESMTP id <20020321214336.FLSK4430.fep03-mail.bloor.is.net.cable.rogers.com@hyperion> for ; Thu, 21 Mar 2002 16:43:36 -0500 Date: Thu, 21 Mar 2002 16:43:33 -0500 Mime-Version: 1.0 (Apple Message framework v481) Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: can't allocate llinfo From: Joe Abley To: freebsd-questions@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: X-Mailer: Apple Mail (2.481) X-Authentication-Info: Submitted using SMTP AUTH PLAIN at fep03-mail.bloor.is.net.cable.rogers.com from [24.156.109.151] using ID at Thu, 21 Mar 2002 16:43:36 -0500 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm getting a bunch of these, all of a sudden: Mar 21 16:39:39 buffoon /kernel: arpresolve: can't allocate llinfo for 209.249.158.34rt Mar 21 16:39:44 buffoon /kernel: arplookup 209.249.158.34 failed: could not allocate llinfo Mar 21 16:39:44 buffoon /kernel: arpresolve: can't allocate llinfo for 209.249.158.34rt Mar 21 16:39:45 buffoon /kernel: arplookup 209.249.158.34 failed: could not allocate llinfo Mar 21 16:39:45 buffoon /kernel: arpresolve: can't allocate llinfo for 209.249.158.34rt Mar 21 16:39:45 buffoon /kernel: arplookup 209.249.158.34 failed: could not allocate llinfo Mar 21 16:39:45 buffoon /kernel: arpresolve: can't allocate llinfo for 209.249.158.34rt They are scaring me, slightly, especially with that slightly malformed IP address. Machine is a fresh 4-STABLE (well, fresh as of last night). That address is actually reached through a gif tunnel; various details below. If this rings any bells for anybody, it would be good to hear from them :) [jabley@buffoon]$ uname -a FreeBSD buffoon.automagic.org 4.5-STABLE FreeBSD 4.5-STABLE #7: Thu Mar 21 11:10:27 EST 2002 jabley@buffoon.automagic.org:/usr/obj/usr/src/sys/BUFFOON i386 [jabley@buffoon]$ [jabley@buffoon]$ ifconfig -a fxp0: flags=8a43 mtu 1500 inet 208.185.30.208 netmask 0xffffffc0 broadcast 208.185.30.255 inet6 fe80::2d0:b7ff:fe79:a0a7%fxp0 prefixlen 64 scopeid 0x1 ether 00:d0:b7:79:a0:a7 media: Ethernet autoselect (100baseTX ) status: active lp0: flags=8810 mtu 1500 lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff000000 inet6 2001:438:1fff:fff7::1 prefixlen 64 ppp0: flags=8010 mtu 1500 sl0: flags=c010 mtu 552 faith0: flags=8002 mtu 1500 gif1: flags=8051 mtu 1280 tunnel inet 208.185.30.208 --> 209.249.254.66 inet6 fe80::2d0:b7ff:fe79:a0a7%gif1 prefixlen 64 scopeid 0x7 inet6 2001:438:1fff:ffff:8::32 --> 2001:438:1fff:ffff:8::31 prefixlen 128 gif0: flags=8051 mtu 1280 tunnel inet 208.185.30.208 --> 24.156.109.151 inet6 fe80::2d0:b7ff:fe79:a0a7%gif0 prefixlen 64 scopeid 0x8 inet 209.249.158.33 --> 209.249.158.34 netmask 0xffffffff inet6 2001:438:1fff:ffff:8::25 --> 2001:438:1fff:ffff:8::26 prefixlen 128 [jabley@buffoon]$ [jabley@buffoon]$ netstat -rn -f inet Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 208.185.30.193 UGSc 4430 15077 fxp0 127.0.0.1 127.0.0.1 UH 379 4340 lo0 208.185.30.192/26 link#1 UC 2 0 fxp0 208.185.30.193 0:0:c:7:ac:2 UHLW 103 0 fxp0 989 208.185.30.208 0:d0:b7:79:a0:a7 UHLW 0 32 lo0 209.249.158/27 209.249.158.34 UGSc 1 2086 fxp0 209.249.158.34 209.249.158.33 UH 0 271 gif0 [jabley@buffoon]$ [jabley@buffoon]$ arp -an ? (208.185.30.193) at 0:0:c:7:ac:2 on fxp0 [ethernet] ? (208.185.30.208) at 0:d0:b7:79:a0:a7 on fxp0 permanent [ethernet] [jabley@buffoon]$ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message