From owner-freebsd-current@FreeBSD.ORG Thu Sep 24 21:20:20 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC411106566C; Thu, 24 Sep 2009 21:20:20 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by mx1.freebsd.org (Postfix) with ESMTP id D13DF8FC1B; Thu, 24 Sep 2009 21:20:20 +0000 (UTC) Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id n8OLKJ4m022080; Thu, 24 Sep 2009 14:20:20 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 24 Sep 2009 14:19:13 -0700 Message-ID: In-Reply-To: <4ABBAC87.4040306@FreeBSD.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Point-to-Point interfaces regressions Thread-Index: Aco9QNUp9HBz/qA8S8+ML6IxqB3RXQAA5ooQ References: <4ABBAC87.4040306@FreeBSD.org> From: "Li, Qing" To: "Alexander Motin" , "freebsd-net" Cc: freebsd-current@freebsd.org Subject: RE: Point-to-Point interfaces regressions X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2009 21:20:21 -0000 >=20 > 1) I am going to reuse Ethernet address as local for PtP link: > %ifconfig ng0 10.0.0.1 10.0.0.2 > ifconfig: ioctl (SIOCAIFADDR): File exists > %ifconfig ng0 > ng0: flags=3D88d1 = metric > 0 > mtu 1500 > inet 10.0.0.1 --> 10.0.0.2 netmask 0xff000000 > So as you can see, address was assigned, but request returned error > status. Probably it is related to the recent local address route > changes. >=20 I have written several times about this particular topic here. Yes, the behavior changed. Previously if you try to ping 10.0.0.1 the packets leak onto the wire even though that's a local address. And you cannot connect to the local end, again, packets go on the wire towards possibly the default gateway. > > 2) I am going to configure arp-proxy: > %arp -s 10.0.0.2 00:1b:24:c5:5b:09 pub > arp: writing to routing socket: Invalid argument > And again it doesn't work, writing to syslog: > kernel: lla_rt_output: RTM_ADD publish (proxy only) is invalid > I will take a look and let you know what the issue might be. -- Qing