so, i have enp420 & tun0. when tun0 comes up, route are not properly update for tun0 routing. i think...

default via 10.0.0.1 dev enp4s0 proto dhcp metric 100
10.0.0.0/24 via 10.0.0.1 dev enp4s0 proto static metric 2
10.0.0.0/24 dev enp4s0 proto kernel scope link src 10.0.0.101 metric 100
10.8.0.0/24 dev tun0 proto kernel scope link src 10.8.0.1
10.8.1.0/24 via 10.8.0.2 dev tun0
10.8.2.0/24 via 10.8.0.2 dev tun0
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown

looks like maybe some NM policy is broke?

does NM create proper route for your vpn on NM restart?

On Sun, May 26, 2019 at 6:59 PM Ed Greshko <ed.greshko@greshko.com> wrote:

On 5/27/19 9:34 AM, Jack Craig wrote:
> anyone got openvpn doing proper route management with vpn start/stop?
>
> my take appears to suggest NM to be the problem, but short on proof.

I had no problems on F28. Now on F30 with no issues.

You'll need to describe what problem you having.

--
Right: I dislike the default color scheme Wrong: What idiot picked the default color scheme
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org