• over_clox@lemmy.world
      4·
      4 hours ago

      You heard OP, that clearly fixes everything.

      Now your toaster, microwave, refrigerator, washing machine, etc are all finally cut off from the AI spyware machine…

  • Aceticon@lemmy.dbzer0.comEnglish
    4·
    10 hours ago

    Judging by my experience, router software probably has memory leaks so it eventually runs out of available memory and stops working properly.

    This is more so if you’re using it for something that opens and closes a ton of connections, such as torrenting. In fact maybe 1 or 2 decades ago when those things had less memory the low and mid end quality routers couldn’t handle torrenting directly (so, when the router had to route each new connection, not behind a VPN were its the VPN-server that does it) without dying in a few hours.

    Most slow or even no-connection problems I have get solved by restarting the router, though I have my own router and it’s a high-end consumer one (rather that using the one provided by the ISP), so nowadas that kind of problem happens maybe twice a year at most.

    • MonkderVierte@lemmy.zip
      1·
      8 hours ago

      Consumer routers use neither ECC nor registered or buffered memory, so i guess it’s just the odd bit flip after weeks of running, in most cases.

      • Aceticon@lemmy.dbzer0.comEnglish
        2·
        7 hours ago

        That wouldn’t explain why some fail in hours when there are tons of connections being opened and closed (like with torrenting) whilst others with only twice or four times the memory will last for months, which is far more that two or four times as long.

        I think it’s mainly memory leaks exactly because in my experience the failure rate seems proportional to Free Memory and frequency of memory allocation (hence hitting much more cheaper low memory routers where a much larger proportion of memory is allocated just for static code and data, in usage situations were a ton of small memory allocations are being allocated, than routers with a bit more memory or in normal usage situations) rather than proportional to Total memory in-use even when statically allocated.

        Not to say that the problem you describe doesn’t happen, just that it doesn’t really explain the distribution in frequency of failures depending on router memory and router usage pattern.

  • undefined@lemmy.hogru.chEnglish
    151·
    21 hours ago

    I feel like — like myself — none of the technical users of Lemmy would actually like this. For me, my router is a mini PC running Alpine Linux and it’s likely the modem (which is also my own) is having problems with the physical cable connection but if I were using an all-in-one shit box from the ISP there would be no way of knowing.

    All this to say, if restarting the router “fixes” things there’s likely a deeper, more unsettling problem happening that’s not being diagnosed.

    • Vogons@fedinsfw.appEnglish
      3·
      13 hours ago

      Came here to say just this. ISP box goes into a Debian board with 10 gigE uplink to my actual switching. I asked if I could replace the XGPON-ONT by SFP+s but Alas the sales agent was rather confused and basically said “why?!”…

    • surewhynotlem@lemmy.world
      5·
      18 hours ago

      For me, it was openwrt bouncing the external interface during a DHCP renewal, even when the IP didn’t change. They still haven’t fixed that. I patch the stupid file every upgrade.

      But yeah, at least I could fix it!

    • InEnduringGrowStrong@sh.itjust.works
      10·
      21 hours ago

      All this to say, if restarting the router “fixes” things there’s likely a deeper, more unsettling problem happening that’s not being diagnosed.

      Odds are it’s just some memory leak.
      Having to reboot every 2-3 month isn’t too far fetched for these ISP modem/router.