Re: [Openvpn-users] Add a directly connected route

2016-08-18 Thread David Sommerseth
On 18/08/16 15:54, Alarig Le Lay wrote: > My goal is to provide fixed public IPv4 and IPv6 to clients. The VPN is > only used in client mode, some people use this VPN to have their own > services at home without dyndns over a broadband access. > So, yes, I want public IP address on the tun interfac

Re: [Openvpn-users] Add a directly connected route

2016-08-18 Thread Alarig Le Lay
On Thu Aug 18 15:41:59 2016, David Sommerseth wrote: > 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 qu

Re: [Openvpn-users] Add a directly connected route

2016-08-18 Thread Jan Just Keijser
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

Re: [Openvpn-users] Add a directly connected route

2016-08-18 Thread Jan Just Keijser
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 n

Re: [Openvpn-users] Add a directly connected route

2016-08-18 Thread David Sommerseth
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 no

Re: [Openvpn-users] Add a directly connected route

2016-08-18 Thread Alarig Le Lay
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@arthu

Re: [Openvpn-users] Add a directly connected route

2016-08-18 Thread Joe Patterson
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. On Thu, Aug 18, 2016 at 8:53 AM Alarig Le Lay wrote: > Hi, > > I have a setup where each client have a /32 IPv4 (not /24) because the > /24 is no

[Openvpn-users] Add a directly connected route

2016-08-18 Thread Alarig Le Lay
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/