On Sat, May 25, 2013 at 3:34 PM, Stuart Henderson <[email protected]>wrote:
> On 2013/05/25 12:33, Mattieu Baptiste wrote: > > > > > > Does someone managed to make OpenVPN work with 'route exec' ? > > For me, it freeze just before establishing routes and creating the tun > > interface. > > Ah - it re-creates the interface, doesn't it... perhaps that fails > with an alternative table... > > As a starting point here's a diff to put the port back the way it was > before I removed the rtable patch, but it still needs actually fixing > (and probably by somebody who actually uses this..) > > Sorry, I wasn't clear enough. I didn't managed to make it work before, with the OpenVPN 2.2.2 port before the upgrade. Now, I have upgraded my box to -current and try to make 'route exec' work, but with the same result. In the same way exposed by stefan, I configure my tun interface in the corresponding routing domain, then I start openvpn : $ sudo ifconfig tun2 create rdomain 1 $ sudo route -T1 exec openvpn --config... In this routing domain, I have other interfaces, with a default gateway. Stefan, how do you configure your tun interface? -- Mattieu Baptiste "/earth is 102% full ... please delete anyone you can."
