Understanding Routing Table with OpenVPNWhy is my router not routing?Windows 7 network connectionsHow Can I...

Are Warlocks Arcane or Divine?

How to deal with or prevent idle in the test team?

A known event to a history junkie

What to do when my ideas aren't chosen, when I strongly disagree with the chosen solution?

Simulating a probability of 1 of 2^N with less than N random bits

What (else) happened July 1st 1858 in London?

Word describing multiple paths to the same abstract outcome

What was required to accept "troll"?

Is there a problem with hiding "forgot password" until it's needed?

For airliners, what prevents wing strikes on landing in bad weather?

Perfect riffle shuffles

Java - What do constructor type arguments mean when placed *before* the type?

Could solar power be utilized and substitute coal in the 19th century?

Superhero words!

Is there an Impartial Brexit Deal comparison site?

Can I rely on these GitHub repository files?

I'm in charge of equipment buying but no one's ever happy with what I choose. How to fix this?

Can the electrostatic force be infinite in magnitude?

How do ultrasonic sensors differentiate between transmitted and received signals?

I2C signal and power over long range (10meter cable)

Can I Retrieve Email Addresses from BCC?

Is exact Kanji stroke length important?

Giant Toughroad SLR 2 for 200 miles in two days, will it make it?

Reply ‘no position’ while the job posting is still there (‘HiWi’ position in Germany)



Understanding Routing Table with OpenVPN


Why is my router not routing?Windows 7 network connectionsHow Can I enable rdp access to a laptop after it connects to VPN?OpenVPN stopped working, what could have happened?How to setup Internet gateway Windows Server 2008 by Routing and Remote AccessOpenVPN routing table changeRouting all traffic over VPN on Ubuntu LinuxInvalid IP Configuration errorWhy does my hostname resolve to IP of virtual nic and not the physical one?default gateway after network card damage













2















Network layout: Laptop (OpenVPN client) <-> router with 192.168.1.xxx subnet <-> internet <-> Home router (running DD-WRT with OpenVPN server) with 192.168.11.xxx subnet



The VPN server is operating in layer 2 mode (bridge). All of my internet traffic passes through the VPN tunnel. My home router & VPN have an external IP of 68.64.127.82.



My laptop (VPN client) has an IP address on the physical LAN of 192.168.1.40. My IP address on the VPN is 192.168.11.50.



Here is my question: What makes all the internet traffic pass through the VPN tunnel?



Network Destination        Netmask          Gateway       Interface  Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.40 20
0.0.0.0 128.0.0.0 192.168.11.1 192.168.11.50 30


The first line says everything should go the router I'm physically connected to (not the VPN router). The second line makes no sense to me. The 192.168.11.xxx subnet is on my VPN. How can you have a 0.0.0.0 destination with a netmask?!?



Question 2: What does the 128.0.0.0 netmask mean with a 0.0.0.0 destination?



Question 3: Why does the second line take priority over the first line?



Thanks for your help!





Here is my full routing table:



Here is my full routing table:



C:Usersowner>route print
===========================================================================
Interface List
19...00 ff 79 ee e1 6b ......TAP-Windows Adapter V9
10...00 1a 4b 13 d2 92 ......Broadcom NetLink (TM) Gigabit Ethernet
1...........................Software Loopback Interface 1
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.40 20
0.0.0.0 128.0.0.0 192.168.11.1 192.168.11.50 30
68.64.127.82 255.255.255.255 192.168.1.1 192.168.1.40 20
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
128.0.0.0 128.0.0.0 192.168.11.1 192.168.11.50 30
192.168.1.0 255.255.255.0 On-link 192.168.1.40 276
192.168.1.40 255.255.255.255 On-link 192.168.1.40 276
192.168.1.255 255.255.255.255 On-link 192.168.1.40 276
192.168.11.0 255.255.255.0 On-link 192.168.11.50 286
192.168.11.50 255.255.255.255 On-link 192.168.11.50 286
192.168.11.255 255.255.255.255 On-link 192.168.11.50 286
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.1.40 276
224.0.0.0 240.0.0.0 On-link 192.168.11.50 286
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.1.40 276
255.255.255.255 255.255.255.255 On-link 192.168.11.50 286
===========================================================================


Here is my ipconfig:



Windows IP Configuration

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Windows Adapter V9
Physical Address. . . . . . . . . : 00-FF-79-EE-E1-6B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::c1f8:5d3:e14:dba6%19(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.11.50(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, December 11, 2014 11:20:53 AM
Lease Expires . . . . . . . . . . : Friday, December 11, 2015 11:20:53 AM
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 192.168.11.0
DHCPv6 IAID . . . . . . . . . . . : 520159097
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-A1-5A-F6-00-1A-4B-6B-D2-7C

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet
Physical Address. . . . . . . . . : 00-1A-4B-13-D2-92
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::61c0:c604:f3e5:498%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.40(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, December 11, 2014 11:20:35 AM
Lease Expires . . . . . . . . . . : Friday, December 12, 2014 11:20:35 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 234887755
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-A1-5A-F6-00-1A-4B-13-D2-92

DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled









share|improve this question





























    2















    Network layout: Laptop (OpenVPN client) <-> router with 192.168.1.xxx subnet <-> internet <-> Home router (running DD-WRT with OpenVPN server) with 192.168.11.xxx subnet



    The VPN server is operating in layer 2 mode (bridge). All of my internet traffic passes through the VPN tunnel. My home router & VPN have an external IP of 68.64.127.82.



    My laptop (VPN client) has an IP address on the physical LAN of 192.168.1.40. My IP address on the VPN is 192.168.11.50.



    Here is my question: What makes all the internet traffic pass through the VPN tunnel?



    Network Destination        Netmask          Gateway       Interface  Metric
    0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.40 20
    0.0.0.0 128.0.0.0 192.168.11.1 192.168.11.50 30


    The first line says everything should go the router I'm physically connected to (not the VPN router). The second line makes no sense to me. The 192.168.11.xxx subnet is on my VPN. How can you have a 0.0.0.0 destination with a netmask?!?



    Question 2: What does the 128.0.0.0 netmask mean with a 0.0.0.0 destination?



    Question 3: Why does the second line take priority over the first line?



    Thanks for your help!





    Here is my full routing table:



    Here is my full routing table:



    C:Usersowner>route print
    ===========================================================================
    Interface List
    19...00 ff 79 ee e1 6b ......TAP-Windows Adapter V9
    10...00 1a 4b 13 d2 92 ......Broadcom NetLink (TM) Gigabit Ethernet
    1...........................Software Loopback Interface 1
    ===========================================================================

    IPv4 Route Table
    ===========================================================================
    Active Routes:
    Network Destination Netmask Gateway Interface Metric
    0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.40 20
    0.0.0.0 128.0.0.0 192.168.11.1 192.168.11.50 30
    68.64.127.82 255.255.255.255 192.168.1.1 192.168.1.40 20
    127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
    127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
    127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
    128.0.0.0 128.0.0.0 192.168.11.1 192.168.11.50 30
    192.168.1.0 255.255.255.0 On-link 192.168.1.40 276
    192.168.1.40 255.255.255.255 On-link 192.168.1.40 276
    192.168.1.255 255.255.255.255 On-link 192.168.1.40 276
    192.168.11.0 255.255.255.0 On-link 192.168.11.50 286
    192.168.11.50 255.255.255.255 On-link 192.168.11.50 286
    192.168.11.255 255.255.255.255 On-link 192.168.11.50 286
    224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
    224.0.0.0 240.0.0.0 On-link 192.168.1.40 276
    224.0.0.0 240.0.0.0 On-link 192.168.11.50 286
    255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
    255.255.255.255 255.255.255.255 On-link 192.168.1.40 276
    255.255.255.255 255.255.255.255 On-link 192.168.11.50 286
    ===========================================================================


    Here is my ipconfig:



    Windows IP Configuration

    Ethernet adapter Local Area Connection 2:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : TAP-Windows Adapter V9
    Physical Address. . . . . . . . . : 00-FF-79-EE-E1-6B
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::c1f8:5d3:e14:dba6%19(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.11.50(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : Thursday, December 11, 2014 11:20:53 AM
    Lease Expires . . . . . . . . . . : Friday, December 11, 2015 11:20:53 AM
    Default Gateway . . . . . . . . . :
    DHCP Server . . . . . . . . . . . : 192.168.11.0
    DHCPv6 IAID . . . . . . . . . . . : 520159097
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-A1-5A-F6-00-1A-4B-6B-D2-7C

    DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
    fec0:0:0:ffff::2%1
    fec0:0:0:ffff::3%1
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Local Area Connection:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet
    Physical Address. . . . . . . . . : 00-1A-4B-13-D2-92
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::61c0:c604:f3e5:498%10(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.40(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : Thursday, December 11, 2014 11:20:35 AM
    Lease Expires . . . . . . . . . . : Friday, December 12, 2014 11:20:35 AM
    Default Gateway . . . . . . . . . : 192.168.1.1
    DHCP Server . . . . . . . . . . . : 192.168.1.1
    DHCPv6 IAID . . . . . . . . . . . : 234887755
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-A1-5A-F6-00-1A-4B-13-D2-92

    DNS Servers . . . . . . . . . . . : 192.168.1.1
    NetBIOS over Tcpip. . . . . . . . : Enabled









    share|improve this question



























      2












      2








      2


      5






      Network layout: Laptop (OpenVPN client) <-> router with 192.168.1.xxx subnet <-> internet <-> Home router (running DD-WRT with OpenVPN server) with 192.168.11.xxx subnet



      The VPN server is operating in layer 2 mode (bridge). All of my internet traffic passes through the VPN tunnel. My home router & VPN have an external IP of 68.64.127.82.



      My laptop (VPN client) has an IP address on the physical LAN of 192.168.1.40. My IP address on the VPN is 192.168.11.50.



      Here is my question: What makes all the internet traffic pass through the VPN tunnel?



      Network Destination        Netmask          Gateway       Interface  Metric
      0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.40 20
      0.0.0.0 128.0.0.0 192.168.11.1 192.168.11.50 30


      The first line says everything should go the router I'm physically connected to (not the VPN router). The second line makes no sense to me. The 192.168.11.xxx subnet is on my VPN. How can you have a 0.0.0.0 destination with a netmask?!?



      Question 2: What does the 128.0.0.0 netmask mean with a 0.0.0.0 destination?



      Question 3: Why does the second line take priority over the first line?



      Thanks for your help!





      Here is my full routing table:



      Here is my full routing table:



      C:Usersowner>route print
      ===========================================================================
      Interface List
      19...00 ff 79 ee e1 6b ......TAP-Windows Adapter V9
      10...00 1a 4b 13 d2 92 ......Broadcom NetLink (TM) Gigabit Ethernet
      1...........................Software Loopback Interface 1
      ===========================================================================

      IPv4 Route Table
      ===========================================================================
      Active Routes:
      Network Destination Netmask Gateway Interface Metric
      0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.40 20
      0.0.0.0 128.0.0.0 192.168.11.1 192.168.11.50 30
      68.64.127.82 255.255.255.255 192.168.1.1 192.168.1.40 20
      127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
      127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
      127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
      128.0.0.0 128.0.0.0 192.168.11.1 192.168.11.50 30
      192.168.1.0 255.255.255.0 On-link 192.168.1.40 276
      192.168.1.40 255.255.255.255 On-link 192.168.1.40 276
      192.168.1.255 255.255.255.255 On-link 192.168.1.40 276
      192.168.11.0 255.255.255.0 On-link 192.168.11.50 286
      192.168.11.50 255.255.255.255 On-link 192.168.11.50 286
      192.168.11.255 255.255.255.255 On-link 192.168.11.50 286
      224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
      224.0.0.0 240.0.0.0 On-link 192.168.1.40 276
      224.0.0.0 240.0.0.0 On-link 192.168.11.50 286
      255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
      255.255.255.255 255.255.255.255 On-link 192.168.1.40 276
      255.255.255.255 255.255.255.255 On-link 192.168.11.50 286
      ===========================================================================


      Here is my ipconfig:



      Windows IP Configuration

      Ethernet adapter Local Area Connection 2:

      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : TAP-Windows Adapter V9
      Physical Address. . . . . . . . . : 00-FF-79-EE-E1-6B
      DHCP Enabled. . . . . . . . . . . : Yes
      Autoconfiguration Enabled . . . . : Yes
      Link-local IPv6 Address . . . . . : fe80::c1f8:5d3:e14:dba6%19(Preferred)
      IPv4 Address. . . . . . . . . . . : 192.168.11.50(Preferred)
      Subnet Mask . . . . . . . . . . . : 255.255.255.0
      Lease Obtained. . . . . . . . . . : Thursday, December 11, 2014 11:20:53 AM
      Lease Expires . . . . . . . . . . : Friday, December 11, 2015 11:20:53 AM
      Default Gateway . . . . . . . . . :
      DHCP Server . . . . . . . . . . . : 192.168.11.0
      DHCPv6 IAID . . . . . . . . . . . : 520159097
      DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-A1-5A-F6-00-1A-4B-6B-D2-7C

      DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
      fec0:0:0:ffff::2%1
      fec0:0:0:ffff::3%1
      NetBIOS over Tcpip. . . . . . . . : Enabled

      Ethernet adapter Local Area Connection:

      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet
      Physical Address. . . . . . . . . : 00-1A-4B-13-D2-92
      DHCP Enabled. . . . . . . . . . . : Yes
      Autoconfiguration Enabled . . . . : Yes
      Link-local IPv6 Address . . . . . : fe80::61c0:c604:f3e5:498%10(Preferred)
      IPv4 Address. . . . . . . . . . . : 192.168.1.40(Preferred)
      Subnet Mask . . . . . . . . . . . : 255.255.255.0
      Lease Obtained. . . . . . . . . . : Thursday, December 11, 2014 11:20:35 AM
      Lease Expires . . . . . . . . . . : Friday, December 12, 2014 11:20:35 AM
      Default Gateway . . . . . . . . . : 192.168.1.1
      DHCP Server . . . . . . . . . . . : 192.168.1.1
      DHCPv6 IAID . . . . . . . . . . . : 234887755
      DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-A1-5A-F6-00-1A-4B-13-D2-92

      DNS Servers . . . . . . . . . . . : 192.168.1.1
      NetBIOS over Tcpip. . . . . . . . : Enabled









      share|improve this question
















      Network layout: Laptop (OpenVPN client) <-> router with 192.168.1.xxx subnet <-> internet <-> Home router (running DD-WRT with OpenVPN server) with 192.168.11.xxx subnet



      The VPN server is operating in layer 2 mode (bridge). All of my internet traffic passes through the VPN tunnel. My home router & VPN have an external IP of 68.64.127.82.



      My laptop (VPN client) has an IP address on the physical LAN of 192.168.1.40. My IP address on the VPN is 192.168.11.50.



      Here is my question: What makes all the internet traffic pass through the VPN tunnel?



      Network Destination        Netmask          Gateway       Interface  Metric
      0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.40 20
      0.0.0.0 128.0.0.0 192.168.11.1 192.168.11.50 30


      The first line says everything should go the router I'm physically connected to (not the VPN router). The second line makes no sense to me. The 192.168.11.xxx subnet is on my VPN. How can you have a 0.0.0.0 destination with a netmask?!?



      Question 2: What does the 128.0.0.0 netmask mean with a 0.0.0.0 destination?



      Question 3: Why does the second line take priority over the first line?



      Thanks for your help!





      Here is my full routing table:



      Here is my full routing table:



      C:Usersowner>route print
      ===========================================================================
      Interface List
      19...00 ff 79 ee e1 6b ......TAP-Windows Adapter V9
      10...00 1a 4b 13 d2 92 ......Broadcom NetLink (TM) Gigabit Ethernet
      1...........................Software Loopback Interface 1
      ===========================================================================

      IPv4 Route Table
      ===========================================================================
      Active Routes:
      Network Destination Netmask Gateway Interface Metric
      0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.40 20
      0.0.0.0 128.0.0.0 192.168.11.1 192.168.11.50 30
      68.64.127.82 255.255.255.255 192.168.1.1 192.168.1.40 20
      127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
      127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
      127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
      128.0.0.0 128.0.0.0 192.168.11.1 192.168.11.50 30
      192.168.1.0 255.255.255.0 On-link 192.168.1.40 276
      192.168.1.40 255.255.255.255 On-link 192.168.1.40 276
      192.168.1.255 255.255.255.255 On-link 192.168.1.40 276
      192.168.11.0 255.255.255.0 On-link 192.168.11.50 286
      192.168.11.50 255.255.255.255 On-link 192.168.11.50 286
      192.168.11.255 255.255.255.255 On-link 192.168.11.50 286
      224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
      224.0.0.0 240.0.0.0 On-link 192.168.1.40 276
      224.0.0.0 240.0.0.0 On-link 192.168.11.50 286
      255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
      255.255.255.255 255.255.255.255 On-link 192.168.1.40 276
      255.255.255.255 255.255.255.255 On-link 192.168.11.50 286
      ===========================================================================


      Here is my ipconfig:



      Windows IP Configuration

      Ethernet adapter Local Area Connection 2:

      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : TAP-Windows Adapter V9
      Physical Address. . . . . . . . . : 00-FF-79-EE-E1-6B
      DHCP Enabled. . . . . . . . . . . : Yes
      Autoconfiguration Enabled . . . . : Yes
      Link-local IPv6 Address . . . . . : fe80::c1f8:5d3:e14:dba6%19(Preferred)
      IPv4 Address. . . . . . . . . . . : 192.168.11.50(Preferred)
      Subnet Mask . . . . . . . . . . . : 255.255.255.0
      Lease Obtained. . . . . . . . . . : Thursday, December 11, 2014 11:20:53 AM
      Lease Expires . . . . . . . . . . : Friday, December 11, 2015 11:20:53 AM
      Default Gateway . . . . . . . . . :
      DHCP Server . . . . . . . . . . . : 192.168.11.0
      DHCPv6 IAID . . . . . . . . . . . : 520159097
      DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-A1-5A-F6-00-1A-4B-6B-D2-7C

      DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
      fec0:0:0:ffff::2%1
      fec0:0:0:ffff::3%1
      NetBIOS over Tcpip. . . . . . . . : Enabled

      Ethernet adapter Local Area Connection:

      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet
      Physical Address. . . . . . . . . : 00-1A-4B-13-D2-92
      DHCP Enabled. . . . . . . . . . . : Yes
      Autoconfiguration Enabled . . . . : Yes
      Link-local IPv6 Address . . . . . : fe80::61c0:c604:f3e5:498%10(Preferred)
      IPv4 Address. . . . . . . . . . . : 192.168.1.40(Preferred)
      Subnet Mask . . . . . . . . . . . : 255.255.255.0
      Lease Obtained. . . . . . . . . . : Thursday, December 11, 2014 11:20:35 AM
      Lease Expires . . . . . . . . . . : Friday, December 12, 2014 11:20:35 AM
      Default Gateway . . . . . . . . . : 192.168.1.1
      DHCP Server . . . . . . . . . . . : 192.168.1.1
      DHCPv6 IAID . . . . . . . . . . . : 234887755
      DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-A1-5A-F6-00-1A-4B-13-D2-92

      DNS Servers . . . . . . . . . . . : 192.168.1.1
      NetBIOS over Tcpip. . . . . . . . : Enabled






      networking router vpn openvpn






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 5 '15 at 14:19









      That Brazilian Guy

      4,80375391




      4,80375391










      asked Dec 11 '14 at 17:50









      pkSMLpkSML

      1521313




      1521313






















          2 Answers
          2






          active

          oldest

          votes


















          3














          Solved! Thanks to eibgrad at the DD-WRT forums. Here is his answer:



          (Source: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=277001 )



          It's just a clever hack/trick. 

          There’s actually TWO important extra routes the VPN adds:

          128.0.0.0/128.0.0.0 (covers 0.0.0.0 thru 127.255.255.255)
          0.0.0.0/128.0.0.0 (covers 128.0.0.0 thru 255.255.255.255)

          The reason this works is because when it comes to routing, a more specific route is always preferred over a more general route. And 0.0.0.0/0.0.0.0 (the default gateway) is as general as it gets. But if we insert the above two routes, the fact they are more specific means one of them will always be chosen before 0.0.0.0/0.0.0.0 since those two routes still cover the entire IP spectrum (0.0.0.0 thru 255.255.255.255).

          VPNs do this to avoid messing w/ existing routes. They don’t need to delete anything that was already there, or even examine the routing table. They just add their own routes when the VPN comes up, and remove them when the VPN is shutdown. Simple.





          share|improve this answer



















          • 3





            Aren't IP address ranges swapped here? 0.0.0.0/128.0.0.0 covers 0.0.0.0 - 127.255.255.255 and 128.0.0.0/128.0.0.0 covers 128.0.0.0 - 255.255.255.255

            – Bojan Komazec
            Feb 19 '16 at 16:07



















          0














          @Bojan Komazec is right



          the 0.0.0.0/1 binary format is like blew:



          ip   : 00000000.00000000.00000000.00000000
          mask : 10000000.00000000.00000000.00000000

          result the subet like this:
          01111111.00000000.00000000.00000000
          01111110.00000000.00000000.00000000
          01111101.00000000.00000000.00000000
          ....


          So 0.0.0.0/1 covers 0.0.0.0 - 127.255.255.255



          the 128.0.0.0/1 binary format is like blew:



          ip   : 10000000.00000000.00000000.00000000
          mask : 10000000.00000000.00000000.00000000

          result the subet like this:
          11111111.00000000.00000000.00000000
          11111110.00000000.00000000.00000000
          11111101.00000000.00000000.00000000


          So 127.0.0.0/1 covers 128.0.0.1 - 255.255.255.255





          share























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            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%2fsuperuser.com%2fquestions%2f851462%2funderstanding-routing-table-with-openvpn%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            3














            Solved! Thanks to eibgrad at the DD-WRT forums. Here is his answer:



            (Source: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=277001 )



            It's just a clever hack/trick. 

            There’s actually TWO important extra routes the VPN adds:

            128.0.0.0/128.0.0.0 (covers 0.0.0.0 thru 127.255.255.255)
            0.0.0.0/128.0.0.0 (covers 128.0.0.0 thru 255.255.255.255)

            The reason this works is because when it comes to routing, a more specific route is always preferred over a more general route. And 0.0.0.0/0.0.0.0 (the default gateway) is as general as it gets. But if we insert the above two routes, the fact they are more specific means one of them will always be chosen before 0.0.0.0/0.0.0.0 since those two routes still cover the entire IP spectrum (0.0.0.0 thru 255.255.255.255).

            VPNs do this to avoid messing w/ existing routes. They don’t need to delete anything that was already there, or even examine the routing table. They just add their own routes when the VPN comes up, and remove them when the VPN is shutdown. Simple.





            share|improve this answer



















            • 3





              Aren't IP address ranges swapped here? 0.0.0.0/128.0.0.0 covers 0.0.0.0 - 127.255.255.255 and 128.0.0.0/128.0.0.0 covers 128.0.0.0 - 255.255.255.255

              – Bojan Komazec
              Feb 19 '16 at 16:07
















            3














            Solved! Thanks to eibgrad at the DD-WRT forums. Here is his answer:



            (Source: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=277001 )



            It's just a clever hack/trick. 

            There’s actually TWO important extra routes the VPN adds:

            128.0.0.0/128.0.0.0 (covers 0.0.0.0 thru 127.255.255.255)
            0.0.0.0/128.0.0.0 (covers 128.0.0.0 thru 255.255.255.255)

            The reason this works is because when it comes to routing, a more specific route is always preferred over a more general route. And 0.0.0.0/0.0.0.0 (the default gateway) is as general as it gets. But if we insert the above two routes, the fact they are more specific means one of them will always be chosen before 0.0.0.0/0.0.0.0 since those two routes still cover the entire IP spectrum (0.0.0.0 thru 255.255.255.255).

            VPNs do this to avoid messing w/ existing routes. They don’t need to delete anything that was already there, or even examine the routing table. They just add their own routes when the VPN comes up, and remove them when the VPN is shutdown. Simple.





            share|improve this answer



















            • 3





              Aren't IP address ranges swapped here? 0.0.0.0/128.0.0.0 covers 0.0.0.0 - 127.255.255.255 and 128.0.0.0/128.0.0.0 covers 128.0.0.0 - 255.255.255.255

              – Bojan Komazec
              Feb 19 '16 at 16:07














            3












            3








            3







            Solved! Thanks to eibgrad at the DD-WRT forums. Here is his answer:



            (Source: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=277001 )



            It's just a clever hack/trick. 

            There’s actually TWO important extra routes the VPN adds:

            128.0.0.0/128.0.0.0 (covers 0.0.0.0 thru 127.255.255.255)
            0.0.0.0/128.0.0.0 (covers 128.0.0.0 thru 255.255.255.255)

            The reason this works is because when it comes to routing, a more specific route is always preferred over a more general route. And 0.0.0.0/0.0.0.0 (the default gateway) is as general as it gets. But if we insert the above two routes, the fact they are more specific means one of them will always be chosen before 0.0.0.0/0.0.0.0 since those two routes still cover the entire IP spectrum (0.0.0.0 thru 255.255.255.255).

            VPNs do this to avoid messing w/ existing routes. They don’t need to delete anything that was already there, or even examine the routing table. They just add their own routes when the VPN comes up, and remove them when the VPN is shutdown. Simple.





            share|improve this answer













            Solved! Thanks to eibgrad at the DD-WRT forums. Here is his answer:



            (Source: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=277001 )



            It's just a clever hack/trick. 

            There’s actually TWO important extra routes the VPN adds:

            128.0.0.0/128.0.0.0 (covers 0.0.0.0 thru 127.255.255.255)
            0.0.0.0/128.0.0.0 (covers 128.0.0.0 thru 255.255.255.255)

            The reason this works is because when it comes to routing, a more specific route is always preferred over a more general route. And 0.0.0.0/0.0.0.0 (the default gateway) is as general as it gets. But if we insert the above two routes, the fact they are more specific means one of them will always be chosen before 0.0.0.0/0.0.0.0 since those two routes still cover the entire IP spectrum (0.0.0.0 thru 255.255.255.255).

            VPNs do this to avoid messing w/ existing routes. They don’t need to delete anything that was already there, or even examine the routing table. They just add their own routes when the VPN comes up, and remove them when the VPN is shutdown. Simple.






            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Dec 11 '14 at 21:10









            pkSMLpkSML

            1521313




            1521313








            • 3





              Aren't IP address ranges swapped here? 0.0.0.0/128.0.0.0 covers 0.0.0.0 - 127.255.255.255 and 128.0.0.0/128.0.0.0 covers 128.0.0.0 - 255.255.255.255

              – Bojan Komazec
              Feb 19 '16 at 16:07














            • 3





              Aren't IP address ranges swapped here? 0.0.0.0/128.0.0.0 covers 0.0.0.0 - 127.255.255.255 and 128.0.0.0/128.0.0.0 covers 128.0.0.0 - 255.255.255.255

              – Bojan Komazec
              Feb 19 '16 at 16:07








            3




            3





            Aren't IP address ranges swapped here? 0.0.0.0/128.0.0.0 covers 0.0.0.0 - 127.255.255.255 and 128.0.0.0/128.0.0.0 covers 128.0.0.0 - 255.255.255.255

            – Bojan Komazec
            Feb 19 '16 at 16:07





            Aren't IP address ranges swapped here? 0.0.0.0/128.0.0.0 covers 0.0.0.0 - 127.255.255.255 and 128.0.0.0/128.0.0.0 covers 128.0.0.0 - 255.255.255.255

            – Bojan Komazec
            Feb 19 '16 at 16:07













            0














            @Bojan Komazec is right



            the 0.0.0.0/1 binary format is like blew:



            ip   : 00000000.00000000.00000000.00000000
            mask : 10000000.00000000.00000000.00000000

            result the subet like this:
            01111111.00000000.00000000.00000000
            01111110.00000000.00000000.00000000
            01111101.00000000.00000000.00000000
            ....


            So 0.0.0.0/1 covers 0.0.0.0 - 127.255.255.255



            the 128.0.0.0/1 binary format is like blew:



            ip   : 10000000.00000000.00000000.00000000
            mask : 10000000.00000000.00000000.00000000

            result the subet like this:
            11111111.00000000.00000000.00000000
            11111110.00000000.00000000.00000000
            11111101.00000000.00000000.00000000


            So 127.0.0.0/1 covers 128.0.0.1 - 255.255.255.255





            share




























              0














              @Bojan Komazec is right



              the 0.0.0.0/1 binary format is like blew:



              ip   : 00000000.00000000.00000000.00000000
              mask : 10000000.00000000.00000000.00000000

              result the subet like this:
              01111111.00000000.00000000.00000000
              01111110.00000000.00000000.00000000
              01111101.00000000.00000000.00000000
              ....


              So 0.0.0.0/1 covers 0.0.0.0 - 127.255.255.255



              the 128.0.0.0/1 binary format is like blew:



              ip   : 10000000.00000000.00000000.00000000
              mask : 10000000.00000000.00000000.00000000

              result the subet like this:
              11111111.00000000.00000000.00000000
              11111110.00000000.00000000.00000000
              11111101.00000000.00000000.00000000


              So 127.0.0.0/1 covers 128.0.0.1 - 255.255.255.255





              share


























                0












                0








                0







                @Bojan Komazec is right



                the 0.0.0.0/1 binary format is like blew:



                ip   : 00000000.00000000.00000000.00000000
                mask : 10000000.00000000.00000000.00000000

                result the subet like this:
                01111111.00000000.00000000.00000000
                01111110.00000000.00000000.00000000
                01111101.00000000.00000000.00000000
                ....


                So 0.0.0.0/1 covers 0.0.0.0 - 127.255.255.255



                the 128.0.0.0/1 binary format is like blew:



                ip   : 10000000.00000000.00000000.00000000
                mask : 10000000.00000000.00000000.00000000

                result the subet like this:
                11111111.00000000.00000000.00000000
                11111110.00000000.00000000.00000000
                11111101.00000000.00000000.00000000


                So 127.0.0.0/1 covers 128.0.0.1 - 255.255.255.255





                share













                @Bojan Komazec is right



                the 0.0.0.0/1 binary format is like blew:



                ip   : 00000000.00000000.00000000.00000000
                mask : 10000000.00000000.00000000.00000000

                result the subet like this:
                01111111.00000000.00000000.00000000
                01111110.00000000.00000000.00000000
                01111101.00000000.00000000.00000000
                ....


                So 0.0.0.0/1 covers 0.0.0.0 - 127.255.255.255



                the 128.0.0.0/1 binary format is like blew:



                ip   : 10000000.00000000.00000000.00000000
                mask : 10000000.00000000.00000000.00000000

                result the subet like this:
                11111111.00000000.00000000.00000000
                11111110.00000000.00000000.00000000
                11111101.00000000.00000000.00000000


                So 127.0.0.0/1 covers 128.0.0.1 - 255.255.255.255






                share











                share


                share










                answered 2 mins ago









                jamleejamlee

                1011




                1011






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Super User!


                    • 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%2fsuperuser.com%2fquestions%2f851462%2funderstanding-routing-table-with-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

                    VNC viewer RFB protocol error: bad desktop size 0x0I Cannot Type the Key 'd' (lowercase) in VNC Viewer...

                    Tribunal Administrativo e Fiscal de Mirandela Referências Menu de...

                    looking for continuous Screen Capture for retroactivly reproducing errors, timeback machineRolling desktop...