WAN IP Alias Not Working
Hi Team,
My ISP has provided a /29 public IP block, and they mentioned that the IPs are “assigned” to us, not explicitly routed to our main WAN IP.
I’m using a TP-Link ER605 managed via Omada Controller.
Here’s the issue:
-
When I assign one of the public IPs as the main WAN IP, it works fine.
-
But if I assign other IPs from the same block as WAN IP Aliases, they do not work — cannot ping, cannot use for NAT, etc.
-
My goal is to use these additional IPs for One-to-One NAT or port forwarding to internal devices.
Since the ISP is not routing the block to a single IP, I assume that using WAN IP aliases (or Virtual IPs) won’t work unless proper routing is in place.
Questions:
-
Is there a way to make these IPs usable via alias or NAT if they’re only “assigned” and not routed?
-
Or do I need the ISP to route the entire /29 block to a single usable WAN IP for aliases and NAT to work?
Appreciate any clarification on how TP-Link handles this scenario.