Something is causing your dnsmasq to crash (the watchdog will restart it). Remove that script to see if it's the cause.
One has root privileges to handle binding to a privileged port (port 53), the other runs without privileges to handle the rest. Typical process separation to improve security, as not everything within dnsmasq needs to run with root privileges.
Well, if CPU utilization is different under 388.2B vs every other 388.1 and 386, in that is results in packet errors or aothe anomalies like http timeout or unresponsive pages on the router, maybe...
I also wrote about this on page 13. Apparently, few people use static entries in ARP, and no one here pays attention to this, except for us. This is a pretty serious bug.
I don't know but in the latest beta I cannot ping any OpenVPN client, in all previous versions I was able to do that. There is something different which I cannot see in the changelog. All clients are connected and functional, I can reach them via ssh but cannot ping any vpn instance. I had to go back to 388.1 where everything works just fine.
Check your settings, there are various users reaching higher than 1 Gbps with Asuwrt-Merlin without problem. My first guess is you are enabling something that disables NAT acceleration, which would cap the speed to around 400 Mbps.
First of all thanks for your reply. We don't actually change any default settings, except the vlan id that is used to connect. I don't use Vpn, scripts of any kind and not even qos (which I've tried but it doesn't solve anything). I don't even use aiprotection or other features. It seems that the new beta firmware has something different for us Italian users. We were talking about it today on a well-known Italian forum where we all understood that the only solution seems to be this beta firmware. Can you please investigate? I don't like having a router without your firmware
Nothing more I can do about that, sorry. This is an ISP-specific issue (if it really is an issue), therefore impossible for me to investigate.
Thank you for your reply, lets hope that the problem doesn't occur on the final build.....
My proposition. Install firmware 386.5_2. and check stability and speed on 160MHz settings. I use fw 386.5_2. works great, fast and stable! Newer fw versions don't work properly with my Samsung S22Ultra.
I think i figured it out, in the process of updates to the firmware and reseting the router i think i forgot to disable the option Spanning-Tree Protocol, still not sure if its completly solved, but i made a quick test and it looks that with this disable the static entry stays configured.
Yeah, that's interesting. The YazDHCP event and the fatal signal crashes appear to have a temporal correlation, but without further data points, we can't yet say that there's causation. As @RMerlin suggested, you could try uninstalling YazDHCP temporarily to see if that has any effect on your situation. If the crashes continue to happen, at least you would have eliminated YazDHCP as the main culprit or a possible contributing factor.
Yes, that's exactly what I've seen every time in ASUS routers: one "dnsmasq" process running with user ID "anybody" (non-root), and the other one running with user ID "*Admin*" which has root privileges. That's why seeing 6 "dnsmasq" processes running simultaneously, as @JGrana mentioned in his post, is surely a sign of some kind of trouble brewing under the surface.
Understood - but no matter what Merlinware version is released - its foundation is Asuswrt - so changes in the perceived behaviour of ones router under a beta or any released version of Merlinware will result in comments from the user base ... whether those changes are brought about directly by what @RMerlin does - or the underlying code it is based on. The distinction between the two matters little to an average "Joe" like me ... and clearly a LOT to the technical boffs like @RMerlin and yourself.
100%
