@Honkman 

The name IP subnet is a bit misleading, there is no subnet but you have to enter one IP address that is in the pool you have.

  @MR.S Not working on my side. Tried it exactly like that. Tried different gateway models. Always the same error message. Enoying.

Whenever I try to change the source port of Test2 to 443 I get the error message. Also creating from scratch is not working.

But thank you for helping out! C

  @Honkman 

What router do you have, version and firmware, and what version of Omada controller do you have?

  @MR.S Latest version of Omada. 6.1.0.19
I tried in the config: ER8411 (the one that I have) and ER7070.

C

  @Honkman 

ok, I have an ER8411 too but it has a dynamic public IP so I can't test it with it, but I did a test with an ER605v2 here which has a private IP, it went fine without any errors.

  @MR.S I have not yet adoped the device to my Omada. Just tried to configure it by selecting that device for the "Internet" settings.

I now tried to create a new site. Same issue.

Running out of ideas. Anhow. No Omada gateways for me then. That's sh .... as this is the last issue I have to fix to get rid of my Fortigates.

BR
C

  @Honkman 

It seems strange, I have no problems so there must be something wrong with your setup. Ask Omada support to look into it
maybe @NeilR_M  can help you on the right track.

  @Honkman I also tested on a new test organization and it worked fine...Just to confirm your process, you added the WAN IP Aliases, and then created the port forwarding rules? Can you send a screenshot of your WAN configuration, censoring any specific public IP details and such? 

  @NeilR_M 

1. Created a new site
2. Enabled WAN Override
3. Selected ER8411
4. WAN POrt: WAN1
5. Static IP
6. 10.1.1.100, 255.255.255.0, 10.1.1.1
7. Two alias: 10.1.1.101 and 10.100.1.102
8. NAT
9. Added one rule for Port 443

C

  @Honkman I see. I was replicating your setup and actually managed to recreate the issue...but only because I was trying to do it via WAN Overrides before adopting the device. I can confirm that once you actually adopt the router, it will allow you to do the port forwarding as you wish.



I'll see if I can find out exactly why this is the case, but go ahead and try it after adopting the gateway.