OpenWrt/LEDE Project

  • Status Closed
  • Percent Complete
    0%
  • Task Type Bug Report
  • Category Base system
  • Assigned To No-one
  • Operating System All
  • Severity High
  • Priority Very Low
  • Reported Version lede-17.01
  • Due in Version Undecided
  • Due Date Undecided
  • Private
Attached to Project: OpenWrt/LEDE Project
Opened by Stephan Richter - 19.07.2018
Last edited by Adrian Schmutzler - 19.06.2020

FS#1678 - TP-Link TL-WR1043ND

Device:
- TP-Link TL-WR1043ND v3, also reported for v1

Software:
- LEDE Reboot 17.01.4 r3560-79f57e422d / LuCI lede-17.01 branch (git-17.290.79498-d3f0685)

Steps to reproduce:
- Flash Router with LEDE
- Setup Wifi

  1. Interface Settings:
    1. Mode: Access Point
    2. Network: lan
    3. Hide ESSID: no
    4. WMM Mode: yes
    5. Encryption: WPA2-PSK (Cipher: auto, set Key)
    6. no MAC Filter
    7. no advanced Settings
  2. Advanced Settings:
    1. Country Code: DE


Expected Behaviour:
- Clients may connect to Wifi and access Local Network and Internet (if set up)

Actual Behavior:
- works in the first place
- Wifi becomes unusable within 24 hours (sometimes only minutes after setup, sometimes after hours)

  1. no disconnection
  2. ping times go up
  3. package losses

- reboot of device fixes problem for short time

More Information:
- does not occur, when Wireless is assigned to the WAN interface (using double NAT behind second router)
- thread: https://forum.lede-project.org/t/tp-link-tl-wr1043n-nd-v1-unreliable-wifi-useless-after-24-hours-ani-disabled/15008

Possibly related Bug reports:

Closed by  Adrian Schmutzler
19.06.2020 11:21
Reason for closing:  Won't fix
Additional comments about closing:  

LEDE-17.01 has reached EOL (end of life). This bug has been closed automatically. If the problem persists with a newer version, please file an appropriate new bug report for that version.

Admin
Jo-Philipp Wich commented on 19.07.2018 08:08

Thanks for the report but why didn't you comment on one of the related bugs? Instead of four "random ath9k wifi issues" bugs we know have five...

psyborg commented on 19.07.2018 11:06

801 device use ath10k driver
1373 device use rt2x00 driver
1582 device use marvell driver

so, completely unrelated

1180 already contains possible solution, have you tried it?

Stephan Richter commented on 19.07.2018 17:39

@Jo-Philipp Wich: because I was not sure, whether it is the same bug. Obviously, some think it is not. Usually Bugtrackers allow to merge issues?

@psyborg: Yes, I have seen that these are different drivers. But the problem
described is very similar. Maybe it is not a problem with the driver (which would explain the different behaviours depending on configuration)? I'm not an expert, just a tought.
I also read the proposed workaround (it is not a real solution, is it?), but as I wrote, I'm not an expert. I have no clue how to "remove 305-ath9k-limit-retries-for-powersave-response-frames.patch" or what "by forcing ps=false" means.

Maybe someone can help me out here? If so, I'm willing to test if this works for me and report here.

Stephan Richter commented on 19.07.2018 18:19

I just noticed I forgot to mention the problem in the task title - is there a way to alter it?

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing