Hi @Matva 

Thanks for posting in our business forum.

Matva wrote

I am running the Software Controller on Linux, version 5.13.22.

 

After upgrading my ER707-M2 v1 router from version 1.0.2 to version 1.2.0 I am no longer able to reach the internet.

 

From any device within my network I can ping any other LAN IP address, but I am unable to ping the Gateway / WAN address of my ISP modem. Any device I connect to the ISP modem directly is having no issues.

 

So to me, it looks like there is something wrong with the internal routing table or something? Downgrading back to 1.1.1, 1.02, or any of the beta versions does not resolve the issue.

 

See screenshot:

 

 

I found another topic with a similar issue where the person ended up removing all VPN profiles. I did that as well. Rebooted the controller, rebooted every device, rebooted the ISP modem,... Nothing.

 

Any ideas or other suggestions would be very great. Thanks!

1. The issue is not the same as the @MR.S . It is not the same and has nothing in common at all.

2. What you pinged is the IP address of the gateway of your router on the WAN, which is a double-NAT scenario.

Let me ask you this, can you ping this IP address 192.168.0.1 in the past?

What is the result if you ping 8.8.8.8 or 1.1.1.1 at this time stamp? It is ping-able, right? Your WAN status is Online which means it gets Internet. This contradicts what you said.

This explains how the Online status works. Common Questions About the Load Balancing & Link Backup(Failover)

3. Downgrading to any previous firmware does not resolve this issue, so it seems to be the case where your first NAT issue. Nothing to do with the Omada router.

Like the comment in 2.

4. In your last reply, you mean after resetting the router, you can ping the IP address of 192.168.0.1 or your actual public IP now?

Hi @Matva 

Thanks for posting in our business forum.

Matva wrote

  @Clive_A 

 

Thanks for checking. I do not believe it to be a NAT issue. As mentioned, when I put my ISP modem in Bridge mode I get a public IP address directly on my ER707. Furthermore, this has always worked before the upgrade. I was able to ping the router on both LAN and WAN interface, as well as any public IP (1.1.1.1, 8.8.8.8,...) It is only after upgrading the ER707 to version 1.2.0 that these issues started occurring. No settings were changed prior to, or after, the upgrade.

 

By resetting the router and re-adopting it, the issue is now resolved. Again without changing any settings on the controller or ISP Modem.

 

Which does lead me to believe that *some* (hidden) setting was changed on the router during the upgrade (NAT, Routing,...?). Inter-VLAN routing kept working fine during the issue. All static routes to all VLANS were indeed present in the routing table.

 

I just checked the routing table and noticed something interesting: Yesterday, during the issue, I only had static routes for all VLANS. Now, I suddenly have additional static routes towards the internet with entry 0.0.0.0/0 pointing to the next-hop, being my ISP gateway IP.

 

So this seems to confirm that the upgrade to 1.2.0 messed up the internal routing tables somehow, clearing the static default route towards internet.

Can you export your backup for me? Let me know if you agree to share your backup or not.

Hi @Matva 

Matva wrote

  @Clive_A 

 

I can do that. Do you need the autobackup .cfg files or Export For Support logs?

Thank you so much for taking the time to post the issue on TP-Link community!

To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID240116513, please check your email box and ensure the support email is well received. Thanks!

Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.

Many thanks for your great cooperation and patience!

Hi @Matva 

Thanks for posting in our business forum.

Matva wrote

  @Clive_A 

 

Thank you. E-mail well received. I have sent the current backup via e-mail.

 

Please note that everything is currently fully operational for me again. If needed, I can also provide a backup from before the upgrade to 1.2.0.

Is everything the same just different firmware? I may downgrade to the previous firmware and adopt then upgrade.

If something's different, please resend the backup to me. I'll check again. If possible, provide the non-support and support version at the same time. Thanks.