-
Notifications
You must be signed in to change notification settings - Fork 8
client drops #5
Comments
Hi, I can't confirm this behavior on my BPI-R1: uptime05:22:51 up 30 days, 18:22, 1 user, load average: 0.25, 0.10, 0.09 dmesg | grep wlan0[ 30.354926] device wlan0 entered promiscuous mode As you see, there's just a couple interface flaps throughout the month, however my wireless clients are still able to connect. What exactly happens in your case when wifi breaks? Do your clients still see the access point? Are you able to initiate a connection and enter a password? I'd also try this once wifi is broken:
tcpdump -nn -i wlan0
|
Hi, sorry i needed the time to reproduce the failure. Now i can say that my problem starts if i use more band width on my devices. E.g. downloading a update. My devices (most android) see the accesspoint and try to reconnect to the bpi-r1. This messages are from my /var/log/syslog this block every time a device wants to connect again many of this messages [..] This type of messages i found after restarting the complete network on the console who is connected with a ttl to the bpi-r1. The tcpdump shows no messages. My next step was to rmmod and insmod 8192cu and start the hostapd with -dd There is many output, this is the block if a device trys to connect. Wireless event: cmd=0x8c04 len=20 Most times the device hangs on "Authentification" but somtimes i see "Getting IP Address". Thanks Frank |
Hi Frank, thanks for the great report. I sometimes see similar issues with clients unable to obtain an IP however this happens after hostapd finished it job and associated the client. No idea what the root cause is, I've got a feeling that realtek's driver is to blame. I hope we'll once have the in-tree driver working properly and then using an unpatched hostapd will be possible. Any ideas on fixing this are welcome. The sole wifi client on my BPI-R1 is a cellphone so I don't have enough data on my hands. |
Hi, thanks for your replay in lightspeed! :o) Have you an other idea? Thanks Frank |
Well there's several parts where things could go wrong:
Related to hardware - do you have enough power coming to the board? Do you have an HDD attached? For me strange things were happening with power until I bought a 5W power supply and applied this fix: http://bananapi.com/index.php/forum/general/391-why-the-sata-disk-doesnt-work-on-bpi-r1?start=12#1317 |
Hi. I am having similar problems. The BPI-R1 acts on my network as router, AP and DHCP server. In the network there is also a second AP and lot of nodes, some with static and some dynamic addresses, some wired and some wireless. Everything works just fine for 2-3 days. Then the AP of the BPI-R1 stops working, everything else keeps working fine, including the dhcp, Internet and the DHCP server. The stations can see the SSID, but when they try to connect the password is rejected. To fix the problem, I have to:
Since restarting hostapd does not fix the problem, I suspect that is not the issue. Also DHCP seems ok. When a station tries to connect, journalctl shows something like the below. Do you have any suggestion? Thanks a lot! Jun 11 21:56:30 bpir1 kernel: +OnAuth |
Hi, i found no solution. In my case the restart of hostapd didn't help. I have to reboot the whole system. Greetings Frank |
Hi, Unfortunately I have the same issue as others in this thread. My configuration is the following:
I can ensure that the issue is not related to the DHCP. To replicate the issue I'm using a speedtest application. On android when the AP doesn't work correctly, it think that the password is wrong. I will be happy to run some tests or provides some logs if somebody has an idea of how to find/understand this issue. |
@schaubl thanks for the steps - I was able to reproduce similar behavior using iperf. The first thing I noted was that the client stops receiving any replies from the AP when this is triggered. The AP seems to receive and send traffic however. Re-associating to the access point fixed the problem for me. I'm not sure how a userspace app like hostapd might be causing this, I think the kernel module is causing this. To completely reload it I'd suggest running this: /etc/init.d/hostapd stop && rmmod 8129cu && modprobe 8129cu && /etc/init.d/hostapd start |
In my case there is no need to remove/reload the driver. The following sequence works:
It would be nice if I had a way to detect programmatically that the AP has become not responsive. I thought about starting a job which listen to the journal and grep for some specific messages which appears when the AP is not working, but not during normal operations. Unfortunately I could not identify any such message. All the messages in the log above, seems to appear also during normal operations. |
Hi,
everything works fine, except that after a few hours all clients are dropped and can't reconnect till i reboot the bpi r1.
This problem is well known and there a many tips like
Is there a working solution?
The text was updated successfully, but these errors were encountered: