Re: Incorrect route with OpenVPN plugin

[Igor Neves <neves igor gmail com>]

Jon Escombe wrote:
> ----- "Jon Nettleton" <jon nettleton gmail com> wrote:
>> On Thu, 2007-05-24 at 14:21 -0400, Dan Williams wrote:
>>> On Wed, 2007-05-23 at 15:20 +0100, John Spray wrote:
>>>> Hi,
>>>>
>>>> I'm connecting to a VPN using NetworkManager 0.6.4 on ubuntu 7.04, but
>>>> it's not picking up the gateway correctly -- after NM connects to the
>>>> VPN I have to do a "route add -net 172.16.200.0 netmask 255.255.255.0 gw
>>>> 172.16.220.1" before it works correctly.  The route NM initially creates
>>>> for the 172.16.0.0 range specifies no gateway.
>>>>
>>>> I have attached logs from daemon.log when NM fails, and from the command
>>>> line output from the successful OpenVPN initialisation.  Note that the
>>>> OpenVPN log shows:
>>>>
>>>> PUSH: Received control message: 'PUSH_REPLY,route-gateway 172.16.220.1 ...
>>> The OpenVPN plugin might not relay the route information to NM when it
>>> gets the config...?
>> sounds like he has the option for Only use the VPN connection for these
>> addresses checked.  If I have it set as the default connection it works
>> properly for me.  
>>
>> Jon
>>
> 
> I see the same problem with NM 6.5 (on f7-rc2). A default route gets created but contains no gateway, and I don't have the "only use for these addresses" option selected...
> 
> Regards,
> Jon.

Yes, this is a problem, with the openvpn plugin at least.

It does not follow the routes given from the openvpn server, this should
be implemented in the plugin, with another things, i have in my TODO.

The field, "route only this" should exists, but the plugin should
support the PUSH_REPLY someone mention, because this can change, and the
client side, should not know that, that's why it is done in the server
side, and replied to the client, with the PUSH_REPLY answer.

I need somebody to help me compiling last svn version of the plugin,
before i try to develop, what it's not done yet.

Cheers.