Does anyone have information if this is already solved? THere was a major update for the Omada Controller Software but I do not know, if this problem has been solved with this new version. C

  @Honkman Is there anyone from TP-Link followinfg this thread? Any idea when this basic function will be implemented and availabel?

BR
C

  @Honkman I am facing the issue with the ER605. Since we are not able to do port forwarding, is it possible to "manually" add the rules in ACL?

  @Honkman Is there a solution for this issue available? There are newer version of Omada as well as a major new release (v6) but it seems that this has not been solved yet.

Anyone from TP-Link here that can comment on that?

That is really a very basic requirement and almost all routers that we use are able to handle that with ease. This hinders us from rolling out TP-Link gateways.

BR
C

  @Honkman 

It works fine now, tested with an ER707-M2

  @MR.S Are you configuring on the device directly or are you usign the Omada controller? C

  @Honkman 

Omada controller 6.1

  @MR.S I have 6.1.0.19 . And it is still not working and shows the error. I even changed to your gateway model.

How did you configure your WAN interface? I set the IP to the first IP of my IP pool. The subnet mask is 255.255.255.240 in my case. the GW is within the pool (one lower than my first IP). Then I added the additional IPs as WAN IP Aliases. But there the alias addresses are labeled as "IP Subnets". Which, for me, is not correct. If I define a subnet I need to provide an IP and the mask (like 24, 22, 20, etc.). 

How did you do that? Do I need to enter the IP Aliases there? To my understanding it should be sufficient, if I add the correct subnet mask to the main WAN config. THis should tell the router which IPs I can use. Right?

BR
C

  @Honkman 

I configure like this, and rememer to enable, default is disabled when you add