CM3000 Slow Login with New Firmware (V6.01.03)

@EG​ - correct - the paperclip was inserted for 30 seconds.  After the reset I had to use the original password that shipped with the unit.  Wondering if it is a bug with the new firmware Comcast pushed out this week. V5.01.02 --> V6.01.03.  Internet speeds and ping times are not affected.  I just can't log into the web interface on the Netgear CM3000 to see channel signal levels.  It icon just spins.  The initial login used to take a few seconds.  Now it takes over 20 seconds to login.

Hi @slthomas00 Thank you for reaching out on the Xfinity Community forums. Are you still seeing an issue with your modem? Have you contacted the OEM for the modem to see if there is anything on their end as well? As mentioned by our amazing expert @EG we have not received any reports of this happening with the latest firmware you received. Technology of course can take time to notice and we appreciate you reaching out. 

@XfinityJanelle​ yes I opened a ticket with Netgear for the CM3000. Right now their first suggestion was a factory reset which I already did. I am still experiencing the slow logins since the firmware update push last Wednesday. Internet performance though is not affected. Previously I could login fine with the older firmware. 

Thank you for providing us with an update @slthomas00. Has Netgear mentioned any other solutions since doing the factory reset?

@XfinityQuemekia​ no - they have not provided any other guidance.  They did ask why I wanted to log into the modem though and I explained that I want to view signal levels and error logs.  Again to recap - performance is not affected (ping times and download/upload speeds), but logging into the modem and viewing logs is extremely slow since the V6.01.03 firmware upgrade.  I will reply back if Netgear has any other advice which I don't believe they will.

Hi @dsm1212,
Thank you for joining in on the discussion here! I see you already have a technician scheduled to come out Monday, would you mind letting the community and I know how things are looking post appointment?

Hi there @dsm1212, how did the appointment go?

PS - Are all of you challenged in even logging in to the modem via the IP address since the firmware update? I can slowly log in, then it times out if I try to access another page, i.e. connection tab, event log, etc. This and connectivity issues. 

If you reboot the modem it will be snappy again.

To be honest though, my modem does not actually restart. It just drops the connection to my router. Does the modem log show yours is actually restarting?

Thank you for the update as I have a call scheduled w/Netgear in 3 hours. This will be helpful. Xfinity also encouraged me to try out their modem/router to see if the problems continue. You've confirmed it helps - in your case/area. Principally speaking I struggle with the $299 Netgear expense to now having to pay a monthly rental fee to use a product in gateway mode to resolve matters. My understanding is that Netgear sends the software updates to Xfinity's IT team who may tweak /fine-tune it prior to distribution. A money maker for Xfinity... 

I have someone from Xfinity coming monday. Even though it is probably a waste of time, we are slaves to their process. I'm going to lobby for going back to the earlier firmware. I had consistent 2.2-2.3Gbps down before the fw update.

For the moment I asked claude to write me a bash script to reboot the modem. I had to provide it the javascript from the index.htm and routerStatus.htm pages. Seems to work so I scheduled it to run on my NAS every day at 5:30. AI saves the day :-).

dsm1212 - I wish I knew how to revert to the previous firmware. What you did is over my head. I spoke to both Netgear and Xfinity Supervisor yesterday. I can't access the modem via a hardwired PC. I made reference to comments above. Netgear wants to suggest it may be a bad modem. I happen to be a Best Buy Total Member so I have the added 2 year coverage. I've opted to go thru the motions and pick up a new replacement modem today. I am very appreciative and in close contact w/the Xfinity Supervisor. Yesterday he stated he is not seeing ANY data coming from my modem on their end, yet I have internet (except the intermittent drops). Per his suggestion, I'll then go to the Xfinity store and have them activate the new modem right there. After connection, I immediately want to see what firmware is on it. I will update the Supervisor via text to let him know the new modem is online. He'll let me know what he sees on Xfinity's side. If this doesn't work - regrettably, I'll be going the slthomas00 route and using an Xfinity modem. 

Here is the reboot script claude.ai wrote. You need to set the password value. If you have a linux server or nas running linux, schedule this to run this once a day to avoid the meltdown until they have a fix. I'm sure they will address this bug sooner or later.

#!/bin/bash

# NETGEAR CM3000 Modem Reboot Script
# This script logs into the modem and triggers a reboot via the web interface

# Configuration
MODEM_IP="192.168.100.1"  # Default CM3000 IP - change if different
USERNAME="admin"
PASSWORD="password"
COOKIE_JAR="/tmp/cm3000_cookies.txt"

# Colors for output
RED='\033[0;31m'
GREEN='\033[0;32m'
YELLOW='\033[1;33m'
NC='\033[0m' # No Color

# Function to print colored output
print_status() {
    echo -e "${GREEN}[INFO]${NC} $1"
}

print_warning() {
    echo -e "${YELLOW}[WARN]${NC} $1"
}

print_error() {
    echo -e "${RED}[ERROR]${NC} $1"
}

# Function to check if modem is reachable
check_modem_connectivity() {
    print_status "Checking modem connectivity..."
    if ping -c 1 -W 3 "$MODEM_IP" > /dev/null 2>&1; then
        print_status "Modem is reachable at $MODEM_IP"
        return 0
    else
        print_error "Cannot reach modem at $MODEM_IP"
        return 1
    fi
}

# Function to perform login
login_to_modem() {
    print_status "Logging into modem..."

    # First, get the login page to establish session

    LOGIN_RESPONSE=$(curl -s -c "$COOKIE_JAR" \
        -A "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36" \
        "http://$MODEM_IP/")

    if [ $? -ne 0 ]; then
        print_error "Failed to access login page"
        return 1
    fi

    # Extract the login form action and any hidden fields
    LOGIN_URL=$(echo "$LOGIN_RESPONSE" | grep -oP 'action="[^"]*"' | sed 's/action="//;s/"//')
    if [ -z "$LOGIN_URL" ]; then
        LOGIN_URL="/goform/Login"
    fi

    # Perform login
    LOGIN_RESULT=$(curl -s -b "$COOKIE_JAR" -c "$COOKIE_JAR" \
        -A "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36" \
        -d "loginName=$USERNAME" \
        -d "loginPassword=$PASSWORD" \
        -X POST \
        "http://$MODEM_IP$LOGIN_URL")

    if [ $? -ne 0 ]; then
        print_error "Login request failed"
        return 1
    fi

    # Check if login was successful by looking for redirect or success indicators
    if echo "$LOGIN_RESULT" | grep -q "index.htm\|main\|successful" || [ ${#LOGIN_RESULT} -lt 100 ]; then
        print_status "Login successful"
        return 0
    else
        print_error "Login failed - check username/password"
        return 1
    fi
}

# Function to navigate to advanced tab and reboot
perform_reboot() {
    print_status "Accessing main page and advanced tab..."

    # Access the main page after login
    MAIN_PAGE=$(curl -s -b "$COOKIE_JAR" \
        -A "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36" \
        "http://$MODEM_IP/index.htm")

    if [ $? -ne 0 ]; then
        print_error "Failed to access main page"
        return 1
    fi

    print_status "Accessing RouterStatus.htm frame (Advanced tab content)..."

    # Access the RouterStatus.htm frame that contains the reboot functionality
    FRAME_CONTENT=$(curl -s -b "$COOKIE_JAR" \
        -A "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36" \
        "http://$MODEM_IP/RouterStatus.htm")

    if [ $? -ne 0 ]; then
        print_error "Failed to access RouterStatus.htm frame"
        return 1
    fi

    # Verify the frame contains the reboot functionality
    if ! echo "$FRAME_CONTENT" | grep -q "advButt"margin: 0;">    print_status "Found reboot functionality in RouterStatus.htm"
    FRAME_URL="RouterStatus.htm"

    print_status "Initiating reboot command..."

    # Look for the form action in the frame content
    FORM_ACTION=$(echo "$FRAME_CONTENT" | grep -oP 'action="[^"]*"' | head -1 | sed 's/action="//;s/"//')
    if [ -z "$FORM_ACTION" ]; then
        # Try common form actions for RouterStatus
        local common_actions=(
            "/goform/RouterStatus"
            "/goform/router_status"
            "/goform/status"
            "/goform/advanced"
            "/goform/cable_information"
        )

        for action in "${common_actions[@]}"; do
            print_status "Trying form action: $action"
            REBOOT_RESPONSE=$(curl -s -b "$COOKIE_JAR" \

                -A "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36" \
                -d "buttonSelect=2" \
                -X POST \
                "http://$MODEM_IP$action")

            if [ $? -eq 0 ]; then
                print_status "Reboot command sent successfully via $action"
                return 0
            fi
        done

        print_error "Could not determine correct form action"
        return 1
    else
        # Execute the reboot command by submitting the form with buttonSelect=2
        print_status "Using form action: $FORM_ACTION"
        REBOOT_RESPONSE=$(curl -s -b "$COOKIE_JAR" \
            -A "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36" \
            -d "buttonSelect=2" \
            -X POST \
            "http://$MODEM_IP$FORM_ACTION")

        if [ $? -eq 0 ]; then
            print_status "Reboot command sent successfully"
            return 0
        else
            print_error "Failed to send reboot command"
            return 1
        fi
    fi
}

# Function to verify reboot started
verify_reboot() {
    print_status "Verifying reboot has started..."
    sleep 5

    # Try to ping the modem - it should become unreachable during reboot
    local attempts=0
    local max_attempts=12

    while [ $attempts -lt $max_attempts ]; do
        if ! ping -c 1 -W 2 "$MODEM_IP" > /dev/null 2>&1; then
            print_status "Modem is rebooting (no longer responding to ping)"
            return 0
        fi

        attempts=$((attempts + 1))
        print_status "Waiting for reboot to start... (attempt $attempts/$max_attempts)"
        sleep 5
    done

    print_warning "Modem still responding - reboot may not have started"
    return 1
}

# Function to wait for modem to come back online
wait_for_online() {
    print_status "Waiting for modem to come back online..."
    local attempts=0
    local max_attempts=60  # Wait up to 5 minutes

    while [ $attempts -lt $max_attempts ]; do
        if ping -c 1 -W 3 "$MODEM_IP" > /dev/null 2>&1; then
            print_status "Modem is back online!"
            return 0
        fi

        attempts=$((attempts + 1))
        if [ $((attempts % 6)) -eq 0 ]; then  # Print status every 30 seconds
            print_status "Still waiting for modem... (${attempts}0 seconds elapsed)"
        fi
        sleep 5
    done

    print_warning "Modem did not come back online within expected time"
    return 1
}

# Cleanup function
cleanup() {
    if [ -f "$COOKIE_JAR" ]; then
        rm -f "$COOKIE_JAR"
    fi
}

# Main execution
main() {
    print_status "Starting CM3000 modem reboot process..."

    # Set trap for cleanup
    trap cleanup EXIT

    # Check if curl is available
    if ! command -v curl &> /dev/null; then
        print_error "curl is required but not installed. Please install curl and try again."
        exit 1
    fi

    # Step 1: Check connectivity
    if ! check_modem_connectivity; then
        print_error "Cannot proceed - modem is not reachable"
        exit 1
    fi

    # Step 2: Login
    if ! login_to_modem; then
        print_error "Login failed - cannot proceed"
        exit 1
    fi

    # Step 3: Perform reboot
    if ! perform_reboot; then
        print_error "Reboot command failed"
        exit 1
    fi

    # Step 4: Verify reboot started
    if verify_reboot; then
        print_status "Reboot initiated successfully"

        # Wait for modem to come back online if running interactively
        if [[ -t 0 && -t 1 && -t 2 ]]; then
            print_status "Running interactively - waiting for modem to come back online..."
            wait_for_online
        else
            print_status "Running non-interactively - not waiting for modem recovery"
        fi
    else
        print_warning "Could not verify reboot started"
    fi

    print_status "Script completed"
}

# Run main function if script is executed directly
if [[ "${BASH_SOURCE[0]}" == "${0}" ]]; then
    main "$@"

fi

@Maggiekev​ I am at almost the 2 week mark with the Comcast XB8 modem in gateway mode in front of my Firewalla firewall.  I only see 2 "correctable" errors in the error log on the XB8.  My ping scripts to google.com running every 20 seconds have been solid.  The Firewallla box also shows no downtime.  The Netgear CM3000 would always show "uncorrectable" errors every other day.  My ping script would also fail with the CM3000.  Like you it was tough for me to accept the $299 cost of the Netgear CM3000 was no longer usable.  Some sort of mental relief is I was paying $30/month with the Netgear CM3000 for unlimited data.  With the XB8 - I signed up for the xFi option which is $25/month and includes unlimited data.  

@Maggiekev​ & @dsm1212  - I had a few T3 timeouts as well in my CM3000 logs.  My understanding normally those are tied to weak/strong signals and/or cabling issues.  I had a Comcast tech visit with a confirmation of signal levels at acceptable levels and no cabling issues.  In regards to your question on gateway (bridge) mode for the XB8, yes you will want to enable that on the XB8.  It is on the first tab and simple click of the button.  I use a Firewalla firewall behind it so using gateway (bridge) mode will operate the same as the CM3000 (no double NAT).  When you put the XB8 in gateway mode, it disables the wireless.  However, the radios are still active and show as hidden networks when I use inSSIDer wifi analyzer.  The public wifi option is also still enabled.  You will first want to be in router mode on the XB8 and disable the public Xfinity wifi option.  I also then put all 3 radios on unused channels and reduced the channel widths to 20 MHz so that my ASUS routers (in AP mode) would not have wireless interference with the XB8 hidden wireless networks.  Like dsm1212 - I am now on a 5 year price locked plan.  Saving $5/month will eventually get me my money back I spent on the CM3000 :-)

@slthomas00​ Nice, thanks for the tips.