Omada unable to route TCP and UDP traffic independently in port forwarding rules?
I'm getting the following error in software controller 6.1.0.19 trying to configure my gateway (ER707-m2) with port forwarding:
"Cannot create a port forwarding rule with the same Interface, Source Port, and WAN IP as an existing one. Please modify."
I'm trying to setup two port forwarding rules:
Any -> 192.168.1.2 on TCP 443
Any -> 192.168.1.3 on UDP 443
It appears if the Omada controller sees both rules as conflicting because they share the same source (external) port 443 and WAN interface/IP, even though the protocols differ.
Is this expected behaviour?
Please help!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @WillOmada
You can use different ports for omada gateway management in standalone mode.
We cannot guarantee if this would be added to the Controller mode, while we would like to escalate your feedback and request to the department in charge of this.
- Copy Link
- Report Inappropriate Content
I don't know if it's expected, but I tested it myself and it's not possible to configure it as you describe.
- Copy Link
- Report Inappropriate Content
And for clarity, I see the above behaviour as a bug.
I.e. that it interprets the above setup as a conflict, ignoring that the two rules are on different protocols. Different processes can listen to the same port as long as it's a different protocol, and indeed in the rule setup it asks you which protocol you'd like to forward: TCP, UDP, or both.
- Copy Link
- Report Inappropriate Content
Hi @WillOmada
Currently, the same port number even with different protocols would be unable to be configured properly on the same WAN interface. So it is recommended that you could try to assign different port numbers for different services.
- Copy Link
- Report Inappropriate Content
It works fine in standalone mode, so why not in controller mode?
- Copy Link
- Report Inappropriate Content
Is this likely to be fixed, ie is it recognised as a bug?
For my use case it's impossible to use a different port as it's for port 443.
- Copy Link
- Report Inappropriate Content
Hi @WillOmada
You can use different ports for omada gateway management in standalone mode.
We cannot guarantee if this would be added to the Controller mode, while we would like to escalate your feedback and request to the department in charge of this.
- Copy Link
- Report Inappropriate Content
I checked policy routing but that is a bit convoluted way to do it.
but this does need to be fixed.
basically you open port to subnets then use policy routing to route the port.
you'll need to make groups for udp443 and tcp443 then hosta hostb.
then create the policy route using the groups made.
it is very convoluted and needs further testing.
but this may be a work around until tp-link corrects this bug.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 421
Replies: 7
Voters 1