Recent content by Frank Monroe

Understood. I made that decision a long time ago. It's been well over a year now. The only reason why this came up again is because I updated to the 386.10 release to test wifi calling for the person in this thread and while I was at it, I tested for wifi connectivity issue again as I do with...

Correct. I never lose concat with anything connected directly to the switch. BTW, I have updated the prior post to include the three reports into post.

Other times this has been reported. https://www.snbforums.com/threads/arp-problem-between-wifi-devices-on-rt-ac88u.81665/ https://www.snbforums.com/threads/rt-ac3100-intermittently-cant-ping-devices-on-the-network.74029/...

The ARP entry for the router is still there.

It's 100% the router issue. I others can reproduce the issue at will. All you have to do is install any version of Merlin past release 386.3_2. I have tested each and every release since then and they all have the issue. Also, yes, the packets don't hit the router. And I'm not talking about...

IPv4 internet traffic continues to work that is. Of course, IPv6 stops working as clients lose their IPv6 configuration.

The problem isn't that all traffic doesn't flow. Traffic to the Internet is fine. However, traffic from device to device stops working. For example, one device cannot ping another. In addition, IPv5 RA's from the router stop reaching client. This is not a client issue.

Great. The point is communication between devices on the same router stop after the router is up for a few days. In addition, certain announcements from the router also cease. This causes issues for both IPv4 and IPv6. For IPv6, clients completely lose their configuration. This is not new...

Yes. I have startup scripts with custom routes and iptable rules that route specific traffic through a VPN (thats not on the Asus router). I also use VPN director and DNSFilter.

Understood about having to remain on 386.3_2. I've been on that version for a year and half due to this. I can stick with it until I replace the router at some point. I generally do test every version to see if it goes away. As far as model specific, mine is an AC5300. I can't remember the...

I was going to do that. Since it takes 3-5 days for the problem to show up I would have to run a week without Merlin to be sure. I'm using features of Merlin that I can't be without for a week.

Actually, there have been quite a few other people reporting this issue. All of them reverted back to 386.3_2 and the problem went away. The issue is not an IPv6 issue. The issue causes ARP and ICMP to fail. Since IPv6 relies on ICMP for RA's, it breaks IPv6. The other people reporting the...

No. This issue isn't specific to IPv6. The issue causes problems for IPv4 as well. The issue will also cause you to lose your IPv6 configuration.

After running 386.10 for five days, It looks like 386.10 still has the ICMP and intra client connectivity issues.

It looks like 386.10 still has the ARP, ICMP, IPv6, and basic intra-router client connectivity issues on the AC5300 that started with version 386.4. My AC5300 has been up for just under five days running 386.10 and it just started having these issues again. I will power cycle and try again...