Wake on WAN

[RMerlin]

Asus is currently planning to reverse the change in a future release.

 

[jmat]

Asus is currently planning to reverse the change in a future release.

Thank you, I think it's great news to start the day. Last night I did the 388.2.2 update on AX86U and the permanent arps are maintained with no problem with the method I am using via VPN. Good morning, until another time. All the best,

 

[MilkyOneWay]

Asus is currently planning to reverse the change in a future release.

Thank you very much for the time spent with this problem!

Best Regards

 

[jmat]

Thank you, I think it's great news to start the day. Last night I did the 388.2.2 update on AX86U and the permanent arps are maintained with no problem with the method I am using via VPN. Good morning, until another time. All the best,

PS: Finally, some time after the 388.2_2 update, the permanent macs disappeared again as per the trick found above, so I'm staying on 388.2 until the issue is resolved, hoping it won't take long. All the best,

 

[Kyjiep]

This morning I did a dirty update from 388.2_2 to 388.4 alpha. No problems are observed. And most importantly, the problem with the disappearance of static entries in the ARP has been fixed.

 

[jmat]

This morning I did a dirty update from 388.2_2 to 388.4 alpha. No problems are observed. And most importantly, the problem with the disappearance of static entries in the ARP has been fixed.

Thank you, Kyjiep, for your good news. Up until now, I have been using version 388.1 on both routers, with the solution we found some time ago, as it seemed to be the most stable one for maintaining permanent entries in the ARP (specifically, in my case, the broadcast address) after the usual restarts or various configuration changes on the router. The method I use doesn't require port forwarding on the WAN because I always do it through the OpenVPN of the router itself for security reasons, essentially treating it as a local connection. I will first test it with version 384.4 alpha on the RT-AX58U, and if everything goes well, I will also do it on the RT-AX86U and will come back to report my experience in this same thread. Regards,

 

[0kk0]

This morning I did a dirty update from 388.2_2 to 388.4 alpha. No problems are observed. And most importantly, the problem with the disappearance of static entries in the ARP has been fixed.

Niceee! Thanks for the update!
I was checking it out now and then last few days...
Im gonna update RT-AX86U PRO when merlin fw is available for it

But verrryyy nice to hear!

 

[jmat]

Thank you, Kyjiep, for your good news. Up until now, I have been using version 388.1 on both routers, with the solution we found some time ago, as it seemed to be the most stable one for maintaining permanent entries in the ARP (specifically, in my case, the broadcast address) after the usual restarts or various configuration changes on the router. The method I use doesn't require port forwarding on the WAN because I always do it through the OpenVPN of the router itself for security reasons, essentially treating it as a local connection. I will first test it with version 384.4 alpha on the RT-AX58U, and if everything goes well, I will also do it on the RT-AX86U and will come back to report my experience in this same thread. Regards,

After several days of monitoring the ARP table behavior of the RT-AX58U and RT-AX86U routers with the new firmware version 388.4 alpha 1, it can be said that at least on these routers, permanent ARPs are functioning normally again. Hopefully, the same will occur in the upcoming firmware updates, and we won't have any more scares for this reason. If anyone requires more specific information about this issue, I'll be happy to provide it. Thanks to RMerlin and everyone who contributed to solving this problem. Best regards to all, and until next time.