I am so sorry! I posted this topic from another computer than running openvpn - so copied one of the wrong settings-files on the road to the one that are running and works for Windows and Schwabes app 🙁 I have updated my first post now.
All my sub-nets are on the 10.99.x.x range
So i push route 10.99.0.0 255.255.0.0 to reach all subnets on my network from my vpn client.
I choose 10.10.10.0 on my tun adapter to be on another subnet completely different. (originally I choose 10.99.10.0 for my tun adapter, but that way I had to use three push route subnets, while I was suspecting that was my problem.) Selecting 10.10.10.0 as tun-subnetwork I can reach all my subnets in one "push route"
In short: the logs from OpenVPN Connect was correct and my copy from the OpenWrt was wrong:
This is a copy-paste from my OpenWrt as it is running now:
config openvpn 'bv_tun'
option dev 'tun'
option port '1195'
option proto 'udp'
option server '10.10.10.0 255.255.255.0'
option ca '/etc/openvpn/ca.crt'
option cert '/etc/openvpn/fw.crt'
option key '/etc/openvpn/fw.key'
option dh '/etc/openvpn/dh2048.pem'
option comp_lzo 'yes'
option mssfix '1420'
option keepalive '10 60'
option verb '3'
option enabled '1'
option log '/tmp/openvpntun.log'
option push 'route 10.99.0.0 255.255.0.0'
Have updated my initial post also.
Best regards,
Arild
openvpn_inc wrote
Hello,
The server config states:
option server '10.10.10.0 255.255.255.0'
option push 'route 10.100.0.0 255.255.0.0'
On the client side log I see:
0 [route] [10.99.0.0] [255.255.0.0]
1 [route] [10.10.10.1]
Why are the subnets 10.100.0.0/16 and 10.99.0.0/16 different? Maybe this is your problem?
Have you done ping tests with packet capturing on the server to verify that pings from the client are arriving at the server?
Kind regards,
Johan
