From owner-freebsd-net Tue Nov 19 12:47:45 2002 Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C369637B404 for ; Tue, 19 Nov 2002 12:47:43 -0800 (PST) Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NetScum.dyndns.dk (dclient217-162-173-135.hispeed.ch [217.162.173.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DF1343E9C for ; Tue, 19 Nov 2002 12:47:41 -0800 (PST) (envelope-from bounce@dcf77-zeit.netscum.dyndns.dk) Received: from MAIL.NetScum.DynDNS.dK (ipv6.NetScum.dyndns.dk [2002:d9a2:ad87:0:200:c0ff:fefc:19aa]) by dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NetScum.dyndns.dk (8.11.6/8.11.6-SPAMMERS-DeLiGHt) with ESMTP id gAJKlan00551 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO) for ; Tue, 19 Nov 2002 21:47:39 +0100 (CET) (envelope-from bounce@dcf77-zeit.netscum.dyndns.dk) Received: (from root@localhost) by MAIL.NetScum.DynDNS.dK (8.11.6/SMI-4.1-R00T0WNED) id gAJKlaQ00550; Tue, 19 Nov 2002 21:47:36 +0100 (CET) (envelope-from bounce@dcf77-zeit.netscum.dyndns.dk) Date: Tue, 19 Nov 2002 21:47:36 +0100 (CET) Message-Id: <200211192047.gAJKlaQ00550@MAIL.NetScum.DynDNS.dK> From: BOUWSMA Beery Organization: Men not wearing any pants that dont shave To: freebsd-net@freebsd.org Subject: Question about rt_llinfo panic in netinet6 X-Hacked: via telnet to your port 25, what else? X-Internet-Access-Provided-By: CABAL MODEM (all hail CABAL) X-NetScum: Yes X-One-And-Only-Real-True-Fluffy: No Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org [IPv6-only address above; strip the obvious for IPv4-only mail] Howdy, I'm able to readily reproduce a panic with -stable that seems to be caused by my IPv6 script interacting with dhclient, that normally happens after the IPv4 address granted by the dhcp server expires. An infrequent occurrence, but I can simulate it pretty easily. The panic is in a sanity check in the src/sys/netinet6/nd6.c file: 456 /* sanity check */ [...] 459 if (rt->rt_llinfo && (struct llinfo_nd6 *)rt->rt_llinfo 459 != ln) 460 panic("rt_llinfo(%p) is not equal to ln(%p)\n", 461 rt->rt_llinfo, ln); I'm unclear, just what is this check, and in what cases is it likely to happen and induce this panic? I haven't figured out exactly what my stf(4)-based IPv6 script that also plays with faith and aliases might be doing to result in this panic, but I'll keep poking at it. What happens when the dhcp lease expires is that my interface IP address is set to 0. Then when I get connectivity to the dhcp server again and re-obtain the old IP address (or, apparently, a new one as well), that is enough to invoke this panic. Thus I can manually set the interface IP to 0.0.0.0 and restart dhclient and get the same panic. The intent of my script is to assign initial IPv6 addresses, or update them in the event the IPv4 address changes out from under me, but my initial debuggery makes it seem the panic happens later, when I try to get the info about the change to update my DNS zone files, or something. thanks, barry bouwsma To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message