On 18/08/16 14:49, Alarig Le Lay wrote: > Hi, > > I have a setup where each client have a /32 IPv4 (not /24) because the > /24 is not only used for the VPN. The server have the address > 89.234.186.3 on eth0 and 89.234.186.4 on tun0. > > The gateway for the clients is 89.234.186.4. But, as it’s not a /24 > network, openvpn try to add a route (0.0.0.0/0 or 0.0.0.0/1 and > 128.0.0.0/1) to a non-directly connected gateway. > > I would like to add a route like “89.234.186.4 dev tun0” by pushing > it to each client. But, if I add “push "route 89.234.186.4"” on the > server config, the client try to add 89.234.186.4 via 89.234.186.4. So > obviously, it’s not working.
Let's flip this around. What is your goal? And is it truly important for you that the VPN client have a public IP address on the tun adapter? If you want to have a public IP address on the tun adapter - it is possible but requires quite some understanding of how TCP/IP routing works and will require additional tweaks to both OpenVPN server and client. If you just want your VPN client to have a public IP address your VPN server controls when surfing the net, there are far easier ways to accomplish that. -- kind regards, David Sommerseth ------------------------------------------------------------------------------ _______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
