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

Forum Discussion

Roblow's avatar
Roblow
Aspirant
May 07, 2022

The WAN port connectivity stopped working

For the first time in the history of me using the Nighthawk X4S R7800 router, I used the Automatic update feature (usually I manually update it and install it after checking the hash).  However, after the update went through (I didn't notice an error on MD5, but I may not have been looking), the WAN port connectivity stopped working, with a caveat that it can be pinged from the device in front of it (the modem).

 

The equipment is below:

 

Verizon FiOS Gateway router (nothing fancy)

Nighthawk X4S R7800

 

Connections go from the Fiber box via ethernet to the FiOS router to the WAN port, then one of the LAN ports is configured to link back to the WAN port on the Nighthawk.  There is no DHCP on that link, so a manual IP address needs to be put in.  The LAN network address of the FiOS router is different from the LAN address of the Nighthawk (I know that's double nat). 

 

Everything was working perfectly before the update.  The only change was the update.  When a device is plugged directly into the FiOS router, there is internet connectivity.

 

Now, I am going to run through the following steps until something fixes it:

 

1. Download and install manually v1.0.2.90 firmware and upload it to the Nighthawk

2. Download and install manually v1.0.2.8x firmware and upload it to the Nighthawk

3. Re-upload v1.0.2.90 firmware and factory reset the Nighthawk

4. Remove the Nighthawk router from the network, setting the FiOS router as the connection medium, and eBay the Nighthawk

 

Even as a network technician for many years, I get tired of companies having poor change management programs that causes customers to work this hard to restore their services when they're trying to just keep up with the limited security issues that plague the Internet as a whole. 

 

 

 

 

5 Replies

  • plemans's avatar
    plemans
    Guru - Experienced User
    May 07, 2022

    Roblow If you're wanting help, we'd recommend starting your own thread so we can help you specifically and not get your details confused with the OP's. If you're just posting to be informative to the fact that you're having issues, thanks for doing so. 

    • Roblow's avatar
      Roblow
      Aspirant
      May 07, 2022

      plemansyep, just adding to the same issue as the OP.  Trying to identify the resolution for others so they don't have to go through the same process (especially those who aren't technicians by trade).

  • Roblow's avatar
    Roblow
    Aspirant
    May 07, 2022

    After installing v1.0.2.90, the error you see on the Internet is pictured below.

     

    From my previous post:

    1. Completed, no change to the issue

    2. Completed on versions .86 & .84, no change to the issue

     

  • Roblow's avatar
    Roblow
    Aspirant
    May 07, 2022

    3. Powered off the device for 2 minutes and turned it back on.  No change in results, so went back to v1.0.2.90 (manual install).  Went to factory reset, but then realized the connection showed "good" on the Internet.  The only change made before the upgrade back to v1.0.2.90 was updating the NTP server to a known good server (I noticed the time was off by 6 months anyway for some reason).  The possibility is that NTP updated the time and then the FiOS router allowed the connectivity (or the Nighthawk did--still not sure which).

     

    I needed to research the "[DoS Attack: IP Spoofing] from source:" issue because I started getting a flood of those error messages in my logs from two client devices, however many posts state to not worry about them (possible false positives).  Those two devices may be IoT devices, which is harder to troubleshoot since connectivity back to them is not usual.

     

    It's hard to say what fixed the issue, but if you run through the same steps I did, you may get it back to good without factory reset.

     

    Rob Low