Changes between Version 1 and Version 2 of OverridingAPushedRouteInTheClientsConfigThrowsAndError


Ignore:
Timestamp:
12/15/16 11:23:48 (2 years ago)
Author:
cavok
Comment:

Putting route-nopull after the local route overrides solves the initial question

Legend:

Unmodified
Added
Removed
Modified
  • OverridingAPushedRouteInTheClientsConfigThrowsAndError

    v1 v2  
    2929This issue materializes because "route-nopull" option takes away the permission from the client to install server-pushed routes, effectively telling the option parser "no, this option is not valid here".
    3030
     31The way to configure it correctly is then:
     32
     33{{{
     34...
     35# Options
     36client
     37route 10.1.0.0 255.255.255.128
     38route-metric 50
     39route-nopull
     40...
     41}}}
     42
    3143[wiki:FAQ Return to FAQ]