Usually dirty flash are fine, but sometimes you can notice something is not right expecially if you go from stock to merlin.In the meantime, thanks for the answers. I think I have sorted out regarding disconnections. They were due to the Netatmo Presence camera. The camera works on Netatmo servers, then you have an app on your smartphone with which notifications arrive, you can see the events and see the live. The camera distinguishes people, animals, vehicles, etc., so it sends notifications, but I had noticed that it often did not perform live, indicating that the camera was off. I remembered that when I installed it 3 years ago, I had opened ports in the router. I redid this setup and now it's fine, I shouldn't have any more disconnection errors.
When you release the new firmware, just update this without losing the settings ??? I ask you because if I have to reconfigure everything from scratch, it takes a long time ...... you know I was used to the original firmware that I updated it with the smartphone app
nano /file/nameI open nano but then I should look for the file you indicated and modify it. How you do it?
I used WinSCP, so I was able to navigate inside the router folders. Inside the 'etc' folder, the 'NetworkManager' entry is missingIf you get disconnections from the llinux box you can easily test two things:
1. try tu lauch ping and leave it runnig per 1 day and see if you still get disconnections during the time ping is running.
2. Disable the power management on the wifi card you have. If you run iwconfig you will get Power Managemnt: on. You can disable via network manager configuration.
View attachment 30771
I understand, thank you. This morning the router still made some boring disconnections but then it was hard to hang up the devices. I decided to install your 384 stable version on the router, reset to factory values and reconfigured everything from scratch. Now it seems to be fine, I'll see what happens in the next few days@MatteoPV
I asked about to Asus developers about this logs
"Feb 12 16:58:01 syslog: wlceventd_proc_event(507): eth2: Disassoc AA:VV:CCD:EE:FF, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0"
And they replied with this:
"Hi Antonio,
No need to worry about the log.
We added the log to know the wifi clients join and leave the wifi network to analysis some customers' aimesh issue."
So as this has been said multiple times it's not an issue. Asus has built the driver with debug flag activated, that's it. Ignore the logs is safe. Topic closed.
Hey there,
Is there any of you having a RT router with Merlin firmware?
There is a bug in my builds and i am not sure if that comes from upstream yet.
The problem happens in the page http://router.asus.com/QoS_EZQoS.asp. Here the ATM checkbox doesn't stay checked after an apply.
That option is missing in the stock firmware.
If you have some time, please have a look and report back. Thanks a lot.
View attachment 30871
What's the router model you tried? what's the firmware version?Yes. When I choose atm and say apply, the atm sign disappears.
What's the router model you tried? what's the firmware version?
So in reality if some one was having an issue aimesh and seeing these spam their logs, Maybe they have an AiMesh logistics issue. This would be an issue only relevant to bring up with Asus through the feedback channel using stock firmware. I concur with GNUton, I have seen these logs before, but I have had Zero Issues with GNUton's firmware fork.@MatteoPV
I asked about to Asus developers about this logs
"Feb 12 16:58:01 syslog: wlceventd_proc_event(507): eth2: Disassoc AA:VV:CCD:EE:FF, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0"
And they replied with this:
"Hi Antonio,
No need to worry about the log.
We added the log to know the wifi clients join and leave the wifi network to analysis some customers' aimesh issue."
So as this has been said multiple times it's not an issue. Asus has built the driver with debug flag activated, that's it. Ignoring the logs is safe. Topic closed.
By installing the GNUton firmware from scratch, even doing a master reset, all those weird logs are gone. I put back the same addon as before. I have Skynet, FlexQOS, swap enabled, AMTM etc. Same adjustments of the DSL part, indeed a setting even more aggressive than the DSL. It has been going without disconnections for 2 days, it has already processed over 30 GB of traffic all in VPN etc. At this point I think it is essential when switching from the original firmware to the Merlin, then do a master reset and configure everything as if the modem were new. From here on, I believe that when updating the firmware, the master reset is no longer neededSo in reality if some one was having an issue aimesh and seeing these spam their logs, Maybe they have an AiMesh logistics issue. This would be an issue only relevant to bring up with Asus through the feedback channel using stock firmware. I concur with GNUton, I have seen these logs before, but I have had Zero Issues with GNUton's firmware fork.
Thanks for checking, but I wanted to know if this bug was present also in upstream firmware. If you have an RT-AC68U non in AiMesh can you please check if ATM works in QoS?DSL-AC68U: 386.01_0-gnuton0_beta1
Hey there,
Is there any of you having a RT router with Merlin firmware?
There is a bug in my builds and i am not sure if that comes from upstream yet.
The problem happens in the page http://router.asus.com/QoS_EZQoS.asp. Here the ATM checkbox doesn't stay checked after an apply.
That option is missing in the stock firmware.
If you have some time, please have a look and report back. Thanks a lot.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!