Port forwarding not working when connected to ethernet backbone access point.

  • Port forwarding works when device (iPad) is connected to the main Alien. When connected to the backbone access point there is no connection (port forwarding). Setup is configured as ethernet backbone. I have tried this both backbone and wireless mesh with the same results, works on main not on backbone router. This is not the mesh kit, this is two separate Alien routers. Had no issues on previous system used.

    I have searched and found no discussions/concerns about port forwarding when connected to the access point. As another note, the port forwarding rule is a device that is also on the LAN port of the access point.

    Any suggestions are welcome. Further details - Blue Iris server using port 8050.


  • @gombash Hi, please contact our support team and attach the support file generated from the app right after or durring the issue.
    Support form - form

  • @UI-AmpliFi
    Thanks for the reply. What are you referring to? support file generated from the app right after or during issue?

  • @gombash Never mind. I think I found it. It's downloading now.

  • @gombash said in Port forwarding not working when connected to ethernet backbone access point.:

    searched and found no discussions/concerns about

    I'm having a very similar problem. Interestingly, port forwarding works with the same setup you mentioned, only when I connect from either outside my network (via cellular) or if I am connected to the wifi of the main alien. I cannot connect via port forwarding if I am connected to the 3rd party access point.

  • Just to say that I also have this issue.

    With the target device connected to a second Router used as a Mesh Point, port forwarding works from outside the network.

    From inside the network it only works with devices connected to the main router.

    I guess it may be some sort of NAT issue.

    I’ve reported this as an issue too.

  • I have the same issue. I have three Alien routers. One is the main and the other two are on ethernet backbone. All three are on the latest software update. How do I fix this?

  • It doesn't work when the access points are not in ethernet backbone mode either.

  • It’s embarrassing that they haven’t fixed this issue yet. Buy the most expensive router and you can’t even fully use its mesh capacity.

  • I would love to know if anyone has tested to see if the long outstanding issue of WiFi Calling inconsistency is related to this issue. I have the WiFi Calling issue and have for well over a year now, and I never thought to ask if everyone was using a mesh setup using Ethernet back-haul. I am wondering if maybe when connecting to the mesh point the UPnP isn't working properly. Any traction on this issue? If it gets fixed, I will retest the WiFi Calling too. Thanks.

  • Same problem here. It's frustrating because I have to disconnect my phone from the mesh in order to use my smart home app when it's connected to the mesh backbone. It works fine when connected to the main router.

  • @Juliano-Teixeira Thank you for your patience! The fix is planned in the roadmap. However, we cannot give any estimates at the moment.

    In a meantime there is a workaround for your issue - avoid using the same Ethernet port for both client and server. The server (port forwarding target) must be connected to a separate Ethernet port on the main router.

  • @UI-AmpliFi I have 2 routers, with the secondary router meshed via wifi, not ethernet. I’m also having port forwarding issues with this setup. Will the ‘fix’ also address my issue? Is there a workaround for me?

Log in to reply