Hello, I am using LEDE few weeks and I am loosing internet on WIFI only.When internet shut down on WIFI, than I can not connect to web gui login or internet (WIFI still connect), but on LAN works all good. It is sporadic but it happen every 2-3 days. After reset router it works fine 2-3 days. My router is ASUS RT-N14 with latest ver. LEDE 17.01.4. But it happen on LEDE 17.01.3 too. I don't know where is problem or where I can focus. Please help. WAN is static and LAN and WIFI are DHCP. Thanks for help.
sistemx - I, too, am having trouble with ASUS router, but it's RT-N16. If you connect to SSH and execute TOP command before triggering large download (even Speedtest), do you see high CPU utilization?
The trouble with ASUS RT-N16 which has very high SIRQ (rightmost value of TOP command) while big transfers are happening, and would be interested to know if you are seeing same symptom with this different hardware.
Hello mrbene, I try TOP command, and when I download file from internet or try speed test or download file from network HDD, my SIRQ is under 15% and idle jumping from 90% to 99%. So looks like different problem on my side.
@sistemx Thanks for follow-up. Sorry I have no additional thoughts to help you.
The RT-N14u has MT7620 chipset which might explain your issue. For some reason devices with this chipset get a strange error message after a while of uptime saying something like "Dropping frame due to full tx queue", and the WiFi then cuts out until the device is rebooted.
I think it has something to do with overheating but I have no proof of this. For me I changed the tx_power to 15 from 20. Now my WiFi will stay up for weeks at a time before cutting out and needing a reboot. I plan to change to a different chipset in future as it doesn't seem like this is going to get fixed, though I hope I'm wrong on that.
Many thanks for explain, I will try your way. But interesting thing is that I used ASUS FW 1 year before and never happen this issue.
BTW, here is system log, what does it mean? it show me when internet down..
Sun Nov 5 19:43:25 2017 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED mac
Sun Nov 5 19:43:25 2017 daemon.info hostapd: wlan0: STA mac IEEE 802.11: disassociated
Sun Nov 5 19:43:26 2017 daemon.info hostapd: wlan0: STA mac IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
And where can I change tx_power?
And what is different between wlan0 and radio0?
Thanks.
and this is dmesg.
307319.756741] mtk_soc_eth 10100000.ethernet eth0: port 1 link up (100Mbps/Full duplex)
[307333.195069] mtk_soc_eth 10100000.ethernet eth0: port 1 link down
[307333.707924] mtk_soc_eth 10100000.ethernet eth0: port 1 link up (100Mbps/Full duplex)
[308195.298005] device wlan0 left promiscuous mode
[308195.307103] br-lan: port 2(wlan0) entered disabled state
[308195.567108] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[308195.802452] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[308196.951021] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[308196.967780] device wlan0 entered promiscuous mode
[308197.489529] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[308197.502563] br-lan: port 2(wlan0) entered forwarding state
[308197.513714] br-lan: port 2(wlan0) entered forwarding state
[308198.012633] device wlan0 left promiscuous mode
[308198.021957] br-lan: port 2(wlan0) entered disabled state
[308198.905942] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[308198.942187] device wlan0 entered promiscuous mode
[308199.811915] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[308199.824939] br-lan: port 2(wlan0) entered forwarding state
[308199.836088] br-lan: port 2(wlan0) entered forwarding state
[308200.420019] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2
[308200.420019] Please file bug report to
[308200.624633] br-lan: port 2(wlan0) entered forwarding state
[308203.569378] device wlan0 left promiscuous mode
[308203.578547] br-lan: port 2(wlan0) entered disabled state
[308204.960819] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[308204.977396] device wlan0 entered promiscuous mode
[308205.505208] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[308205.518245] br-lan: port 2(wlan0) entered forwarding state
[308205.529390] br-lan: port 2(wlan0) entered forwarding state
[308205.797624] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2
[308205.797624] Please file bug report to
[308206.319990] br-lan: port 2(wlan0) entered forwarding state
[308258.655337] device wlan0 left promiscuous mode
[308258.664497] br-lan: port 2(wlan0) entered disabled state
[308259.424494] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[308259.440993] device wlan0 entered promiscuous mode
[308259.961708] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[308259.974731] br-lan: port 2(wlan0) entered forwarding state
[308259.985882] br-lan: port 2(wlan0) entered forwarding state
[308261.046332] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2
[308261.046332] Please file bug report to
[308261.109111] br-lan: port 2(wlan0) entered forwarding state
[308693.180890] device wlan0 left promiscuous mode
[308693.190060] br-lan: port 2(wlan0) entered disabled state
[308693.958327] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[308693.974867] device wlan0 entered promiscuous mode
[308694.495612] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[308694.508647] br-lan: port 2(wlan0) entered forwarding state
[308694.519799] br-lan: port 2(wlan0) entered forwarding state
[308694.805013] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2
[308694.805013] Please file bug report to http://rt2x00.serialmonkey.com
[308695.660547] br-lan: port 2(wlan0) entered forwarding stateSee the Inactivity Timeout Options section in this OpenWRT article...
https://wiki.openwrt.org/doc/uci/wireless#inactivity_timeout_options
Even while your not explicitly getting the haunted error:
ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
But the logs are pretty close.
I still think @a7201 's point is valid. Except thinking that is a overheating issue.
Unfortunately this issue has been reported by multiple users for many years, and the rt2x00 team is not that active anymore I guess the chances on a fix are not that high.
@sistemx you can change you TX power at LuCI --> Network --> Wireless --> "your network" EDIT --> transmit power
Please note that all your SSID's should have the same TX power if this is not done by default.
And the difference between radio0 and wlan0 is that radio0 is the physical wireless hardware and wlan0 is virtual that gives radio0 a function.