Search results

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

  1. E

    Traffic spike fix from 384.14_2 was reverted in 386.1

    Nothing new here? Should we just give up on the built-in traffic statistics? I'm still hoping to test a fixed/test rstats on an RT-AC68U.
  2. E

    New repeating error message

    I don't have aiprotect enabled, I still see the message, and the message is more than a debug message in my case. The mac address is the mac for a wifi AP (non asus) that's got some devices connected to it's ethernet ports. The device itself appears to get kicked off the network sometimes as do...
  3. E

    Traffic spike fix from 384.14_2 was reverted in 386.1

    I'm on an RT-AC68U
  4. E

    Traffic spike fix from 384.14_2 was reverted in 386.1

    I knew it would happen when I upgraded to 386.1, and indeed, within less than 3 hours, I see a spike just like Morac's. Happy to test a patched rstats.
  5. E

    [Release] Asuswrt-Merlin 384.18 and 384.13_10 is now available

    Shouldn't have said anything - as this is happening to my router starting about an hour ago. Looks like these are the processes getting wedged: 209 admin 5100 D nt_center 6685 admin 3472 D TrafficAnalyzer -e 7210 admin 1424 D cp /tmp/syslog.log /tmp/syslog.log-1 /jffs...
  6. E

    [Release] Asuswrt-Merlin 384.18 and 384.13_10 is now available

    I've had occasional "stability" issues like this as well - where ssh works, but the webui won't respond. When logged in via ssh I find a lot of watchdog errors in the syslog and attempts to cp syslog files to jffs hanging (probably why the web server is hanging)... when I reboot from the ssh...
  7. E

    NVRAM [Release] NVRAM Save/Restore Utility

    Maybe this is because I saved and restored on the latest (384.18) Merlin, but when I did so, everything seemed to be OK, with a few exceptions: - the custom traffic stats location was lost and went to the default ram location - custom scripts were disabled even though I had them enabled prior to...
  8. E

    [Beta] Asuswrt-Merlin 384.16 beta (and 384.13_5) are available

    FWIW, I'm not seeing the traffic spike on my AC68U, and did see it under beta1. (6 days uptime)
  9. E

    [Beta] Asuswrt-Merlin 384.16 beta (and 384.13_5) are available

    Looks like this commit rolled back the fix from this commit, bringing back the traffic monitor stats breakage.
  10. E

    [Beta] Asuswrt-Merlin 384.16 beta (and 384.13_5) are available

    Seeing that on my AC68U as well. I'm pretty sure that this was fixed prevously with a patch from Eric... but maybe that patch got missed in this round.
  11. E

    Watchdog crash problem

    Didn't see a crash - just a hang. And "ps" showed a huge number of those "cp .../tmp/syslog... /jffs" commands running. I've reformatted /jffs (backed up jffs, selected the reformat on next reboot option, rebooted, then restored /jffs, then rebooted again) and haven't had the problem since...
  12. E

    Watchdog crash problem

    I had this happen yesterday as well - loads of the watchdog restarts getting logged. I was able to run some commands though, and see that any attempt to access /jffs was hanging... so there were a lot of "cp .../tmp/syslog... /jffs" processes running and hung. reboot didn't work - or not...
  13. E

    [Release] Asuswrt-Merlin 384.14 (and 384.13_2) are now available

    I can confirm that the traffic spikes are fixed on my AC68U.
  14. E

    Internet Status: Disconnected?

    It is strange that some bootloaders have ATEMODE=1 and some ATEMODE=0... in fact all the cfe binary files shipped in the GPL bundle for the ac68u variants contain ATEMODE=1 which is what triggers the problem currently. Hacking the bootloader so it sets ATEMODE=0 instead also fixes the problem.
  15. E

    [Release] Asuswrt-Merlin 384.14 (and 384.13_2) are now available

    I built a 384.14 branch with the rstats update mentioned before reverted (the whole thing, as I didn't want to bother trying to pick through it for what specifically caused the bug) and the traffic monitoring false spikes are gone now (12+ hours and about 40GB of data transferred and no problems...
  16. E

    [Release] Asuswrt-Merlin 384.14 (and 384.13_2) are now available

    Neither of the tests worked... any newer GPL/binary blobs applied on top of 384.13, or reverted from 384.14 result in the internet status disconnected, even though it's working. It looks like in release/src/router/rc/services.c, the start_wanduck function is bailing out because of the...
  17. E

    Internet Status: Disconnected?

    On my rt-ac68u, the problem appears to be that wanduck isn't getting kicked off when using firmware newer than 384.13. If I ssh in and manually start up wanduck, then the internet status immediately shows that it's connected.
  18. E

    [Release] Asuswrt-Merlin 384.14 (and 384.13_2) are now available

    Realized (since I didn't see it in the "compile from source" wiki) that I'd compiled a non-mainline .15 firmware, which misses a lot of changes, including the binary blobs... so that explains why my .15 build isn't seeing the problems I saw on the .14 Merlin build (no internet status when there...
  19. E

    [Release] Asuswrt-Merlin 384.14 (and 384.13_2) are now available

    I think I found what's causing it (well, the high level cause though not a specific patch)... in that on the .13 firmware, the wanduck daemon is running, while on the .14 firmware it isn't at all, and that's why the link_internet nvram setting hasn't been updated. I compiled the current .15...
  20. E

    [Release] Asuswrt-Merlin 384.14 (and 384.13_2) are now available

    I know about that.. but it's not a fix and it isn't sticky - reboot and the problem (in the GUI, not actual connectivity) is back.
Top