From owner-freebsd-net@FreeBSD.ORG Wed Sep 10 19:30:05 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D1218106566B for ; Wed, 10 Sep 2008 19:30:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BB7448FC14 for ; Wed, 10 Sep 2008 19:30:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m8AJU5Ba063751 for ; Wed, 10 Sep 2008 19:30:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m8AJU5v2063748; Wed, 10 Sep 2008 19:30:05 GMT (envelope-from gnats) Date: Wed, 10 Sep 2008 19:30:05 GMT Message-Id: <200809101930.m8AJU5v2063748@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Jeff Wheelhouse Cc: Subject: Re: kern/127050: [carp] ipv6 does not work on carp interfaces [regression] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jeff Wheelhouse List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2008 19:30:05 -0000 The following reply was made to PR kern/127050; it has been noted by GNATS. From: Jeff Wheelhouse To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/127050: [carp] ipv6 does not work on carp interfaces [regression] Date: Wed, 10 Sep 2008 15:02:00 -0400 I am experiencing the identical behavior on the following releases: 6.3-RELEASE-p4 6.4-PRERELEASE (as of Sep 6) I have reproduced the problem on both amd64 and i386, on both physical interfaces and VLAN interfaces. The problem is the same: - two machines, both configured correctly - both machines can ping6 each other - carp configures correctly, and announcements are observed on the relevant LAN via tcpdump - one machine goes to MASTER and one goes to BACKUP - an additional machine on the same LAN can ping6 both machines - none of the three machines can ping (or route through) the CARP IPv6 address However, I'm *assuming* these are the CARP announcements (since they are from the right IPv6 addresses and MASTER/BACKUP status seems to work: 11:54:51.818511 IP6 A:B:C:D::1 > ff02::12: ip-proto-112 36 11:54:52.855924 IP6 A:B:C:D::1 > ff02::12: ip-proto-112 36 11:54:53.893300 IP6 A:B:C:D::1 > ff02::12: ip-proto-112 36 11:54:54.930386 IP6 A:B:C:D::1 > ff02::12: ip-proto-112 36 11:54:55.967965 IP6 A:B:C:D::1 > ff02::12: ip-proto-112 36 11:54:57.004987 IP6 A:B:C:D::1 > ff02::12: ip-proto-112 36 11:54:58.042481 IP6 A:B:C:D::1 > ff02::12: ip-proto-112 36 I would be happy to help troubleshoot this problem in any way possible. Thanks, Jeff