Port Forwarding

[Arekitect]

I am perplexed by the complexity of configuring port forwarding on TG4482A. What used to be a simple task of entering the IP address of the destination device and port range now requires an Ignite app and selecting the device from the dropdown list. Unfortunately, 70% of devices on my network are listed as Offline, including the device I need to configure. All devices use DHCP, some with reservations based on MAC address. Has anyone successfully solved the mystery of devices being listed as offline when they are clearly connected and visible on the network? Changing the IP address and rebooting the gateway don't make a difference. The device may show up for a couple of minutes online before moving to the Offline list again. I saw some posts recommending restoring the gateway to the factory defaults, which is just plain dumb as it erases all custom configurations.

I would like to understand the mechanism behind the device's discovery process to configure the port forwarding.  A 2-minute task shouldn't take days to complete. So frustrating!

***ADDED LABELS***

[Biollw]

Best option: Bridge the Rogers modem/gateway and get/use your own router. Much more control over your requirements.

[Arekitect]

Yes, that would work, but I am already paying for Rogers hardware, and I don't see a point in adding more complexity and cost to my network to address this issue. Rogers needs to live up to their customer service commitment and develop a solution to the problem reported by multiple users.

[Biollw]

It won't add complexity to your network. Matter of fact it, in many cases, simplifies it by allowing you full control/better control over your network topology. Such as port forwarding, assigning status IPs, blocking IPs, etc.

Rogers caters to the lay person, 99.9% of their customer base, not higher skilled network customers like you and me.

Good Luck.

[Arekitect · Accepted solution]

It is essential to mention that switching Rogers modem into bridge mode will disable Ignite WiFi boosting pods and disable Ignite WiFi Hub. It also affects Ignite TV.  So basically, in addition to a firewall, I would also need to buy a new WiFi AP and WiFi extenders to create a proper mesh in the house. However, I as much as I would like better firewall capabilities and more flexibility in managing devices, I will stick with the simple setup. As for my Port Forwarding issues, I used a USB WiFi adapter (in addition to a CAT5 connection) to register the device on the Ignite Hub. I was able to create a Port Forwarding rule immediately using  WiFi IP. Next, I removed the USB WiFI adapter and assigned its IP to the NIC on my device exposed to the Internet. It's a convoluted solution, but it worked. I wish Rogers would address the device discovery issues on Ignite gateway, though.

[Micbeau]

I have the same issue with Port Forwarding, Rogers wifi hub won't do it. I have a wifi6 mesh network with my own router. I would like the Rogers hub to forward specific ports numbers to my router. However easy the setup/ steps seems in the rogers hub, they don't work. (1) pick device, (2) enter port. Done. Doesn't work... you mention to Bridge the Rogers hub, so basically the Rogers hub is simply a pass thru, all traffic is controlled thru my router. If j can get that working, that would be great. Any instructions?

[Arekitect]

 I am unsure what you are trying to accomplish by forwarding ports to the router. If you configure our Ignite Gateway into the Bridge mode,  you can control all port forwarding on your router. Keep in mind that the change will disable Wi-Fi on the Ignite Gateway and may affect Ignite TV service.  If you want to make the change, simply navigate to  Gateway > At a Glance page and enable Bridge Mode. However, to turn off the Bridge Mode if something goes wrong you will have to call Rogers Support.

[Arekitect]

I need to reply to my complaint about port forwarding. A technician performed a factory rest on my modem. Despite his assurances that "the app" saves all custom configurations, all settings were lost, including port forwarding config. When creating a new Port Forwarding rule, the Ignite app only allows selecting a device from a list of the CONNECTED devices. There is no option to enter an IP address manually. All devices I need to configure appear OFFLINE and are unavailable from the drop-down list. I understand that Rogers wanted to create a modern, easy experience with the new Ignite app but you CAN NOT drop usability when developing a new UX. My VoIP phone and security systems are offline because I can't open ports to the internet. It is soooooo frustrating. I don't see anyone who could find a solution to this problem.

Rogers, please listen and fix the app!

[Cerunnnos]

This thread is vindication of my utter absolute frustration with the Ignite system, and the app. It's beyond frustrating.

All of this is apparently possible if you're a business customer.

The thing is this - THIS HAS BEEN possible to configure for decades. And they've removed it for residential customers. It's poor business, and just another example of how out of touch Rogers is with an important section of their consumer base. They don't care. They won't do anything about it because they want us to pay more, period. 

If I could go back to Bell, I would. In a heart beat. Home3000 is a dream to configure.