They were more or less copied from a config built by a previous sysadmin and have been only slightly modified over time, i.e., I did not build them from scratch and if anyone sees general issues with them, please feel free to point them out. Have done a lot of googling and man page reading - but maybe I'm just missing something very obvious. That being said, I am still *very* confused about how and why these client config files are being created. This was easily resolved by moving routing directives to the server config file. This were apparently overriding the routes in DEFAULT. After some poking around, I discovered files in the ccd named after the client id, with the following contents: ifconfig-push 10. 255.255.255.0 But subsequent connections did not get any routing info. The first time a client connected, everything worked fine. No significant loss in overall speed is noticed. Once version 5.2.0 connects, latency increases but that is to be expected from a VPN. Versions 5.5 and 5.6 can't establish connections with the available servers. We had our routes configured in ccd/DEFAULT. As of version 5.2.0 works on my Mac (macOS Sierra 10.12.4). I discovered this when troubleshooting an issue with routes not getting pushed to clients. Can anyone shed some light on how/when/why openvpn automatically creates individual client config files in the client-config-dir?
0 Comments
Leave a Reply. |