Modem inaccessible after friendly ip range addition and reboot

I am having an issue with a recently reconfigured RV55. The unit is at a remote location so I cannot download logs.

Before reconfig

  • Modem has 5 ips configured in Input Trusted IP List and 2 ranges in Inbound Trusted IP Range.
  • Connectivity confirmed from the Trusted IPs.

Reconfig

  • New entry added to the Inbound Trusted IP Range. Entry was applied and device rebooted.

After reconfig

  • Device is no longer accessible from any of the previously configured ips and ranges.
  • Device power cycled remotely. Device checked in after remote power cycle.
  • The modem continues to check in on AirVantage.
  • The Inbound Trusted IP Range entries listed in AirVantage are correct and include the new entry.

Other devices have been configured with the same ip range without issue.

Using AirVantage I edited the configuration and removed the new IP range. When I try to Apply Settings using AirVantage it fails.

For further context I applied the new Inbound Trusted IP Range to 27 modems. Out of 27, four had issues and I can no longer connect to them; two RV55 (4.18.1.002) and two RV50 (4.16.0.021). Both RV55 modems continue to check in on AirVantage. The two RV50 modems have not been heard from since the change was made.

This morning, using AirVantage, I was able to change the configuration on the two RV55 modems and remove the new Inbound Trusted IP Range and reboot. The devices are now accessible from the preexisting ip ranges.

In the process I learned that when I lost connectivity after a new ip range was added, and then tried yesterday to use AirVantage to remove the new ip range, the reason the Apply Setting operation failed in AirVantage was that I was deleting the ips leaving blank entries rather than replacing them with the default 0.0.0.0.

The two RV50 modems are still inaccessible and not checking in.

Hi @dalden,

Could you please share the URL link to RV50 and RV55 on AirVantage with me to check it?

Thanks,