Home

Forums

Stories

Knowledge Base

Business Community > Gateways > Omada unable to route TCP and UDP traffic independently in port forwarding rules?

< Gateways

Omada unable to route TCP and UDP traffic independently in port forwarding rules?

Omada unable to route TCP and UDP traffic independently in port forwarding rules?

Omada unable to route TCP and UDP traffic independently in port forwarding rules?

Yesterday

Posts: 8

Helpful: 2

Solutions: 0

Stories: 0

Registered: 2024-02-15

Omada unable to route TCP and UDP traffic independently in port forwarding rules?

Yesterday

Tags: #Routing #NAT #Controller #Firewall

Model: ER707-M2

Hardware Version: V1

Firmware Version: 1.3.1 Build 20251009 Rel.67687

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!

1

1

#1

2 Reply

LV6

12 hours ago

Posts: 3138

Helpful: 1106

Solutions: 451

Stories: 0

Registered: 2018-08-17

Re:Omada unable to route TCP and UDP traffic independently in port forwarding rules?

12 hours ago

I don't know if it's expected, but I tested it myself and it's not possible to configure it as you describe.

1

1

#2

LV1

8 hours ago

Posts: 8

Helpful: 2

Solutions: 0

Stories: 0

Registered: 2024-02-15

Re:Omada unable to route TCP and UDP traffic independently in port forwarding rules?

8 hours ago

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.

1

1

#3