50% packet loss after cable modem upgrade???

13»

All Replies

  • itxnc
    itxnc Posts: 98  Ally Member
    First Comment Friend Collector Sixth Anniversary

    So… this was new (tried to SSH into the router with Putty)

    CLI via browser worked fine, but this was unexpected… We're on the 2023 WK06 firmware

  • Zyxel_Cooldia
    Zyxel_Cooldia Posts: 1,511  Zyxel Employee
    Zyxel Certified Network Administrator - Security Zyxel Certified Sales Associate 100 Answers 1000 Comments

    Hi @itxnc,

    The most common reason for the 'Couldn't agree a key exchange algorithm' error message in PuTTY is an outdated version of the software.
    To resolve the issue, you can try upgrading to the latest version of PuTTY, which should support the latest key exchange algorithms and security protocols.
    By the way, has the issue been solved by MSO?

  • itxnc
    itxnc Posts: 98  Ally Member
    First Comment Friend Collector Sixth Anniversary
    edited March 2023

    Just to give everyone an update - best we can tell this was/is some weird issue on the ISP backend? They supposedly had techs check out the backend equipment when they "saw metrics that concerned them", but never heard one way or another. The problem seemed to dissipate. However, it does still happen, just now it's intermittent. We'll see a brief packet loss. It seems to happen more (based on ping plot) when we're on the phone. So we're seeing maybe 5-10 brief interruptions per day instead of the constant on/off packet loss that made the connection unusable until we bounced the WAN connection. Packet loss is ALWAYS at the immediate cable modem gateway (not the modem itself). But even 5-10 times a day is not great when clients are constantly saying 'I can't hear you' and sure enough a red bar pops up on PingPlotter then we get voice path back (VoIP/RingCentral). Of course, getting the ISP to agree it's their issue instead of any other vendor we use (Zyxel, RingCentral, etc) is a steep climb. But that's where we are. Best guess is when they swapped out our modem with a newer model/brand, we hit a different gateway and this problem happens.

  • mMontana
    mMontana Posts: 1,389  Guru Member
    50 Answers 1000 Comments Friend Collector Fifth Anniversary

    Following…

  • PeterUK
    PeterUK Posts: 3,389  Guru Member
    100 Answers 2500 Comments Friend Collector Seventh Anniversary
    edited March 2023 Answer ✓

    Maybe another thing to test is set port to 1000Mbps-Full Duplex/Auto Negotiate instead of Auto Negotiate

Security Highlight