Modify

Opened 4 years ago

Last modified 4 years ago

#14648 accepted defect

ath9k driver broken after r39138 - Wireless doesn't connect

Reported by: katananja@… Owned by: jow
Priority: response-needed Milestone: Chaos Calmer 15.05
Component: packages Version: Trunk
Keywords: Cc:

Description

TP-Link TL-WDR4300 v1 r39143

After the r39138 update wireless devices doesn't connect anymore, they do authenticate but doesn't receive IP adresses. Up to r39137 all was working fine, this affects a TL-WN821N at my Desktop, my cell Phone Xperia ZL and my laptop Acer that uses a Broadcom BCM43XX driver.

Attachments (3)

trunk-error.txt (2.2 KB) - added by katananja 4 years ago.
Systemlog error, mac address zeroed by me
wifi-log.txt (76.5 KB) - added by katananja 4 years ago.
log generated by CatLog on my Xperia ZL phone
wireless_config.txt (1.0 KB) - added by katananja 4 years ago.
/etc/config/wireless

Download all attachments as: .zip

Change History (12)

Changed 4 years ago by katananja

Systemlog error, mac address zeroed by me

Changed 4 years ago by katananja

log generated by CatLog on my Xperia ZL phone

Changed 4 years ago by katananja

/etc/config/wireless

comment:1 follow-up: Changed 4 years ago by Elphidium

Have you tryed to put fixed ip and restart dnsmasq ? im having the same issue and "solved" by that procedure.

comment:2 in reply to: ↑ 1 Changed 4 years ago by katananja

Replying to Elphidium:

Have you tryed to put fixed ip and restart dnsmasq ? im having the same issue and "solved" by that procedure.

To put a fixed IP where?
My router has a fixed IP, doing a hardware restart doesn't change a thing.

comment:3 Changed 4 years ago by katananja

Now on trunk r39150, it works only if you after a hardware reboot, restart dnsmasq.

comment:4 follow-up: Changed 4 years ago by duvi

Maybe it's a dnsmasq error, not wifi?
See #14629

comment:5 in reply to: ↑ 4 Changed 4 years ago by katananja

Replying to duvi:

Maybe it's a dnsmasq error, not wifi?
See #14629

Could be, but at the r39137 it was just fine. Maybe the ath9k patch or something else broke the dnsmask, I can't identify the error or why this happen because there is no line missing at /tmp/etc/dnsmasq.conf.

I've just downgrade back to r39137 and the issue goes away. If it's something related with the changes at r39101 as the #14629 pointed out, it makes no sense to me.

comment:6 follow-up: Changed 4 years ago by jow

  • Owner changed from developers to jow
  • Priority changed from normal to response-needed
  • Status changed from new to accepted

Please try r39152

comment:7 in reply to: ↑ 6 Changed 4 years ago by katananja

Replying to jow:

Please try r39152

I confirm it's fixed, thank you!

comment:8 Changed 4 years ago by brian.olmsted@…

I have to wait until the r39152, r39153 or r39155 snapshot is uploaded to downloads.openwrt.org snapshot repository. Don't have a compilation environment and don't want to brick my router in the meantime. Hopefully sometime tomorrow morning ;)

comment:9 Changed 4 years ago by brian.olmsted@…

seems fine for me. Only issue I have is with /etc/init.d/network restart issuing an error about "Command failed: Not Found"

Add Comment

Modify Ticket

Action
as accepted .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.