Port Forwarding 80,443

[LetsFix]

I get an error when trying to forward 80&443 TCP to my NAS. Says the ports are already used by "*". What does this mean? I've not had this issue with any other ISP. How can I get these forwarded?

***EDITED LABELS***

[-G-]

---

@LetsFix wrote:

I get an error when trying to forward 80&443 TCP to my NAS. Says the ports are already used by "*". What does this mean? I've not had this issue with any other ISP. How can I get these forwarded?

---

You are not the only person to report this issue with the Comcast gateways:

https://forums.xfinity.com/conversations/your-home-network/forwarding-port-80443-is-not-working-anym...

https://support.shaw.ca/t5/internet-discussions/port-forwarding-not-working-on-80-or-443/td-p/48644

As for why you are seeing that particular error, I don't know, and I'm not currently in a configuration where I can test or troubleshoot this.  The gateway has services listening on those ports on the internal LAN IP address.  So... perhaps this is a bug... OR... maybe the gateway also has services listening on those ports on the WAN interface as well(?) which is preventing you from forwarding those ports to your own server?

Another possibility is that this is a deliberate attempt (although, on its own, not a very effective way) to prevent you from setting up a web server on standard, well-known ports on a residential Internet service.

[LetsFix]

I've since realized that, for whatever reason, my PS4 Device Name was changed to *. I have port forwards for gaming, which include 80, and 443. I was with Bell before my move, and had no trouble forwarding 80/443 to multiple devices. Is there anything I can do, or is Rogers just a incompatible ISP for the NAS requirements?

[-G-]

---

@LetsFix wrote:

I've since realized that, for whatever reason, my PS4 Device Name was changed to *. I have port forwards for gaming, which include 80, and 443.

---

Ah, okay.  That makes sense.  I thought that you were trying to configure port forwarding for the first time and ran into that error.

I was with Bell before my move, and had no trouble forwarding 80/443 to multiple devices. Is there anything I can do, or is Rogers just a incompatible ISP for the NAS requirements?

---

It's frustrating because port forwarding on the Ignite gateways is pretty simplistic and has some weird bugs.

As far as I know, with the Ignite gateways, port forwarding can only be done to the same port internally.  So, once you forward port 80 (associated with the WAN IP address) to an internal system, you are then kinda stuck if you need to forward to port 80 on another internal host.  Other firewalls will allow you to forward, say, port 8080 (WAN IP address) to port 80 of a different internal system... but not with the Ignite Gateway.

I'll tag @Gdkitty for confirmation and any other suggestions.

[LetsFix]

Can I somehow disable/change the firewall? Thanks for your help so far. 

[-G-]

---

@LetsFix wrote:

Can I somehow disable/change the firewall? Thanks for your help so far. 

---

Unfortunately, if the Ignite Gateway is missing features or functions that you require, your only option is to enable Bridge Mode and use your own router/firewall instead.