On Tue, 09 Sep 2014 20:50:59 +0400 ValdikSS <i...@valdikss.org.ru> wrote: > I can confirm this bug. This probably happened after networkmanager > update. It seems like networkmanager intercepts route too late. > > Here are two workarounds: > 1) add "route-delay 1" to your openvpn configuration file. > 2) use route-nopull and redirect-gateway (without def1). >
Thanks! I used #2 and it did the trick. My route now seems more route-appropriate (if such a term exists) claudio@Chuck:~$ ip ro default via 10.4.0.5 dev tun0 10.4.0.5 dev tun0 proto kernel scope link src 10.4.0.6 169.254.0.0/16 dev wlan0 scope link metric 1000 XXX.XXX.XXX.XXX via 192.168.1.1 dev wlan0 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.16 I'll wait to see where this goes :) Thanks again, Claudio
