Adam Williamson writes: > If you can pinpoint a fairly straightforward 'install, do X, and weird > thing Y happens' flow, I'd file a bug - probably against NetworkManager > indeed - with the instructions to reproduce. Thanks! I did a reinstall. And yes, NetworkManager attempts to manage the tun0 device created by OpenVPN. Here are my steps: - boot boot.iso - do absolute minimal install - login as root - yum install dnf - dnf install openvpn - nmcli the primary ethernet into a static configuration Here I encounter a weirdness, NetworkManager does not setup a default route. I manually add a default route, at which point another default route is immediately created with extra parameters "proto static metric 1024". So I delete the route I created, leaving the new one. Setup my openvpn, which creates a tun0 device and adds 0/1 and 128/1 routes by itself. However, a ip route reveals that the 0/1 route is missing. nmcli d status reports that tun0 is managed. Manually adding the 0/1 route does not stick. I close openvpn, and the tunnel. nmcli c show shows a new connection uuid for that tun0 connection. I nmcli c delete that connection. I nmcli n off, and then modify NetworkManager.conf adding no-auto-default=* and ignore-carrier=* and repeat. Same issue happens. I modify NetworkManager to add keyfile to the plugins, and a [keyfile] entry specifying tun0 as an unmanaged interface. This now gets me to the point where NetworkManager leaves tun0 alone (something I didn't have to do in F20) and my OpenVPN tunnel works. There in an issue that the reinstall process revealed. Note now, I am no longer removing ifcfg-enpXs0 and doing everything via nmcli, as opposed to before where I only used NetworkManager with the keyfile plugin and had my setup totally in system-connections. As I mentioned above, I no longer have a default route being set up. I don't know why. A full install to the gnome desktop reveals that when I login, absolutely no network icon appears in the top right, but when I add my default route (as mentioned above) a new default route is created with the exact same route and "proto static metric 1024" and immediately I see the network icon appear in the top right of my desktop. I have yet to migrate my the nmcli modified ifcfg-enpXs0 setup to my old keyfile-only setup, to see if that still causes issues with the default route, but at this point things are working, it's just that as I said, the takeaway is: NetworkManager in F21 tries to manage tunX devices, unless explicitly told not to, unlike F20. -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
