Hi,
In light of the recent events (COVID-19 for those viewing after "the event"), we've purchased 300 seats and are currently sending all our remote workers internet traffic through the OpenVPN-AS server.
We need to do this for various reasons that I won't go into although it's to do with something something security something something regulation etc..
The problem we're having is that most of our available bandwidth is taken up with traffic such as spotify / netflix / youtube etc..
We don't pose any restrictions on the above sites.
I have a list of advertised routes available for each AS, it's pretty huge but I've aggregated it down to 50 odd networks that I would like to use the user's default gateway for.
Under Configuration > Advanced VPN, I added the following snippet to the "Client Config Directives" section:
route 23.246.0.0 255.255.192.0 net_gateway
route 37.77.184.0 255.255.248.0 net_gateway
route 45.57.0.0 255.255.128.0 net_gateway
route 64.120.128.0 255.255.128.0 net_gateway
route 66.197.128.0 255.255.128.0 net_gateway
route 69.53.224.0 255.255.224.0 net_gateway
route 108.175.32.0 255.255.240.0 net_gateway
route 185.2.220.0 255.255.252.0 net_gateway
route 185.9.188.0 255.255.252.0 net_gateway
route 192.173.64.0 255.255.192.0 net_gateway
route 198.38.96.0 255.255.224.0 net_gateway
route 198.45.48.0 255.255.240.0 net_gateway
route 208.75.76.0 255.255.252.0 net_gateway
(this example is all of Netflix's ipv4 networks)
However, this didn't appear to make it to any of the clients.
When testing, I couldn't see these config directives being pushed by the server to the connecting client.
Infact, a pretty odd side effect is that when those routes are present, the config attribute
vpn.server.tls_auth
is set to "false", which obviously breaks the world.
Aside from a possible bug, am I doing something incorrect? Have I misunderstood what this 'Client Config Directives' feature does?
Can anyone suggest a way for me to accomplish what I'm trying to do?
