Port forwarding issue HUB 5

[urgiv]

Greetings to the esteemed community,

I seek your expertise regarding a technical matter concerning port forwarding on the HUB 5 device. Within my local area network (LAN), I possess multiple "smart devices" that can be accessed and controlled locally through a web browser interface by inputting their respective IP addresses, such as 192.168.0.10, 192.168.0.11, and so on. These devices utilize local port 80 (HTTP) for communication.

However, I am facing a challenge in configuring these devices to be accessible from external locations.
While I have successfully established port forwarding for only one device with the configuration
WAN IP - 86.xxx.xxx.73:190 -> Port forward to -> 192.168.0.10:80,
Subsequent attempts to set up additional rules encounter a conflict within the router due to port 80 being already in use. example WAN IP - 86.xxx.xxx.73:191 -> Port forward to -> 192.168.0.11:80,

I kindly request your assistance in understanding this issue and providing a simplified explanation of the underlying technical concepts. Your expertise in this matter would be greatly appreciated.

Thank you for your attention to this inquiry experts 😉

[Client62]

Do your smart devices allow you to specify unique Remote Management Port numbers ?

[urgiv]

 I dont think - most of them are ESP12

[pete_at_home]

Just checked my Hub5, and it certainly does detect the port 80 destination as clashing, even though the internal IP addresses are different.   i.e. it doesn't work.   Short sighted implimentation by Sagem if you ask me.

My PfSense firewall lets me do it, as do most NAT Gateways.

Also the VM Hub4 allows it, but the firmware for these was originally written by Motorola-Arris

[legacy1]

So you need your own router

[urgiv]

maybe FW is faulty and VM need to sort out?

[Roger_Gooner]

Are these old devices as most smart devices now use cloud-based control, so obviating the need to assign fixed ip addresses. All you have to do is set them up and control them via a phone app.

[urgiv]

Not my own made ESP12 😉

[Client62]

If you are waiting for VM to come with a solution, please don't !  

It would be amazing if a forum Mod grasped the limitation encountered, let alone logged it as a fault to fix.

Crack on and start thinking about Hub 5 in Modem mode and a 3rd party router where you can apply your port forwarding settings and expect it to work.  Time to take back control.

[legacy1]

VM don't believe people need port forwarding they don't support it either.

The fault is VM doing router mode and think they can do a safer router mode then 3rd party can not saying thats a lie it is likely there goal they see port forwarding a unnecessary risk but of course they had to add it but that does not mean it works the same way like NAT loopback, source IP NAT external port to other internal port and so on.