Adding route on client using OpenVPN












11















So this is my setup.
Laptop Running Ubuntu
OpenVPN version 2.3.2



I connect to a OpenVPN server that connects to an off-site network.



I get the OpenVPN client running and I can ping the VPN server. The server doesn't push any routes so I need to route on the client.



Adding the off-site networks to route to the VPNserver so that I can access the off site network.



So the problem I have is that my requests don't jump from 192.168.0.1 network to the off site 172...* one... Can I do anything about that on my client?
I don't have any ownership of the server and routs are not pushed from server now , in the future i don't know



tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
inet addr:10.242.2.6 P-t-P:10.242.2.5 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:100 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:12129 (12.1 KB)

wlan1 Link encap:Ethernet HWaddr 5c:93:a2:a0:6e:1b
inet addr:10.101.7.41 Bcast:10.101.31.255 Mask:255.255.224.0
inet6 addr: fe80::5e93:a2ff:fea0:6e1b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:355109 errors:0 dropped:0 overruns:0 frame:0
TX packets:206832 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:454685028 (454.6 MB) TX bytes:23942624 (23.9 MB)



Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 10.101.0.1 0.0.0.0 UG 0 0 0 wlan1
10.101.0.0 0.0.0.0 255.255.224.0 U 0 0 0 wlan1
10.242.2.1 10.242.2.5 255.255.255.255 UGH 0 0 0 tun0
10.242.2.5 0.0.0.0 255.255.255.255 UH 0 0 0 tun0
192.168.0.0 10.242.2.5 255.255.255.0 UG 0 0 0 tun0
192.168.82.0 10.242.2.5 255.255.255.0 UG 0 0 0 tun0









share|improve this question

























  • Routes can be added by pusing/pulling or manual configuration in the client configuration. Is your question about how to do this without pushing routes on the server or is your question how to push them from the server to the clients (or individual ones)? Please include in your question (edit it please): 1) Whether you have control over the configuration of the server. 2) Include client OpenVPN configuration (also server if 1 was yes). This way we can help you better.

    – gertvdijk
    Apr 23 '15 at 13:05


















11















So this is my setup.
Laptop Running Ubuntu
OpenVPN version 2.3.2



I connect to a OpenVPN server that connects to an off-site network.



I get the OpenVPN client running and I can ping the VPN server. The server doesn't push any routes so I need to route on the client.



Adding the off-site networks to route to the VPNserver so that I can access the off site network.



So the problem I have is that my requests don't jump from 192.168.0.1 network to the off site 172...* one... Can I do anything about that on my client?
I don't have any ownership of the server and routs are not pushed from server now , in the future i don't know



tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
inet addr:10.242.2.6 P-t-P:10.242.2.5 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:100 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:12129 (12.1 KB)

wlan1 Link encap:Ethernet HWaddr 5c:93:a2:a0:6e:1b
inet addr:10.101.7.41 Bcast:10.101.31.255 Mask:255.255.224.0
inet6 addr: fe80::5e93:a2ff:fea0:6e1b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:355109 errors:0 dropped:0 overruns:0 frame:0
TX packets:206832 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:454685028 (454.6 MB) TX bytes:23942624 (23.9 MB)



Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 10.101.0.1 0.0.0.0 UG 0 0 0 wlan1
10.101.0.0 0.0.0.0 255.255.224.0 U 0 0 0 wlan1
10.242.2.1 10.242.2.5 255.255.255.255 UGH 0 0 0 tun0
10.242.2.5 0.0.0.0 255.255.255.255 UH 0 0 0 tun0
192.168.0.0 10.242.2.5 255.255.255.0 UG 0 0 0 tun0
192.168.82.0 10.242.2.5 255.255.255.0 UG 0 0 0 tun0









share|improve this question

























  • Routes can be added by pusing/pulling or manual configuration in the client configuration. Is your question about how to do this without pushing routes on the server or is your question how to push them from the server to the clients (or individual ones)? Please include in your question (edit it please): 1) Whether you have control over the configuration of the server. 2) Include client OpenVPN configuration (also server if 1 was yes). This way we can help you better.

    – gertvdijk
    Apr 23 '15 at 13:05
















11












11








11


6






So this is my setup.
Laptop Running Ubuntu
OpenVPN version 2.3.2



I connect to a OpenVPN server that connects to an off-site network.



I get the OpenVPN client running and I can ping the VPN server. The server doesn't push any routes so I need to route on the client.



Adding the off-site networks to route to the VPNserver so that I can access the off site network.



So the problem I have is that my requests don't jump from 192.168.0.1 network to the off site 172...* one... Can I do anything about that on my client?
I don't have any ownership of the server and routs are not pushed from server now , in the future i don't know



tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
inet addr:10.242.2.6 P-t-P:10.242.2.5 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:100 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:12129 (12.1 KB)

wlan1 Link encap:Ethernet HWaddr 5c:93:a2:a0:6e:1b
inet addr:10.101.7.41 Bcast:10.101.31.255 Mask:255.255.224.0
inet6 addr: fe80::5e93:a2ff:fea0:6e1b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:355109 errors:0 dropped:0 overruns:0 frame:0
TX packets:206832 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:454685028 (454.6 MB) TX bytes:23942624 (23.9 MB)



Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 10.101.0.1 0.0.0.0 UG 0 0 0 wlan1
10.101.0.0 0.0.0.0 255.255.224.0 U 0 0 0 wlan1
10.242.2.1 10.242.2.5 255.255.255.255 UGH 0 0 0 tun0
10.242.2.5 0.0.0.0 255.255.255.255 UH 0 0 0 tun0
192.168.0.0 10.242.2.5 255.255.255.0 UG 0 0 0 tun0
192.168.82.0 10.242.2.5 255.255.255.0 UG 0 0 0 tun0









share|improve this question
















So this is my setup.
Laptop Running Ubuntu
OpenVPN version 2.3.2



I connect to a OpenVPN server that connects to an off-site network.



I get the OpenVPN client running and I can ping the VPN server. The server doesn't push any routes so I need to route on the client.



Adding the off-site networks to route to the VPNserver so that I can access the off site network.



So the problem I have is that my requests don't jump from 192.168.0.1 network to the off site 172...* one... Can I do anything about that on my client?
I don't have any ownership of the server and routs are not pushed from server now , in the future i don't know



tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
inet addr:10.242.2.6 P-t-P:10.242.2.5 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:100 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:12129 (12.1 KB)

wlan1 Link encap:Ethernet HWaddr 5c:93:a2:a0:6e:1b
inet addr:10.101.7.41 Bcast:10.101.31.255 Mask:255.255.224.0
inet6 addr: fe80::5e93:a2ff:fea0:6e1b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:355109 errors:0 dropped:0 overruns:0 frame:0
TX packets:206832 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:454685028 (454.6 MB) TX bytes:23942624 (23.9 MB)



Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 10.101.0.1 0.0.0.0 UG 0 0 0 wlan1
10.101.0.0 0.0.0.0 255.255.224.0 U 0 0 0 wlan1
10.242.2.1 10.242.2.5 255.255.255.255 UGH 0 0 0 tun0
10.242.2.5 0.0.0.0 255.255.255.255 UH 0 0 0 tun0
192.168.0.0 10.242.2.5 255.255.255.0 UG 0 0 0 tun0
192.168.82.0 10.242.2.5 255.255.255.0 UG 0 0 0 tun0






openvpn routing






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 11 '18 at 20:11









tomodachi

9,35542240




9,35542240










asked Apr 23 '15 at 12:44









JockeJocke

56114




56114













  • Routes can be added by pusing/pulling or manual configuration in the client configuration. Is your question about how to do this without pushing routes on the server or is your question how to push them from the server to the clients (or individual ones)? Please include in your question (edit it please): 1) Whether you have control over the configuration of the server. 2) Include client OpenVPN configuration (also server if 1 was yes). This way we can help you better.

    – gertvdijk
    Apr 23 '15 at 13:05





















  • Routes can be added by pusing/pulling or manual configuration in the client configuration. Is your question about how to do this without pushing routes on the server or is your question how to push them from the server to the clients (or individual ones)? Please include in your question (edit it please): 1) Whether you have control over the configuration of the server. 2) Include client OpenVPN configuration (also server if 1 was yes). This way we can help you better.

    – gertvdijk
    Apr 23 '15 at 13:05



















Routes can be added by pusing/pulling or manual configuration in the client configuration. Is your question about how to do this without pushing routes on the server or is your question how to push them from the server to the clients (or individual ones)? Please include in your question (edit it please): 1) Whether you have control over the configuration of the server. 2) Include client OpenVPN configuration (also server if 1 was yes). This way we can help you better.

– gertvdijk
Apr 23 '15 at 13:05







Routes can be added by pusing/pulling or manual configuration in the client configuration. Is your question about how to do this without pushing routes on the server or is your question how to push them from the server to the clients (or individual ones)? Please include in your question (edit it please): 1) Whether you have control over the configuration of the server. 2) Include client OpenVPN configuration (also server if 1 was yes). This way we can help you better.

– gertvdijk
Apr 23 '15 at 13:05












1 Answer
1






active

oldest

votes


















21














Looking at your routing table. There is no explicit route telling traffic to 172...* as you call it. To be sent to the VPN tun interface.



You have several options:





  1. If you have access to the openVPN server add this directive to the openvpn config:



    push "redirect-gateway def1 bypass-dhcp"


    This setting will route/force all traffic to pass through the VPN.
    The other alternative you have. Is to add a static route yourself on the client side




  2. Add the route manually on the client side in a terminal



    sudo route add -net 172.16.0.0/24 dev tun0



  3. openvpn has a directive for adding and removing of routes client side in your openvpn config file with
    with the route option.



    Adding:



    route 172.16.0.0 255.255.255.0


    to your openvpn config file on the vpn client.
    will add the route automatically when you connect




  4. Bonus: openvpn also has a
    up/down directive that allows you to launch a script on connect to VPN.
    This can allows you to do any custom action like setting DNS, routes etc. But it requires you to store the commands to execute in another file.



    So if you had the following to your openvpn client config file



    script-security 2 system
    up run-stuff-after-vpn-connect.sh


    Create a file named run-stuff-after-vpn-connect.sh (make sure it has execute permissions. And add:



    #!/bin/sh
    route add -net 172.16.0.0/24 dev tun0


    This will add the route as soon as the tunnel is up






Since you didn't give us the full declaration of your subnet in your question assuming its
172.16.0.0/24






share|improve this answer


























  • so if i add the up route add -net 172.16.0.0/24 dev tun in my client.conf file the rout should be shown in netstat -rn ?

    – Jocke
    Apr 23 '15 at 13:14











  • no the vpn does not go up if i add that line in client.conf

    – Jocke
    Apr 23 '15 at 13:20











  • where do i add the up route command ... ??

    – Jocke
    Apr 23 '15 at 13:47






  • 2





    @tomodachi I had to use dot notation to get this to work on an openvpn client (2.3.11) route 0.0.0.0 128.0.0.0

    – Matt
    Sep 23 '16 at 7:35






  • 4





    On my OpenVPN 2.3.13 (Windows 10), the option route 172.16.0.0/24 is not accepted, I have to use route 172.16.0.0 255.255.255.0 instead.

    – WoJ
    Nov 23 '16 at 7:17











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f612840%2fadding-route-on-client-using-openvpn%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









21














Looking at your routing table. There is no explicit route telling traffic to 172...* as you call it. To be sent to the VPN tun interface.



You have several options:





  1. If you have access to the openVPN server add this directive to the openvpn config:



    push "redirect-gateway def1 bypass-dhcp"


    This setting will route/force all traffic to pass through the VPN.
    The other alternative you have. Is to add a static route yourself on the client side




  2. Add the route manually on the client side in a terminal



    sudo route add -net 172.16.0.0/24 dev tun0



  3. openvpn has a directive for adding and removing of routes client side in your openvpn config file with
    with the route option.



    Adding:



    route 172.16.0.0 255.255.255.0


    to your openvpn config file on the vpn client.
    will add the route automatically when you connect




  4. Bonus: openvpn also has a
    up/down directive that allows you to launch a script on connect to VPN.
    This can allows you to do any custom action like setting DNS, routes etc. But it requires you to store the commands to execute in another file.



    So if you had the following to your openvpn client config file



    script-security 2 system
    up run-stuff-after-vpn-connect.sh


    Create a file named run-stuff-after-vpn-connect.sh (make sure it has execute permissions. And add:



    #!/bin/sh
    route add -net 172.16.0.0/24 dev tun0


    This will add the route as soon as the tunnel is up






Since you didn't give us the full declaration of your subnet in your question assuming its
172.16.0.0/24






share|improve this answer


























  • so if i add the up route add -net 172.16.0.0/24 dev tun in my client.conf file the rout should be shown in netstat -rn ?

    – Jocke
    Apr 23 '15 at 13:14











  • no the vpn does not go up if i add that line in client.conf

    – Jocke
    Apr 23 '15 at 13:20











  • where do i add the up route command ... ??

    – Jocke
    Apr 23 '15 at 13:47






  • 2





    @tomodachi I had to use dot notation to get this to work on an openvpn client (2.3.11) route 0.0.0.0 128.0.0.0

    – Matt
    Sep 23 '16 at 7:35






  • 4





    On my OpenVPN 2.3.13 (Windows 10), the option route 172.16.0.0/24 is not accepted, I have to use route 172.16.0.0 255.255.255.0 instead.

    – WoJ
    Nov 23 '16 at 7:17
















21














Looking at your routing table. There is no explicit route telling traffic to 172...* as you call it. To be sent to the VPN tun interface.



You have several options:





  1. If you have access to the openVPN server add this directive to the openvpn config:



    push "redirect-gateway def1 bypass-dhcp"


    This setting will route/force all traffic to pass through the VPN.
    The other alternative you have. Is to add a static route yourself on the client side




  2. Add the route manually on the client side in a terminal



    sudo route add -net 172.16.0.0/24 dev tun0



  3. openvpn has a directive for adding and removing of routes client side in your openvpn config file with
    with the route option.



    Adding:



    route 172.16.0.0 255.255.255.0


    to your openvpn config file on the vpn client.
    will add the route automatically when you connect




  4. Bonus: openvpn also has a
    up/down directive that allows you to launch a script on connect to VPN.
    This can allows you to do any custom action like setting DNS, routes etc. But it requires you to store the commands to execute in another file.



    So if you had the following to your openvpn client config file



    script-security 2 system
    up run-stuff-after-vpn-connect.sh


    Create a file named run-stuff-after-vpn-connect.sh (make sure it has execute permissions. And add:



    #!/bin/sh
    route add -net 172.16.0.0/24 dev tun0


    This will add the route as soon as the tunnel is up






Since you didn't give us the full declaration of your subnet in your question assuming its
172.16.0.0/24






share|improve this answer


























  • so if i add the up route add -net 172.16.0.0/24 dev tun in my client.conf file the rout should be shown in netstat -rn ?

    – Jocke
    Apr 23 '15 at 13:14











  • no the vpn does not go up if i add that line in client.conf

    – Jocke
    Apr 23 '15 at 13:20











  • where do i add the up route command ... ??

    – Jocke
    Apr 23 '15 at 13:47






  • 2





    @tomodachi I had to use dot notation to get this to work on an openvpn client (2.3.11) route 0.0.0.0 128.0.0.0

    – Matt
    Sep 23 '16 at 7:35






  • 4





    On my OpenVPN 2.3.13 (Windows 10), the option route 172.16.0.0/24 is not accepted, I have to use route 172.16.0.0 255.255.255.0 instead.

    – WoJ
    Nov 23 '16 at 7:17














21












21








21







Looking at your routing table. There is no explicit route telling traffic to 172...* as you call it. To be sent to the VPN tun interface.



You have several options:





  1. If you have access to the openVPN server add this directive to the openvpn config:



    push "redirect-gateway def1 bypass-dhcp"


    This setting will route/force all traffic to pass through the VPN.
    The other alternative you have. Is to add a static route yourself on the client side




  2. Add the route manually on the client side in a terminal



    sudo route add -net 172.16.0.0/24 dev tun0



  3. openvpn has a directive for adding and removing of routes client side in your openvpn config file with
    with the route option.



    Adding:



    route 172.16.0.0 255.255.255.0


    to your openvpn config file on the vpn client.
    will add the route automatically when you connect




  4. Bonus: openvpn also has a
    up/down directive that allows you to launch a script on connect to VPN.
    This can allows you to do any custom action like setting DNS, routes etc. But it requires you to store the commands to execute in another file.



    So if you had the following to your openvpn client config file



    script-security 2 system
    up run-stuff-after-vpn-connect.sh


    Create a file named run-stuff-after-vpn-connect.sh (make sure it has execute permissions. And add:



    #!/bin/sh
    route add -net 172.16.0.0/24 dev tun0


    This will add the route as soon as the tunnel is up






Since you didn't give us the full declaration of your subnet in your question assuming its
172.16.0.0/24






share|improve this answer















Looking at your routing table. There is no explicit route telling traffic to 172...* as you call it. To be sent to the VPN tun interface.



You have several options:





  1. If you have access to the openVPN server add this directive to the openvpn config:



    push "redirect-gateway def1 bypass-dhcp"


    This setting will route/force all traffic to pass through the VPN.
    The other alternative you have. Is to add a static route yourself on the client side




  2. Add the route manually on the client side in a terminal



    sudo route add -net 172.16.0.0/24 dev tun0



  3. openvpn has a directive for adding and removing of routes client side in your openvpn config file with
    with the route option.



    Adding:



    route 172.16.0.0 255.255.255.0


    to your openvpn config file on the vpn client.
    will add the route automatically when you connect




  4. Bonus: openvpn also has a
    up/down directive that allows you to launch a script on connect to VPN.
    This can allows you to do any custom action like setting DNS, routes etc. But it requires you to store the commands to execute in another file.



    So if you had the following to your openvpn client config file



    script-security 2 system
    up run-stuff-after-vpn-connect.sh


    Create a file named run-stuff-after-vpn-connect.sh (make sure it has execute permissions. And add:



    #!/bin/sh
    route add -net 172.16.0.0/24 dev tun0


    This will add the route as soon as the tunnel is up






Since you didn't give us the full declaration of your subnet in your question assuming its
172.16.0.0/24







share|improve this answer














share|improve this answer



share|improve this answer








edited 2 hours ago









Community

1




1










answered Apr 23 '15 at 13:07









tomodachitomodachi

9,35542240




9,35542240













  • so if i add the up route add -net 172.16.0.0/24 dev tun in my client.conf file the rout should be shown in netstat -rn ?

    – Jocke
    Apr 23 '15 at 13:14











  • no the vpn does not go up if i add that line in client.conf

    – Jocke
    Apr 23 '15 at 13:20











  • where do i add the up route command ... ??

    – Jocke
    Apr 23 '15 at 13:47






  • 2





    @tomodachi I had to use dot notation to get this to work on an openvpn client (2.3.11) route 0.0.0.0 128.0.0.0

    – Matt
    Sep 23 '16 at 7:35






  • 4





    On my OpenVPN 2.3.13 (Windows 10), the option route 172.16.0.0/24 is not accepted, I have to use route 172.16.0.0 255.255.255.0 instead.

    – WoJ
    Nov 23 '16 at 7:17



















  • so if i add the up route add -net 172.16.0.0/24 dev tun in my client.conf file the rout should be shown in netstat -rn ?

    – Jocke
    Apr 23 '15 at 13:14











  • no the vpn does not go up if i add that line in client.conf

    – Jocke
    Apr 23 '15 at 13:20











  • where do i add the up route command ... ??

    – Jocke
    Apr 23 '15 at 13:47






  • 2





    @tomodachi I had to use dot notation to get this to work on an openvpn client (2.3.11) route 0.0.0.0 128.0.0.0

    – Matt
    Sep 23 '16 at 7:35






  • 4





    On my OpenVPN 2.3.13 (Windows 10), the option route 172.16.0.0/24 is not accepted, I have to use route 172.16.0.0 255.255.255.0 instead.

    – WoJ
    Nov 23 '16 at 7:17

















so if i add the up route add -net 172.16.0.0/24 dev tun in my client.conf file the rout should be shown in netstat -rn ?

– Jocke
Apr 23 '15 at 13:14





so if i add the up route add -net 172.16.0.0/24 dev tun in my client.conf file the rout should be shown in netstat -rn ?

– Jocke
Apr 23 '15 at 13:14













no the vpn does not go up if i add that line in client.conf

– Jocke
Apr 23 '15 at 13:20





no the vpn does not go up if i add that line in client.conf

– Jocke
Apr 23 '15 at 13:20













where do i add the up route command ... ??

– Jocke
Apr 23 '15 at 13:47





where do i add the up route command ... ??

– Jocke
Apr 23 '15 at 13:47




2




2





@tomodachi I had to use dot notation to get this to work on an openvpn client (2.3.11) route 0.0.0.0 128.0.0.0

– Matt
Sep 23 '16 at 7:35





@tomodachi I had to use dot notation to get this to work on an openvpn client (2.3.11) route 0.0.0.0 128.0.0.0

– Matt
Sep 23 '16 at 7:35




4




4





On my OpenVPN 2.3.13 (Windows 10), the option route 172.16.0.0/24 is not accepted, I have to use route 172.16.0.0 255.255.255.0 instead.

– WoJ
Nov 23 '16 at 7:17





On my OpenVPN 2.3.13 (Windows 10), the option route 172.16.0.0/24 is not accepted, I have to use route 172.16.0.0 255.255.255.0 instead.

– WoJ
Nov 23 '16 at 7:17


















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f612840%2fadding-route-on-client-using-openvpn%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

GameSpot

connect to host localhost port 22: Connection refused

Getting a Wifi WPA2 wifi connection