Modify

Opened 5 years ago

Closed 5 years ago

#13159 closed defect (worksforme)

330-fix_reassoc_after_ack_failure.patch causes silent failures

Reported by: tusker@… Owned by: developers
Priority: normal Milestone: Chaos Calmer 15.05
Component: packages Version: Trunk
Keywords: Cc:

Description

Hi,

I have just tried to use latest trunk, which uses the 330-fix_reassoc_after_ack_failure.patch. With this patch enabled, wifi connectivity drops silently, without any error message in logread.

Running 'wifi' resumes connectivity for a few minutes.

Reverting out just that patch, resumes normal behaviour.

Cheers,

Damien

Attachments (0)

Change History (7)

comment:1 Changed 5 years ago by nbd

That's very odd. My tests show exactly the opposite. Without the patch, wifi can get stuck without reconnecting (AP considers the Client disassociated, Client thinks it's still connected), whereas with the patch the Client gets notified when it's no longer considered associated to the AP.

comment:2 Changed 5 years ago by nbd

Please show me the contents of the following files when it breaks:

/sys/kernel/debug/ieee80211/phy0/ath9k/xmit
/sys/kernel/debug/ieee80211/phy0/ath9k/reset

comment:3 Changed 5 years ago by nbd

Also, please increase the debug level of hostapd and show me its logs

comment:4 Changed 5 years ago by tusker@…

Hi nbd,

That actually makes sense to me. I only applied this new version on the client, rather than on the AP, so because the AP never sent the client that message, then the client would get stuck. Perhaps we need to leave the logic on the client the same, and only apply this logic for the AP side of things ?

I will test again with the patch on both the client and the AP.

Cheers,

Damien

comment:5 Changed 5 years ago by nbd

The code that this patch modifies is not even called on the client side, so I think it's probably an error in your test setup.

comment:6 Changed 5 years ago by tusker@…

Hi,

Tested again with both client and AP with that patch included, so far so good, with no silent failures.

I am running the client in sta+client bridge, so perhaps that is why the AP code is being used for my test setup.

Could this potentially cause interoperability issues with other routers running other firmwares ?

I would be happy to retest any combination you think would be valuable. How do I set the debug level in hostap without restarting it? (ie, the AP is in a hard to reach location, and only accessible via wifi)

Cheers,

Damien

comment:7 Changed 5 years ago by nbd

  • Resolution set to worksforme
  • Status changed from new to closed

I don't think this patch caused silent connection drop issues in any way. Simply bridging a client mode interface does not magically make it use AP related code. It also doesn't cause any interop issues with other equipment, this is purely standard compliant stuff.

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


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

 
Note: See TracTickets for help on using tickets.