From owner-freebsd-current@FreeBSD.ORG  Thu Mar 11 10:52:57 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 1951F106566C
	for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 10:52:56 +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 BB9D38FC0C
	for <freebsd-current@freebsd.org>; Thu, 11 Mar 2010 10:52:56 +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 o2BAqtSA015296;
	Thu, 11 Mar 2010 02:52:56 -0800 (PST)
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, 11 Mar 2010 02:52:46 -0800
Message-ID: <B583FBF374231F4A89607B4D08578A4306CE24B1@bcs-mail03.internal.cacheflow.com>
In-Reply-To: <4B980347.8020500@protected-networks.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Error 127.0.0.1: no route to host
Thread-Index: AcrAkatm/dHl6mY/SOipMBL1JsGTBAAcHXvg
References: <747dc8f31003091046t28d69ce0y6924ce31db77783b@mail.gmail.com>	<B583FBF374231F4A89607B4D08578A4306C5D469@bcs-mail03.internal.cacheflow.com>	<B583FBF374231F4A89607B4D08578A4306C5D4F2@bcs-mail03.internal.cacheflow.com><4B96FD4B.3090706@FreeBSD.org>
	<4B978E41.4010800@protected-networks.net>
	<B583FBF374231F4A89607B4D08578A4306CE1FA6@bcs-mail03.internal.cacheflow.com>
	<4B980347.8020500@protected-networks.net>
From: "Li, Qing" <qing.li@bluecoat.com>
To: "Michael Butler" <imb@protected-networks.net>
Cc: freebsd-current@freebsd.org
Subject: RE: Error 127.0.0.1: no route to host
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2010 10:52:57 -0000

>=20
> Without the route.h patch, I can't ping 127.0.0.1 or the local or
> remote address of the OpenVPN tunnel (on tap0). In fact, you=20
> can't even build OpenVPN from ports as it'll fail its self-test.
>=20

   Please see my previous clarification email on the what and the why
   about the "route.h.diff" patch. =20

   I spent some time looking into the issue and found the problem=20
   is the if_tap interface turns out to be one of those interfaces=20
   that claims to be of IFT_ETHER type, but does not touch the=20
   "if_link_state" variable.

>
> With the route.h patch, I can ping all local addresses but not the=20
> far end of the tunnel.
>=20

   Please try the new patch at

     http://people.freebsd.org/~qingli/ecmp-tap.diff

   Let me know how it works out for you.

   -- Qing


P.S.  You really just need the 2-line fix in the if_tap.c file.
      route.h is slightly touch to be (ifp) instead of just ifp in
      the macro.