Forums

Home Forums Troubleshooting I think I bricked a AX1800 and WR619AC

I think I bricked a AX1800 and WR619AC

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #7414
    ARugger
    Participant

    I configured (off line) the AX behind a Netgear modem. No issues with Ethernet or Wi-Fi internet connections. I later decided to use an existing Newfi D2 as an access point, and configured it (offline) per the blog article, tagging LAN (port 1). The next step required tagging LAN (port 1) on the AX. Multiple attempts to login failed, so I reset it and tried to reconfigure it, but after saving from network settings, it went into perpetual reboot. I bailed and reset again, but this time, I could not get to initial set up, I tried all of the suggestions by support. Thinking that the LAN port might be bad, I configured the WR619 the same (logged in easily, offline), and the same thing happened.

    Looking back, I changed the default LAN IP to 10.xx.xx.x and confused DHCP limit to mean end (75 start, limit 200). Same thing happened in the demo, perpetual reboot. Either or both I think caused this, though now, after scouring the forum, I think it was changing the default LAN IP.

    I had logged into multiple pcwrt routers off line using a MacBook and Firefox with no issues, but I don’t think I made the same changes as I did with the above. I have scoured this forum before and after these events and I have never read not to change the default LAN IP, if that is what caused it.

    What do you think happened? Possible solution or paperweights?

    Thanks in advance

    #7415
    ARugger
    Participant

    Edit: configured offline and connected behind a netgear modem.

    #7417
    ARugger
    Participant

    All good for now, computer port issue
    Still curious about changing LAN IP and perpetual reboot, I’ll use default for now

    #7460
    support
    Keymaster

    Changing the LAN IP address to 10.0.0.1/24 won’t kick the router into a perpetual rebooting loop. Nor would changing DHCP params to 75 start, limit 200. Even though the latter gives invalid range (i.e., the max (75 + 200 -1) > 254), the router will clamp the max to 254. It must be something else that’s causing the perpetual reboot.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.