On 09/13/2017 04:46 PM, James Cameron wrote:
I'll give it some more testing and let you know, but it seems as
capable of keeping a connection as 4.13 plus my earlier revert.
The change I sent earlier should be as good as reverting the change to
write_byte in your reversion.
There has been a report (in Russian unfortunately) at
https://www.linux.org.ru/forum/desktop/12620193 of delays in ARP handling.
According to Google translate is as follows:
============================================================
Periodically, Wi-Fi networker rtl8821ae ceases to respond to ARP, which causes
the Internet to end. Wireshark looks quite interesting: ARP replays can be sent
by one large packet a few seconds after receiving the requests, ie. they seem to
be buffered somewhere.
arping, launched under strace, also hints at certain problems:
sendto(3,
"\0\1\10\0\6\4\0\1\334\205\336\3572\343\300\250\0h\377\377\377\377\377\377\300\250\0\1",
28, 0, {sa_family=AF_PACKET, proto=0x806, if3, pkttype=PACKET_HOST, addr(6)={1,
ffffffffffff}, 20) = -1 ENOBUFS (No buffer space available)
alarm(1) = 0
rt_sigreturn() = 45
recvfrom(3, 0x7fffc1646030, 4096, 0, 0x7fffc1645fb0, 0x7fffc1645eac) = ?
ERESTARTSYS (To be restarted if SA_RESTART is set)
--- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} ---
sendto(3,
"\0\1\10\0\6\4\0\1\334\205\336\3572\343\300\250\0h\377\377\377\377\377\377\300\250\0\1",
28, 0, {sa_family=AF_PACKET, proto=0x806, if3, pkttype=PACKET_HOST, addr(6)={1,
ffffffffffff}, 20) = -1 ENOBUFS (No buffer space available)
alarm(1) = 0
rt_sigreturn() = 45
recvfrom(3, 0x7fffc1646030, 4096, 0, 0x7fffc1645fb0, 0x7fffc1645eac) = ?
ERESTARTSYS (To be restarted if SA_RESTART is set)
--- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} ---
recvfrom(3, 0x7fffc1646030, 4096, 0, 0x7fffc1645fb0, 0x7fffc1645eac) = ?
ERESTARTSYS (To be restarted if SA_RESTART is set)
--- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} ---
sendto(3,
"\0\1\10\0\6\4\0\1\334\205\336\3572\343\300\250\0h\377\377\377\377\377\377\300\250\0\1",
28, 0, {sa_family=AF_PACKET, proto=0x806, if3, pkttype=PACKET_HOST, addr(6)={1,
ffffffffffff}, 20) = -1 ENOBUFS (No buffer space available)
============================================================
I need to explore that ENOBUFS return code.
Your case where the device is unresponsive to pings from another NIC until the
device transmits may also be an ARP problem.
For completeness, are you using the 2.4 of 5 GHz band? What is the make/model
your AP? If possible for you to determine, what firmware is it running?
Thanks,
Larry
