• stephner74@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    16 minutes ago

    Yes I’m a genius in that aspect I could tell you what to do when you’re out of subscription 😅

  • Aceticon@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    4
    ·
    3 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
      link
      fedilink
      arrow-up
      1
      ·
      1 hour 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.

  • Cousin Mose@lemmy.hogru.ch
    link
    fedilink
    English
    arrow-up
    14
    ·
    edit-2
    15 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.app
      link
      fedilink
      English
      arrow-up
      3
      ·
      6 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
      link
      fedilink
      arrow-up
      5
      ·
      11 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!

      • wonderingwanderer@sopuli.xyz
        link
        fedilink
        arrow-up
        1
        ·
        25 minutes ago

        But yeah, at least I could fix it!

        Isn’t openwrt open-source? If you fixed it on your machine, couldn’t you submit a PR to their codebase?

        • surewhynotlem@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          26 minutes ago

          This is the file:

          /etc/hotplug.d/iface/20-firewall

          In there, there’s a line that says

          [ "$ACTION" = ifupdate -a -z "$IFUPDATE_ADDRESSES" -a -z "$IFUPDATE_DATA" ] && exit 0

          change it to

          [ "$ACTION" = ifupdate -a -z "$IFUPDATE_ADDRESSES" ] && exit 0

          I pieced it together from this post, if it’s still around: https://github.com/openwrt/openwrt/issues/10338

    • InEnduringGrowStrong@sh.itjust.works
      link
      fedilink
      arrow-up
      9
      ·
      15 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.