mt7615E AP/VLAN
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 888
- Forks
- 436
- PR merge metrics
- No merged PRs in 30d
Description
this issue is only occur when using vlan_id in wpa_psk file or ppsk with freeradius (AP_VLAN),
no issue with standard AP
the only easy/simple way i can reproduce this is by viewing remote vnc (same local network)
so i think its UDP related, here's what i'm experiencing
- connection got dropped, wifi still connected
- no communication to/from after it got dropped
tested with snapshot - 21.02 branch
tested devices: ea7500 v2, ea8100 v1, re650 v1
after a week of fiddling around,
reverting this commit fix the issue i have, 0ed6a335ebc28936c68ccba82368d4ab1c8e5fcf
or just remove ieee80211_send_bar() inside case IEEE80211_AMPDU_TX_OPERATIONAL
i understand mt7615 is an old device so it may not be the focus anymore,
but please could you take a look at this particular commit @nbd168
thank you
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with commit 0ed6a335ebc28936c68ccba82368d4ab1c8e5fcf and the ieee80211_send_bar() call inside IEEE80211_AMPDU_TX_OPERATIONAL. Reproduce with mt7615 AP_VLAN using vlan_id in the wpa_psk file or PPSK with FreeRADIUS, preferably through remote VNC on the same network. Done means resolving the post-drop loss of communication without regressing standard AP behavior on the reported devices.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100