Bug 828824
| Summary: | USB Wi-Fi dongle not working as access point | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tom Horsley <horsley1953> | ||||||||||||||||
| Component: | kernel | Assignee: | Stanislaw Gruszka <sgruszka> | ||||||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||
| Version: | 17 | CC: | felixbellaby, gansalmon, itamar, jonathan, jwboyer, kernel-maint, madhu.chinakonda | ||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||
| Hardware: | Unspecified | ||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||
| Whiteboard: | |||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||
| Last Closed: | 2012-07-07 21:54:36 UTC | Type: | Bug | ||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||
| Embargoed: | |||||||||||||||||||
| Attachments: |
|
||||||||||||||||||
|
Description
Tom Horsley
2012-06-05 12:38:20 UTC
Can you provide steps to reproduce (including relevant parts of hostap config) so I could investigate that locally ? I just tried a few different kernels: kernel-3.3.4-5.fc17.x86_64 - also does not work On fedora 16 partition: kernel-3.3.7-1.fc16.x86_64 - yet another failure kernel-3.3.6-3.fc16.x86_64 - this one seemed to work And it was working so well not too long ago :-). Created attachment 589542 [details]
/usr/local/bin/start-ap
This is the shell script that starts everything. Note that I normally don't
start iptables at all, so the starting of iptabes in here is just to get the
NAT routing going.
Created attachment 589545 [details]
/etc/hostapd.conf
This is the hostapd.conf file with the passphrase changed.
Created attachment 589546 [details]
/etc/sysconfig/iptables
These are the NAT routing rules I get when I start iptables.
Created attachment 589547 [details]
/etc/dhcp/dhcpd.conf
Here is the DHCP server config.
Created attachment 589549 [details]
/etc/sysconfig/dhcpd
And finally, here is the /etc/sysconfig/dhcpd file with the argument
to DHCPD so it will only serve info over wlan0.
Hey! It isn't 100% failure. On about the 10th try, it actually connected and is working. My phone can now get out to websites around the internet. So apparently instead of failing 10% of the time, it went to failing 90% of the time. I guess I just need to retry often enough and it will eventually work. Created attachment 594182 [details] 0001-rt2x00usb-do-not-check-STATUS_PENDING-bit-on-rx.patch Proposed patch for this problem - patch makes things work on my setup. Test kernel with patch is here: http://koji.fedoraproject.org/koji/taskinfo?taskID=4193085 please test it. 3.4.4-1.bz828824.fc17.x86_64 is looking good so far. I got a clean connection the first time I tried after the initial boot, then disconnected everything and tried connecting again, and the 2nd one worked perfectly as well. It has been so random, I can't be absolute positive it is fixed, but it sure looks better with the small sample size I have at the moment :-). Thanks! And the next day, it continues to work perfectly first time, every time. I'm beginning to believe this is indeed fixed for sure. The last time it connected this many times in a row with no problems is a distant memory (maybe around f12 or f13?). Created attachment 595753 [details] 0001-rt2x00usb-fix-indexes-ordering-on-RX-queue-kick.patch Tom, previous patch is a bit buggy, it could possibly cause kernel crash. Please test this one http://koji.fedoraproject.org/koji/taskinfo?taskID=4212293 Just booted 3.4.4-3.bz828824_v2.fc17.x86_64 and the dongled connected perfectly the first time I tried. Seems to work so far. This morning I tried to connect again, and it took two attempts to work. Don't know if that means anything or not - two is still much better than it was. Josh, please apply patch from comment 12 as fix for this bug, I just posted it upstream today http://marc.info/?l=linux-wireless&m=134140046608506&w=2 Thanks Stanislaw! In Fedora git for F16/F17/rawhide. kernel-3.4.4-5.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/kernel-3.4.4-5.fc17 kernel-3.4.4-4.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/kernel-3.4.4-4.fc16 Package kernel-3.4.4-4.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.4.4-4.fc16' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-10319/kernel-3.4.4-4.fc16 then log in and leave karma (feedback). kernel-3.4.4-5.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. kernel-3.4.4-4.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. I have been seeing packet loss using a rt2800usb device in managed mode since the first 3.4.4 kernels were distributed. This packet loss becomes total after a few minutes of pinging the network. The total package loss occurs without any change in the iwconfig output and without any postings to the syslogs. I used the 3.3.7-1.rc17 kernel as a stop gap for a month before reverting to an ath5k device. There are no problems in either of these cases. Loading the rt2x00lib module into the 3.4.4-5.fc17 kernel using modprobe seems to make no difference providing the rt2800usb device is unplugged. However, the package loss returns when the rt2800lib module is loaded using modprobe (this also loads the crc_ccitt module). This recurrance of the packet loss occurs even when the rt2800usb device is unplugged and the ath5k device and interface are the only ones in use. Since Stanislaw has made patches to these kernel modules and the symptoms resemble the ones reported under this bug, it seems sensible to raise the issue here. Felix, please open separate bug report for this problem and provide needed information (steps to reproduce, hw info, etc ...). |