A hardwired device failing to receive an IP address on a non-default VLAN in TP-Link Omada typically stems from incorrect switch port configuration, specifically the Untagged Port setting. The most common fix is ensuring the target switch port is added as an Untagged member for the specific VLAN ID while keeping it tagged or untagged for the default network as required by your topology.
Verify Switch Port Configuration
The primary cause of this issue is misconfiguration at the physical switch level within the Omada Controller. Each switch port must be explicitly configured to handle the VLAN traffic. If a port is not set to
Untagged for the new VLAN, the connected device will not see the broadcast domain necessary to request an IP via DHCP.
Navigate to the
Omada Controller and select your managed switch from the device list. Open the
Port Management section. Here you will see a grid representing each physical port. Locate the port where your problematic device is connected. Click the
Edit icon (usually a pencil) for that specific port.
In the
VLAN Settings tab, you will see a list of available VLANs. You must ensure two things:
- The target VLAN ID is present in the list.
- The mode for that VLAN is set to Untagged.
If the VLAN is missing entirely, click
Add VLAN, enter the correct VLAN ID, and set it to
Untagged. This tells the switch to strip the VLAN tag before sending frames to the end device, which is standard for most PCs, printers, and IoT devices. After making changes, click
Save and apply the configuration.
Check Router and DHCP Scope
Once the switch port is correctly configured, the next step is verifying that the router can actually assign addresses for that VLAN. In Omada, the router (or gateway) must have an interface configured for the new VLAN ID. If the VLAN exists on the switch but not on the router, the DHCP requests will bounce back or drop.
Log into your Omada Gateway/Router settings. Go to the
Network or
Interfaces section. Ensure there is a dedicated interface for the new VLAN ID. Check the following:
- DHCP Server Status: It should be enabled for this interface.
- IP Range: Verify the pool has available addresses.
- Subnet Mask: Ensure it matches your intended network design (e.g., /24).
If you recently changed VLAN settings on the switch, restart the DHCP service on the router or reboot the router to ensure it picks up the new interface configuration. A stale DHCP lease on the client side can also prevent renewal, so releasing and renewing the IP on the PC is a quick diagnostic step.
Validate Physical Layer and PoE Dependencies
Sometimes the issue is not logical but physical. If your device is powered via PoE or connected through a chain of equipment, intermediate failures can isolate the VLAN traffic. For instance, if you are using a PoE splitter for an IoT device, ensure the splitter is functioning correctly. Data reception issues often mimic VLAN problems when the power delivery fails intermittently. Refer to our guide on
Troubleshooting IoT Device Data Reception Issues with PoE Splitter to rule out hardware faults.
Additionally, check the cable integrity. A damaged Ethernet cable might support basic connectivity but fail under the specific load or signaling requirements of tagged/untagged transitions. Try swapping the cable with a known good one. If you are connecting multiple switches, ensure the uplink ports between them are configured as
Tagged for all relevant VLANs. Without proper trunking between switches, VLAN traffic cannot traverse the network backbone. See
Solving Ethernet Issues: The Role of Ethernet Switches for more details on inter-switch connectivity.
Review ACL and Security Policies
If the port is untagged and the DHCP scope is valid, access control lists (ACLs) may be blocking the traffic. Omada allows you to restrict communication between VLANs or devices. Check if any
Access Control rules are inadvertently dropping packets from the new VLAN or allowing only specific IPs. Temporarily disable strict ACLs to test if connectivity returns.
Also, verify that the device itself is not reserving an old MAC address binding that conflicts with the new subnet. On the Windows machine, open Command Prompt and run
ipconfig /release followed by
ipconfig /renew. On macOS, go to Network Preferences, select the adapter, and click
Renew DHCP Lease.
Frequently Asked Questions
Why is my device getting an APIPA address (169.254.x.x)?
An APIPA address indicates the device failed to contact a DHCP server. This usually means the switch port is not untagged for the correct VLAN, or the router lacks a DHCP scope for that VLAN ID. Verify the port configuration in the Omada controller first.
Can I use a single VLAN for both VoIP phones and regular computers?
It is generally recommended to separate VoIP traffic into its own VLAN for Quality of Service (QoS) prioritization. While possible to mix them, it complicates troubleshooting and security policies. Use distinct VLAN IDs for voice and data networks.
Do I need to configure the router interface before configuring the switch?
No, but the order matters for testing. You can configure the switch ports first. However, if the router does not have an interface defined for that VLAN ID, the switch will pass traffic that the router cannot process. Ensure the router interface exists to avoid confusion.
What happens if I forget to set a port as Untagged?
The end device will receive frames with 802.1Q tags attached. Most consumer PCs and IoT devices do not understand these tags and will discard the frames, resulting in no network connectivity or failure to obtain an IP address.