Hide Forgot
Newly installed (and updated) Fedora 25 system. When pressing the "+" button in the "Network" settings from Gnome, I get an "Add VPN" dialog asking the type of VPN I want to add. At no point I have the option to add a VLAN. Using nmcli to create the VLAN makes it show in the "Network" settings from Gnome. FWIW I am using the "keyfile" plugin. But this was never a problem in F22, F23 or F24.
no UI supports every option of NetworkManager -- contrary to nmcli which is supposed to make everything accessible. Especially, gnome-control-center doesn't handle device types that aren't common on the desktop. You may use nm-connection-editor instead, which supports VLANs. Anyway, reassigning to gnome-control-center for consideration.
I don't expect it to support everything. But in the specific case of VLANs: * It *does* supports it. It can edit them just fine, it just can't add them * It has been working for years, this is a regression * The docs says it works -> https://docs.fedoraproject.org/en-US/Fedora/25/html/Networking_Guide/sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI.html#sec-Establishing_a_VLAN_Connection
FWIW a fully updated Fedora 25 still has the problem.
I have this issue too, it only show VPN option, the official doc says we can add VLAN interface in GUI. (https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/Networking_Guide/index.html#sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI)
I think if I press the "+", it should show this http://imgur.com/Dqv6XEh , but it only show VPN sub menu
Due to the rebase of Gnome, gnome-control-center no longer allows to add certain connection types like VLAN. The documentation needs to be fixed.
Other clients (nm-connection-editor, nmtui and nmcli) still support VLAN.
This is a disappointing loss of functionality that affects me the same as the others have reported. Would be great to have VLAN-capabilities back in gnome-control-center instead of being forced to use nmcli / nm-connection-editor for this small subset of connections that were manageable in prior releases.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Same problem here in Fedora 26 (Gnome). All tagged 802.1q VLAN connections configured in nm-connection-editor are completely functional when managed with nmcli. However, they do not appear in the GNOME network settings applet as long they are not active. When enabled manually with nmcli, they appear under the "Bluetooth" subsection of LAN settings (lol) and can be disabled by the network applet. I used to run Fedora on several admin console PCs with about 10+ tagged VLANs connected on each. Obviously it is time to look for a Linux distribution that is little bit more focused on the networking topic.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Unfortunately this is still an issue on Fedora 28.