From owner-freebsd-net@FreeBSD.ORG  Fri May 26 09:17:10 2006
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
X-Original-To: freebsd-net@freebsd.org
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 722FE16A463
	for <freebsd-net@freebsd.org>; Fri, 26 May 2006 09:17:10 +0000 (UTC)
	(envelope-from _pppp@mail.ru)
Received: from f22.mail.ru (f22.mail.ru [194.67.57.55])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1283943D46
	for <freebsd-net@freebsd.org>; Fri, 26 May 2006 09:17:10 +0000 (GMT)
	(envelope-from _pppp@mail.ru)
Received: from mail by f22.mail.ru with local 
	id 1FjYRQ-000FnS-00; Fri, 26 May 2006 13:17:08 +0400
Received: from [81.200.14.42] by koi.mail.ru with HTTP;
	Fri, 26 May 2006 13:17:08 +0400
From: dima <_pppp@mail.ru>
To: Jan Zorz <freebsd@dir-slovenia.com>
Mime-Version: 1.0
X-Mailer: mPOP Web-Mail 2.19
X-Originating-IP: [81.200.14.42]
Date: Fri, 26 May 2006 13:17:08 +0400
In-Reply-To: <200605260913.35506.freebsd@dir-slovenia.com>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 8bit
Message-Id: <E1FjYRQ-000FnS-00._pppp-mail-ru@f22.mail.ru>
Cc: freebsd-net@freebsd.org
Subject: Re[2]: CARP broken in 6.1
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dima <_pppp@mail.ru>
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 26 May 2006 09:17:11 -0000

> On Thursday 25 of May 2006 17:17, dima wrote:
>> Assigning an IP address to a CARP interface leads to the new route table
>> entry: <THIS_IP> <THIS_IP> UH 0 0 carp0
>>
>> and such error in /var/log/messages:
>> arp_rtrequest: bad gateway <THIS_IP> (!AF_LINK)
>>
>> Removing the entry manually seems to fix the issue. But I can't ping the
>> CARP address from inside.
> 
> On which interface you try to setup carp? Fiber, copper, which brand?

em(4), copper. Does it matter?