From owner-freebsd-current@FreeBSD.ORG Thu Jul 30 16:57:16 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 31F2D106564A; Thu, 30 Jul 2009 16:57:16 +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 11CAE8FC14; Thu, 30 Jul 2009 16:57:15 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id n6UGvEba002626; Thu, 30 Jul 2009 09:57:15 -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, 30 Jul 2009 09:55:39 -0700 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: recent change to ifconfig breaks OpenVPN? Thread-Index: AcoRNU94anw5Tb2FSISYElzlWKas2gAATmKQ References: <4A709126.5050102@elischer.org><3A1518B9-2C8C-4F05-9195-82C6017E4902@lassitu.de> From: "Li, Qing" To: "Stefan Bethke" , "Qing Li" , "Bjoern A. Zeeb" Cc: Matthias Andree , FreeBSD Current Subject: RE: recent change to ifconfig breaks OpenVPN? 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, 30 Jul 2009 16:57:16 -0000 I will look into it. -- Qing > -----Original Message----- > From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd- > current@freebsd.org] On Behalf Of Stefan Bethke > Sent: Thursday, July 30, 2009 9:46 AM > To: Qing Li; Bjoern A. Zeeb > Cc: Matthias Andree; FreeBSD Current > Subject: Re: recent change to ifconfig breaks OpenVPN? >=20 > Am 30.07.2009 um 08:40 schrieb Stefan Bethke: >=20 > > Am 30.07.2009 um 01:46 schrieb Matthias Andree: > > > >> Hi everybody, > >> > >> If that is the case, then we should go quickly to either make it go > >> into 8-CURRENT's ports or OpenVPN 2.1, or both. > >> > >> I'm not sure I have sufficient context or time to read up to > >> determine my own role here (I haven't been following -current for > >> lack of time); can someone summarize the issue for me? > > > > I can try to summarize; I don't think I'll have time to come up with > > a patch this weekend. > > > > The problem appears to be that OpenVPN invokes ifconfig with > > incorrect (but previously working) parameters, namely "ifconfig tun0 > > local_ip local_ip" instead of "ifconfig tun0 local_ip remote_ip". > > The problem does not appear to be the SIOCAIFADDR but the RT_ADD > > that ifconfig does. When I drafted a replacement OpenVPN --up > > script yesterday, I also noticed that the parameters passed to the > > script are wrong (netmask instead of remote ip), and environment > > variables are partially not set (ifconfig_remote is empty). > > > > This issue appears to affect tun-mode connections; tap-mode > > connections appear to continue to work. > > > > I'm not sure if that is a more general problem with OpenVPN (at > > least in --topology subnet mode), or a specific problem in the > > FreeBSD-specific code. I just looked at a Linux box connected to > > the same OpenVPN server, and their ifconfig invocation looks > > different from ours, so the FreeBSD-specific code at least plays > > some role. > > > > I'd still like to know whether the change to the routing code is > > intentional or a regression. >=20 > I did at least have time to figure out the commit that changed it: > 195914 >=20 > > Author: qingli > > Date: Mon Jul 27 17:08:06 2009 > > New Revision: 195914 > > URL: http://svn.freebsd.org/changeset/base/195914 > > > > Log: > > This patch does the following: > > > > - Allow loopback route to be installed for address assigned to > > interface of IFF_POINTOPOINT type. > > - Install loopback route for an IPv4 interface addreess when the > > "useloopback" sysctl variable is enabled. Similarly, install > > loopback route for an IPv6 interface address when the sysctl > > variable > > "nd6_useloopback" is enabled. Deleting loopback routes for > > interface > > addresses is unconditional in case these sysctl variables were > > disabled after an interface address has been assigned. >=20 >=20 > Setting net.link.ether.inet.useloopback=3D0 does not restore the > previous behavior. >=20 >=20 > Stefan >=20 > -- > Stefan Bethke Fon +49 151 14070811 >=20 >=20 >=20 >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current- > unsubscribe@freebsd.org"