Sadly, it does not matter which port sram99 is attempting to forward, as the error message being received is the same as the rest of us and the same error on every and any port forwarding attempt. PORT FORWARDING DOES NOT WORK on this modem, at least not currently. It might have worked int he past but not now.
I set up a Nextcloud server which is connected to another router that's connected to the Ignite router, and I can't access it now because port-forwarding stopped working. In ignitewifi.rogers.com, the IP address of the TP-Link router is in 10.0.0.x, but it should be a static IP of 192.168.0.x.
Setting a "reserved IP address" doesn't work either because it will only let you do it within the range the DHCP.
Please fix this.
What is Rogers thinking?!
Keep in mind, this is a Comcast system, not a Rogers system, although, no doubt there are changes to accommodate Rogers, and Shaw and any other ISP who signs up to use this system. The drawback, Comcast is in control. If another ISP makes a request, they might see the requested changes if its useful to Comcast, just speculating here. So, even if Rogers forwards your request to Comcast, who knows if that request will ever see the light of day.
9 months later, this issue is not resolved. Rogers should be ashamed of their service and support. For anyone but the most basic user, this is a problem. In this day and age, port forwarding is a very common NEED, not some nice-to-have feature. My term is up in June and I will be taking a hard look at my options. 25 year Rogers customer.
Keep in mind, this is a licenced system from Comcast. With that type of arrangement, there is always the danger and reality that bug fixes or possible enhancements requested by the licencees will be cast aside. If Comcast found any use in bug fixes or enhancements, then they would probably occur. If not, well, here you are, several months later. That's the reality of not running your own show.
Rogers Ignite Internet restore old Port Forward gui to interface provided by default gateway.
I was wondering if it's possible to restore the option to configure port forwarding using the gui provided by the default gateway address. Right now it's only possible to be configured by using my Ignite profile. Although I am willing to do so, the new method of selecting a specific device has made port forwarding more difficult than convenient for me as the specific linux server I wish to port forward isn't recognized as a device on my ignite profile.
Thank you in advance for suggestions!
To be more clear, I would rather specify an IP address than to select a device.
I have tried both using the settings directly on the modem and by using both the ignite website and app. I wish to open port 25565/tcp for my local address 10.0.0.30. However because Ignite requires a user to select a device rather than a specific IP I am having issues with port forwarding. The device I want to use isn't shown in the Ignite menu despite showing up as connected in my modem settings.
@Smiley1 @-G- can probably confirm this. When you use the app or online controls (there is an online control capability correct ?), you lose control over certain functions directly thru the modem. If you run a factory reset and never use the app or online control, you should then have full access to all of the functions shown in the modem's UI. That's probably the quickest way to resolve the problem. Just have to be prepared to set the modem up from scratch.