On 23/5/2016 11:15 μμ, Selva Nair wrote: > While this should work, leaving all common options in the config file > and the ones that need client-specific override in ccd/DEFAULT may be > easier to maintain than using push-reset and redefining all push > options. Then all clients without a specific ccd file will get the > common options plus those in DEFAULT while the ones with a ccd file > would get the common options plus those in the ccd file.
You are undoubtedly right! Yet, as I am experimenting with these configuration options, I decided to try (in an experimental, "beta" stage) this approach, i.e. to push-reset and then reconfigure this couple of new clients, leaving the rest of the config as is. For a more permanent solution, I am planning to use the push-remove option! > push-remove in git master is even better. Yes, of course! I look forward to finding the soonest available time to build it! > In your server config add push "route-gateway 10.12.12.1". This is > automatically done (for topology subnet) if --server option is used to > setup the server ip, ip-pool etc, not otherwise. Also see --server and > --route options in the man page for more details. Thank you, I will try that. But: in my server config I do have: "server 10.12.12.0 255.255.255.0" (as I have earlier listed). Wouldn't this be the same as defining the --server option to setup the server ip? Thanks again! Nick ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
