NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

liamscor's avatar
liamscor
Luminary
Jun 10, 2025

I found that disabling all logging and then performing a full power cycle of my 963 system

I found that disabling all logging and then performing a full power cycle of my 963 system—a step I came across in the post linked below (which discusses BE systems)—resulted in a significant performance improvement in my setup, allowing me to have a mucher longer uptime before needing to reboot for system stability.

 

I was also encountering a connectivity issue with certain devices after 5–8 days, which required a full system reboot to resolve. After disabling logging, that issue seems to have been resolved as well. I thought this might be helpful to share in case others are facing similar problems.

 

https://community.netgear.com/discussions/en-home-orbi-be/orbi-be-series-troubleshooting-tips---reboots-and-crashes/2449415

10 Replies

  • FURRYe38's avatar
    FURRYe38
    Guru - Experienced User

    Only ones I have enabled on my 963 system:

    Include in Log
     
     
    Connections to the Web-based interface of this Router
    Router operation (startup, get time etc)
    Known DoS attacks and Port Scans
     
    Wireless access
     
     

    I also have SIP ALG enabled as well. Normally disabled by default. Was mentioned years ago that enabling this helped as well. 

     

    • donawalt's avatar
      donawalt
      Mentor - Experienced User

      FYI I read SIP ALG (Application Layer Gateway) is a helper service meant for old VoIP systems — it inspects and modifies SIP (Session Initiation Protocol) packets for voice calls.

      On many modern routers, SIP ALG causes more harm than good, breaking VoIP calls, Ring doorbells, or Teams/Zoom sessions. Disabled for me, haven't seen any issues.

      • FURRYe38's avatar
        FURRYe38
        Guru - Experienced User

        There was a known issue about 15+ years ago with SIP ALG. Also uPnP. I've been using SIP ALG and uPnP since then. Have not seen any issues. Have also asked beta testers to help test SIP ALG in past projects with it enabled or disabled, have had zero problems with it. I would presume and guess that since 15 years have passed that the core devs for SIP ALG and uPnP have make corrections and changes to these features since then, and should not be a problem to use them either way today. 

  • Just an update on this, I have found that if you have netgear armor enabled, there then seems to be some issue related to the logging, I have now factory reset and setup from scratch via the via web gui and not used the orbi app, and haven't had to disable any logging.

    • FURRYe38's avatar
      FURRYe38
      Guru - Experienced User

      Good ol Armor doing stuff. 

      Wondering if you used Orbi app and disabled Armor in the app, does problem still continue? 

      • liamscor's avatar
        liamscor
        Luminary

        Disabling armor doesn't seem to fix the issue, at least for me anyway.