From owner-freebsd-net@FreeBSD.ORG Mon Mar 29 17:35:22 2010 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27DEF106566B for ; Mon, 29 Mar 2010 17:35:22 +0000 (UTC) (envelope-from pieter@os3.nl) Received: from mail.thelostparadise.com (router.thelostparadise.com [IPv6:2a02:898:0:30::30:1]) by mx1.freebsd.org (Postfix) with ESMTP id B685D8FC15 for ; Mon, 29 Mar 2010 17:35:21 +0000 (UTC) Received: by mail.thelostparadise.com (Postfix, from userid 127) id 5B06B7303D; Mon, 29 Mar 2010 19:35:20 +0200 (CEST) Received: from localhost by mail.thelostparadise.com (Postfix) with ESMTP id 425B973039 for ; Mon, 29 Mar 2010 19:35:19 +0200 (CEST) Message-ID: <4BB0E4D3.70904@os3.nl> Date: Mon, 29 Mar 2010 19:35:15 +0200 From: Pieter de Boer MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: ::1 magically replaced with other address X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Mar 2010 17:35:22 -0000 Hullo, On my 8.0-RELEASE-p1 system, my ::1 address on lo0 has been magically replaced with a global routable IPv6 address I have configured on lo3. This has happened two times with a week or so interval, without me doing any ifconfigs. With `replaced' I mean that ::1 is simply gone from the interface, although a route to it remains. Instead of ::1, one of the addresses configured on lo3 is also there on lo0. The address that ::1 is suddenly replaced with, is assigned to a jail that has it assigned to a child jail. There are also other IPv6 addresses assigned to this jail and its child jail, but those don't show up on lo0 all of a sudden: only one out of the set does. My question is, has anyone seen anything like this or does anyone have a clue how I could debug this? I cannot easily reboot the affected system to add debugging statements to the kernel, etc, but perhaps there are other ways? Thanks, Pieter