Background:

 

This guide offers a comprehensive troubleshooting guide on the IPv4 is not working on the WAN interface.

 

This Article Applies to:

 

All TP-Link(Omada) routers.

 

Troubleshooting Steps:

 

Issue 1: Unable to get an IP address.

 

1. Check the wire and power.

Swap with different Ethernet cables.

Check if you use the original power adapter or if it can supply enough power to your router.

 

2. Check the WAN Connection type.

If you are using Static IP or PPPoE as a connection, make sure that you have selected the Connection Type properly.

Please double-check if your input information is correct. It is quite important to cross-refer this with your previous working routers.

 

3. Check if a WAN VLAN ID is required.

If you are using Dynamic IP as a connection, you might consult with your ISP if a WAN VLAN ID is required. You have to specify the proper VLAN ID before you use it.

 

4. Check if MAC Clone is required.

We usually recommend you consult with your ISP directly on this matter. If they force you to use their ONT or modem, we are not able to fix the issue where you have double NAT.

MAC Clone might bypass the ISP modem-router and ONT but we do not guarantee this.

If you connect your new Omada router to the modem and it does not respond to an IP address, you can try to clone the previous router's MAC address to your new Omada router.

 

• Power down the modem 5 minutes and boot up again might flush the MAC address.
• Consult with your ISP and explain that you need a new router. Request for MAC address flush on their end can also help.
• MAC clone is a way to do it on your own without touching your ISP and other modem settings.

 

The 4G USB modem is in a good position for signal reception. (Optional for USB WAN). No IP address might be a reason where the DHCP interaction cannot even be finished because of a bad signal.

 

Issue 2: Have an IP address but not able to connect to the Internet.

 

1. Check if you can ping any public IP addresses like 8.8.8.8 or 1.1.1.1

If you cannot ping an IP address like a public DNS server, you are likely to experience an issue with your ISP. Consult if your plan is still available or if you need to top up your account.

 

If you can ping these IPs but are not able to connect to regular HTTP/HTTPS webs, you are most likely to face a problem with your host file on your computer.

Or your LAN DNS is misconfigured. Please examine if your LAN DNS is set to either the same as the default gateway IP or a public DNS IP.

 

2. Check if the modem is properly configured.

From the inbound fiber to the modem, do not bend the fiber which may risk breaking the glass.

Contact the modem support or ISP on the LED status on the modem to make sure it is properly connected to the ISP server.

 

Note:

 

1. As IPv4 drains today, the ISP may charge you for the public IPv4 address. If you don't have an IP address on your WAN while setting it to the bridge mode, contact your ISP regarding this. We do not offer support on the ISP level support.

 

Update Log:

 

Feb 14th, 2025:

Release of this article.

 

Recommended Threads:

 

No Traffic After OpenVPN Is Connected - Android/iOS OpenVPN Connect 3.4.0 Update

How to Configure Site-to-Site WireGuard VPN on Omada Controller

How to Configure GRE VPN on Omada Router

 

Feedback:

 

• If this was helpful, welcome to give us Kudos by clicking the upward triangle below.
• If there is anything unclear in this solution post, please feel free to comment below.

 

Thank you in advance for your valuable feedback!

 

------------------------------------------------------------------------------------------------

Have other off-topic issues to report? 

Welcome to > Start a New Thread < and elaborate on the issue for assistance.