TinCanTech wroteFrom the 22 manual:
https://community.openvpn.net/openvpn/wiki/Openvpn22ManPage
--max-routes n
- Allow a maximum number of n --route options to be specified, either in the local
configuration file, or pulled from an OpenVPN server. By default, n=100.
--max-routes-per-client n
- Allow a maximum of n internal routes per client (default=256). This is designed
to help contain DoS attacks where an authenticated client floods the server with
packets appearing to come from many unique MAC addresses, forcing the server to
deplete virtual memory as its internal routing table expands. This directive can
be used in a --client-config-dir file or auto-generated by a --client-connect
script to override the global value for a particular client.
Note that this directive affects OpenVPN's internal routing table, not the kernel
routing table.
You ought to use up-to date version 2.3.11
Driver wroteI have tried adding the max-routes option to the server config and the issue persists
Did you stop/start the server ?
We are on CentOS6 and the version available is 2.2.2, packages outside of yum are a pretty hard sell in our enviroment. Either way, max-routes is suppose to be supported in 2.2.
Yep restarting the service and it simply fails to start when there are more than 100 routes in the server config file. I can comment one of them out to get us back to 100 and the service starts with no issues.
