[mt7613/mt7615] client connected but ping fail
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 888
- Forks
- 436
- PR merge metrics
- No merged PRs in 30d
Description
on chip mt7613
iwinfo wlan1 assoclist show the sta connected
but ping fail, no network
tcpdump -i wlan1 shows that sta client(My PC) sending arp request and AP reply the arp reply
that means My PC cannot get the arp replay packets
say, AP sending out but actually xmit fail?
and on this situation
it is eating memory
The memory is quickly exhausted
oom-kill
but if I do something
ifconfig wlan1 down
ifconfig wlan1 up
the lost memory back again.
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 by reproducing the mt7613/mt7615 failure with iwinfo wlan1 assoclist, tcpdump -i wlan1, and a ping from the connected station. Compare ARP transmission with memory usage, then repeat the ifconfig wlan1 down and ifconfig wlan1 up recovery. Done means the station can exchange traffic and memory no longer grows until OOM-kill.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100