On 18/08/16 15:43, Jan Just Keijser wrote: > Hi, > > On 18/08/16 15:34, Alarig Le Lay wrote: >> On Thu Aug 18 13:23:40 2016, Joe Patterson wrote: >>> I think what you want is 'push "route 89.234.186.0 255.255.255.0"' >>> If you >>> just have route with an IP and no netmask, it's going to assume a >>> /32 mask. >> I do want to have a /32 route. The /24 is not fully reachable via the >> VPN. >> >> eg.: >> alarig@arthur ~ $ mtr -4 -n -c 1 -w kaiminus.swordarmor.fr >> Start: Thu Aug 18 15:32:56 2016 >> HOST: arthur Loss% Snt Last Avg Best Wrst StDev >> 1.|-- 89.234.186.4 0.0% 1 7.9 7.9 7.9 7.9 0.0 >> 2.|-- 89.234.186.15 0.0% 1 8.7 8.7 8.7 8.7 0.0 >> > there's no "standard" way to do this - and I assume all of your > clients are Linux clients. > What you'd need to do is: > - push a route > push "route 89.234.186.4 255.255.255.255" > - add > route-noexec > route up "<path to script>" > this route-up script would then add the route using the appropriate > '/sbin/ip' command. actually, that's route-up "<path to script>" with a hyphen.
But also, as David S pointed out, there are easier methods to use public IP addresses for clients - which, of course, is explained in my OpenVPN cookbook ;) HTH, JJK ------------------------------------------------------------------------------ _______________________________________________ Openvpn-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openvpn-users
