From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [BUG] VPN broken in net-next Date: Wed, 2 Mar 2011 16:41:14 -0800 Message-ID: <20110302164114.2e110ea0@nehalam> References: <20110302162826.59f52c77@nehalam> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org To: David Miller Return-path: Received: from mail.vyatta.com ([76.74.103.46]:43009 "EHLO mail.vyatta.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753276Ab1CCAlR (ORCPT ); Wed, 2 Mar 2011 19:41:17 -0500 In-Reply-To: <20110302162826.59f52c77@nehalam> Sender: netdev-owner@vger.kernel.org List-ID: On Wed, 2 Mar 2011 16:28:26 -0800 Stephen Hemminger wrote: > My PPTP VPN is broken with net-next tree, it works fine with 2.6.38-rc6 > but not in the next tree. Bisected the problem down to the following commit. > > Debugging to see which address request is failing with the new code. > > 9435eb1cf0b76b323019cebf8d16762a50a12a19 is the first bad commit > commit 9435eb1cf0b76b323019cebf8d16762a50a12a19 > Author: David S. Miller > Date: Fri Feb 18 12:43:09 2011 -0800 > > ipv4: Implement __ip_dev_find using new interface address hash. > > Much quicker than going through the FIB tables. > > Signed-off-by: David S. Miller > > :040000 040000 265fa1882ee3430f74d59c9b38b6aca0858396d6 28a01a4941f99f7c266fd84f36cc27b933d426c1 M net > -- > To unsubscribe from this list: send the line "unsubscribe netdev" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html __ip_dev_find is being called with 10.250.0.105 and failing. At the time the route tables are: When VPN is up, the following is in the local table: local 10.250.0.105 dev ppp0 proto kernel scope host src 10.250.0.105 and it isn't getting matched... In main table the difference is: +10.255.254.0 dev ppp0 proto kernel scope link src 10.250.0.105 -default via 192.168.1.1 dev eth0 proto static