On Wed, Apr 17, 2013 at 3:24 PM, Stuart Henderson <[email protected]> wrote:
> I think the rtable support is broken though.
>
> In 2.2.2 it seems to just do the same as running "route -T <table>
> exec openvpn $options" so if you don't have a route to the other
> endpoint it is unable to connect.
>
> With the update, the option is parsed ("rtable = 1" in debug output),
> but it appears to just connect as normal via rtable 0.
>
> But I don't really see the use of this limited rtable support anyway;
> since we now have 'route exec' we can just use that and remove these
> patches.
>
Does someone managed to make OpenVPN work with 'route exec' ?
For me, it freeze just before establishing routes and creating the tun
interface.
--
Mattieu Baptiste
"/earth is 102% full ... please delete anyone you can."