Hide Forgot
Description of problem: I am trying to use a Raspberry Pi 3 as an access point. I installed FC23 on the Pi and got the WiFi working. The plan was to make a bridge between wlan0 & eth0 on the Raspberry Pi. This is actually possible, but, it is *not* possible with Network manager alone. Version-Release number of selected component (if applicable): N/A How reproducible: 100% Steps to Reproduce: 1. Fire up Network Manager GUI/TUI 2. Create a new bridge. Place wired ethernet (eth0) and WiFi into bridge. 3. Specify the WiFi adapter should be in AP mode. Add security settings, etc. Actual results: The bridge starts with eth0 added to it. However, wireless adapter is not started and is not added. This is despite the configuration files all being correctly created in /etc/sysconfig/network-scripts Interestingly the only way I have managed to get this to work is to install hostapd. Configuring and starting hostapd does activate the wlan0 interface as expected. This can then be manually added to the bridge Network Manager created. Clearly hostapd is doing something (sorry, I don't know what and there are no clues in the log) that Network Manager's WiFi AP mode doesn't. Expected results: Creating a Network Manager configuration as described should be all that is required to setup a bridged WiFi/wired access point. It should not be necessary to use hostapd and manually add the connection to the bridge. Additional info:
Version information: Linux hppi 4.1.20-v7+ #867 SMP Wed Mar 23 20:12:32 GMT 2016 armv7l armv7l armv7l GNU/Linux NetworkManager --version 1.0.10-3.fc23
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.