Hi @Tyra 

ER605 V1 1.3.0 port forward. V5.9.31 Software Controller.

On another site, I have an ER605 V2. WAN 192.168.2.10, Controller is V5.9.31. I use a computer from this ER605 V2 and access the port forwarding on first site.

Wireshark shows port forwarding works.

Got zipped when I transferred it from the test PC. But still shows the point.

  @Clive_A 

Hi Clive, I appreciate the reply!

As soon as I take the ER605 off the controller, the exact same port forwarding works perfectly when it is configured standalone.

This is 100% repeatable, every single time I get the same result.

I have tried multiple different ports using netcat to listen for input, perfect responses internally and externally when the router is on standalone mode, no external access at all when adopted by the controller. I have tried putting the server temporarily in the DMZ, no results when adopted, perfect results in standalone.Switching the forward from TCP to all also has no effect, and again the forward works as TCP only on standalone mode.

Any further ideas would be hugely appreciated.

Hi @Tyra 

Thanks for posting in our business forum.

I tested it locally with my Plex. Nothing wrong with it. Computer hosted that hosts Plex isn't off power. I suggest you check if your Plex is logged in on the computer that hosts the server. And don't close the window of the log-in.

  @Clive_A 

Hi Clive,

Thanks again for this.

I have tested with Plex, from multiple devices, alongside a number of other services such as listening for access with netcat and spinning up a quick webserver.

When adopted, I cannot access any of these services at all (from an external device, internal access works perfectly).

When I un-adopt the router and set up the exact same port forwards all services work perfectly internally and externally.

All the best,

Tom

Hi @Tyra 

Thanks for posting in our business forum.

Tyra wrote

I have an ER605, along with a few other Omada devices, all handled by a software controller running on an ubuntu server (Controller v5.9.31).

 

When I set port forwarding rules on my Omada controller, they have no effect. Nothing can get through and my services remain inaccessible.

 

When it is in standalone mode, the exact same port forwarding rules configured on the router work perfectly.

 

Adopt the ER605 again, and everything stops working.

 

The exact same setting tried for multiple ports including (for testing) putting the server in the DMZ, the router will not do it when it has been adopted by the controller, and it all works perfectly when in standalone mode.

 

Would love any assistance people can offer here. I found a few people having had the same issue in the past but no concrete solution.

I had posted this in the wrong place before, hopefully this helps.

Have you verified that if your LAN IP changed after the adoption?

Since the Plex server is using 127.0.0.1:32400, I suspect that your LAN IP changed after the adoption. Is your Plex server on 192.168.0.1/24, the default LAN?

(127.0.0.0 = localhost = the IP of the computer)

  @Clive_A 

Hi Clive,

I am not on my home network right now, please hold on and I will get that tested to be sure.

I don't believe this can be the case as I have the server set up with a static internal IP so it should not be changing no matter what, but best to confirm this 100% before I get back to you.

All the best