Hide Forgot
Created attachment 491223 [details] log of hostapd messages, iwconfig after run, athernos info from boot log Description of problem: Hostapd fails to start with error "Could not set channel for kernel driver." The wireless device appears to be configured properly but for Master mode and the proper channel via iwconfig, but the network interface is not up or part of the routing after executing service hostapd start. If you do an ifup wlan0, then it switches back to ad-hoc mode instead of master mode. Version-Release number of selected component (if applicable): 0.6.10-2.fc14, kernel 2.6.35.11-83.fc14.x86_64 How reproducible: Always Steps to Reproduce: 1. service hostapd start 2. 3. Actual results: Drops wlan0 from network configuration. Expected results: Continued operation in master mode which was working fine in fc13. Additional info: Network manager is not running. This box remains configured via old style configuration as it is a fixed server.
It seems to be working for me, test f14 w/ ath5k. Perhaps you could attach your hostapd.conf? And the output of dmesg and/or the contents of /var/log/messages?
Created attachment 491342 [details] hostapd.conf Modified only to remove key and ssid. Unmodified from working F13.
Created attachment 491343 [details] Description before execution of hostapd This is how the network configuration looks before starting hostapd service with some IP addresses masked.
Created attachment 491344 [details] dmesg after service hostapd start If this isn't far enough back, I can create a longer list.
After the hostapd start, the wlan0 network is down. I could certainly have missed something in the upgrade, but there didn't seem to be anything I spotted in the release notes related to this. This was a working configuration before with a script I ran to start and stop the wlan network at particular times of the day. As far as I know only the underlying fedora binaries changed. If there is a new parameter I need to use, I missed it - sorry. If you need anything else, let me know and I'll try to get it to you as soon as feasible.
Seems to be resolved with the new kernel-2.6.35.12-88.fc14.x86_64 package.