[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20110302.170346.13723622.davem@davemloft.net>
Date: Wed, 02 Mar 2011 17:03:46 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: unlisted-recipients:; (no To-header on input)
Cc: netdev@...r.kernel.org
Subject: Re: [BUG] VPN broken in net-next
From: Stephen Hemminger <shemminger@...tta.com>
Date: Wed, 2 Mar 2011 16:56:53 -0800
> On Wed, 02 Mar 2011 16:50:09 -0800 (PST)
> David Miller <davem@...emloft.net> wrote:
>
>> From: Stephen Hemminger <shemminger@...tta.com>
>> Date: Wed, 2 Mar 2011 16:46:37 -0800
>>
>> > The addresses (that matter) when VPN is up are:
>>
>> I really need to know what addresses interfaces have the time of the
>> __ip_dev_find() call which, if I'm not mistaken, is before the VPN is
>> up.
>
>
> inet 127.0.0.1/8 scope host lo
> inet 192.168.1.11/24 brd 192.168.1.255 scope global eth0
> inet 192.168.100.1/24 brd 192.168.100.255 scope global virbr0
> inet 192.168.99.1/24 brd 192.168.99.255 scope global virbr1
I see nothing providing 10.0.whatever that __ip_dev_find() is being
asked to resolve.
I think we were allowing the route lookup pptp is trying to do at
connect time erroneously, and it should elide the explicit source
address specification in the flow.
See my other email.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists