Description of problem: Issue found in previous versions of Fedora, but not reported. If a router with a 5GHz port has a broadcast SSID, Fedora can connect to it. If the SSID of the 5GHz port is not broadcast, Fedora will attempt to connect, fail and then inactivate the 5GHZ connection. Non-5GHz router ports can be used whether or not the SSID is broadcast. Version-Release number of selected component (if applicable): Fedora 22 (and previous) How reproducible: Set the router (in this case, a Netgear Nighthawk R7000) to broadcast the SSID of the 5GHz port, connect successfully and use the wifi connection. Disconnect or use that connection or another to turn off SSID broadcast on the 5GHz port, attempt to reconnect to the 5 GHz port, and the attempt fails and the connection definition is disabled. The 'Hidden network" box in the "Networks" "Wi-Fi" window connection definition appears to not matter at all. It can be on for a broadcast SSID port, off for a hidden (non-5GHz) port and a connection will still occur. Steps to Reproduce: 1. Set the router (in this case, a Netgear Nighthawk R7000) to broadcast the SSID of the 5GHz port, connect successfully and use the wifi connection. 2. turn off SSID broadcast on the 5GHz port 3.attempt to reconnect to the 5 GHz port, and the attempt fails and the connection definition is disabled. Actual results: 5GHz router port cannot be connected to when the SSID is not broadcast. Expected results: all router ports can be connected to whether or not the SSID is broadcast. Additional info: VAIO laptop computer, dual boot with Microsoft Vista operating system. Vista can connect to the 5 GHz router port whether or not the port broadcasts an SSID
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.