On Thu, Feb 9, 2017 at 3:51 AM, Thomas Haller <[email protected]> wrote: > On Wed, 2017-02-08 at 11:52 -0600, Greg Oliver wrote: >> On Wed, Feb 8, 2017 at 11:36 AM, Thomas Haller <[email protected]> >> wrote: >> > On Sat, 2017-01-28 at 10:59 -0600, Greg Oliver wrote: >> > > I posted a while back about not being able to set the gateway for >> > > static routes in VPN connections to the tun/tap/ppp interface, >> > > and a >> > > great hint to just set it to 0.0.0.0 was given. That has worked >> > > in >> > > the latest NetworkManager in F25. >> > > >> > > It accepts the gateway and will work as expected, but every time >> > > I >> > > edit the connection afterward, I have to re-fill in my gateways >> > > on >> > > every individual route again - per connection. If I never need >> > > to >> > > edit a VPN, no issue, but unfortunately I need to often edit >> > > them. >> > > This behavior just started (recently anyway - not sure the exact >> > > commit). >> > > >> > > Happens on all types (vpnc, openconnect, pptp). >> > > >> > > Thanks >> > > >> > > -Greg >> > > >> > >> > Hi Greg, >> > >> > Note that in nm-connection-editor a gateway of "0.0.0.0" is >> > identical >> > to leaving the field empty. Thus, if you edit a connection to have >> > gateway 0.0.0.0, next time when revisiting the connection the >> > gateway >> > is cleared. >> > >> > Thomas >> >> That is true, but when I edit it again, it requires me to re-enter >> 0.0.0.0 before I can save it. Would it be possible to add this as a >> feature request to not have to add a gateway address (for manually >> enetered routes) at all in the GUI? > > doesn't happen to me. Either I am testing something different then you, > or you are using an older version of the GUI, where a bug got fixed > recently. > > Can you describe exactly where you are clicking? And which nm- > connection-editor version are you using? Or is it gnome-control-center? > > Thomas
This behaviour just started happening. When you first told me of the 0.0.0.0 gateway option on VPN connections, it did not do this. NetworkManager-wwan-1.4.4-3.fc25.x86_64 NetworkManager-1.4.4-3.fc25.x86_64 NetworkManager-openconnect-1.2.4-3.fc25.x86_64 NetworkManager-openvpn-1.2.6-1.fc25.x86_64 NetworkManager-pptp-gnome-1.2.4-1.fc25.x86_64 NetworkManager-team-1.4.4-3.fc25.x86_64 NetworkManager-glib-1.4.4-3.fc25.x86_64 NetworkManager-vpnc-1.2.4-1.fc25.x86_64 NetworkManager-libnm-1.4.4-3.fc25.x86_64 NetworkManager-adsl-1.4.4-3.fc25.x86_64 NetworkManager-vpnc-gnome-1.2.4-1.fc25.x86_64 NetworkManager-wifi-1.4.4-3.fc25.x86_64 NetworkManager-config-connectivity-fedora-1.4.4-3.fc25.x86_64 NetworkManager-openconnect-gnome-1.2.4-3.fc25.x86_64 NetworkManager-bluetooth-1.4.4-3.fc25.x86_64 NetworkManager-pptp-1.2.4-1.fc25.x86_64 NetworkManager-openvpn-gnome-1.2.6-1.fc25.x86_64 Like the pic shows, it now makes me fill in the gateway address 0.0.0.0 again every time I edit the connection. This happens on VPN connections as well as ethernet profiles in this version. You are correct though - if I use nm-connection-editor, the issue is not there. Looks like an issue with gnome-control-center - do I need to punt this their direction? Thanks, Greg
_______________________________________________ networkmanager-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/networkmanager-list
