GNOME Bugzilla – Bug 741487
tap/L2 mode impossible to use
Last modified: 2020-11-12 14:30:23 UTC
When I select "Shared key" under "Authentication", two fields appear: "Remote IP address" and "Local IP address", which both translate to an "ifconfig" OpenVPN option. The problem is, with a 'tap' VPN (Advanced - Set virtual device type), these options make no sense at all. In 'tap' mode, OpenVPN expects a local address and a netmask as the parameters – exactly as if configuring an Ethernet device. (Also, surely the options shouldn't be under "Authentication"?) Other tabs (IPv4 Settings, IPv6 Settings) have a similar problem in all authentication modes. Since 'tap' mode makes the VPN work like an Ethernet device, one would expect to have an option to configure static addresses and routes, or perhaps use DHCP or autoconf. (I guess most of the time the OpenVPN server pushes those settings, but that's only possible in TLS mode – static-key requires the client itself to configure IP.) This is shared by both nm-connection-editor and gnome-control-center. NetworkManager 1.1-git network-manager-applet 0.9.10.0 gnome-control-center 3.14.2
bugzilla.gnome.org is being shut down in favor of a GitLab instance. We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time. If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/ Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).