Menu
What's new
By:
Filters Better Search

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

    AC88U with 386.4 - DHCP lost after a day

    I would've thought that spaces in names would've caused an immediate problem, rather than something that would spring up hours later... in any case, if you ssh into the router and run "top" I was seeing the dnsmasq process constantly sitting at the top of the output, which is not normal... and...
  2. E

    AC88U with 386.4 - DHCP lost after a day

    Was seeing the same thing on my router (AC86U) and "service restart_dnsmasq" fixed it... dnsmasq was spinning on the cpu but not handing out leases. Maybe this was what was happening to you as well? See here
  3. E

    Release Asuswrt-Merlin 386.4 is now available

    Was seeing the same thing on my router (AC86U) and "service restart_dnsmasq" fixed it... dnsmasq was spinning on the cpu but not handing out leases. Seems like it could be related to https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q1/016018.html ("Infinite loop in dnsmasq v2.86?")
  4. E

    Release Asuswrt-Merlin 386.4 is now available

    I'm seeing a problem also related to dnsmasq causing problems... after a day or 12 hours (seems random) my devices stop being able to renew their leases and start failing to get to the internet... looking at the router GUI, the cpu is being heavily used, and when I check "top" it's clear that...
  5. E

    AiMesh nodes disconnect since 386.1

    Maybe my "problem" is different... I don't see anyone mentioning "restart_wireless" in their logs, which is what I took to be a problem. It doesn't happen all that often and I haven't actually had complaints from those attached to the mesh node about issues (maybe they had connected to another...
  6. E

    Release Asuswrt-Merlin 386.2 is now available

    Upgraded an AC86U from 386.1_2 to 386.2 (dirty flash, though was factory reset when installing 386.1_2) and all seems fine, except the yellow flashing exclamation point says there's newer firmware available, but of course the admin page shows that everything is up to date. Maybe a stale nvram...
  7. E

    Traffic spike fix from 384.14_2 was reverted in 386.1

    I've upgraded my router to an AC86U in the meantime (from an AC68U) and haven't seen the spikes in the 24h or daily roll-ups any more, but do see them in the real-time view, within 5-10s of looking, it will jump to 2147500KB/s. But since it's not affecting the overall data, I haven't put in the...
  8. E

    High RAM Usage RT-AC86U

    For those who say that free memory going near zero isn't a problem... I agree that it might not be, assuming that you've got a lot in cache... however, take a look at process sizes over time and I think you'll notice that some of them do seem to leak and get larger over time, which will lead to...
  9. E

    AiMesh nodes disconnect since 386.1

    How did this go? I'm also seeing issues with my aimesh node inexplicably disconnecting randomly when running 386.1_2. I've also tried running the latest stock fw on the node but have seen the same problem. Maybe just putting 384.19 on the node would be better.
  10. E

    new AC86U crashes after 5 or 6 days

    Yep - already had that setting when the problem reboots happened.
  11. E

    new AC86U crashes after 5 or 6 days

    Haven't got any samba/usb sharing enabled at all. And since I currently have no scripts running (just FlexQOS which doesn't use the usb device), I guess it might be worth simply removing the usb stick to see if things are stable without it.
  12. E

    new AC86U crashes after 5 or 6 days

    You mean this: I've never had that enabled... so I guess that's not my problem.
  13. E

    new AC86U crashes after 5 or 6 days

    I've got a mesh setup which used to run with 3 AC68U devices and I've swapped in a new AC86U as the central device in the mesh... and it works fine (factory reset with Merlin 386.1_2, temp hovers around 77-78C all the time), but it's crashed/rebooted on me twice since I started using it. After...
  14. E

    Traffic spike fix from 384.14_2 was reverted in 386.1

    I would test an AC68U firmware if they had one available to test.
  15. E

    [Beta] VNSTAT on Merlin; CLI, UI and email data use monitoring (install script offline for now)

    I had not used vnstat prior to today. And the timestamps were probably messed up somewhat due to TZ not being set in my command line nor the startup script for vnstat. I've added the TZ setting now and appear to be getting reasonable data currently. Still don't know where the original "extra"...
  16. E

    [Beta] VNSTAT on Merlin; CLI, UI and email data use monitoring (install script offline for now)

    So I installed this by hand, following the instructions (I think) at the github site and I'm getting data, but while the graphs are showing info, I'm not sure it's right... since the graph is showing data that doesn't match the command line output, and I've only been running it for a little over...
  17. E

    Traffic spike fix from 384.14_2 was reverted in 386.1

    That's not why I'm using the traffic data - I just like to have the data as a nice to have... if it's broken, it doesn't really matter to me, but it would be nice if it worked. Guess I'll probably switch to the alternate (not part of merlin) traffic data stats solution mentioned earlier in this...
  18. E

    Traffic spike fix from 384.14_2 was reverted in 386.1

    Don't think there's anything else to test, given this setup, is there?:
  19. E

    Traffic spike fix from 384.14_2 was reverted in 386.1

    Well, since I can't use cake-qos (ac68u not supported) but I am using FlexQOS, shouldn't my hw accel also be disabled? I'm still seeing the spikes with this config/hardware.
  20. E

    Traffic spike fix from 384.14_2 was reverted in 386.1

    Still getting spikes daily here - multiple. I doubt that since the problem appears to be a wraparound issue that they'd simply go away over time. And even if they did, simply having them every reboot would effectively kill/swamp out the normal data represented on the graph for any period that...
Top