Another Port Forwarding Gripe

I am also trying to forward port 12601 to IPv4 10.0.0.10. The device is an alarm system with Reserved IP.  I can ping the device and log into it from within the LAN. Device shows as "not connected" even when I am pinging or retrieving data from it on LAN. I disabled Advanced Security so I can get to the Port Forward menu. My device does not appear in the Port-Forward drop-down list. Occasionally, the device shows up as Connected, it is still missing from the drop-down list for port forward. I spent hours on CHAT with Xfinity "experts" and no-one can help. This port was forwarded 2 years ago and worked correctly until I installed xfi pods. Now I cannot configure Port-Forwarding logged into 10.0.0.1 - when I try it send me to "myxfi". The device is connected to ethernet port on Gateway NOT Wi-Fi.  Help. Any ideas?

HOORAY! I found a work-around. Instead of port forward, I put the IPv4 device 10.0.0.10 in DMZ. It should ignore any messages not sent through its one open port.  I tested access from outside the LAN and it worked. No thanks to tech support, however.

I am trying that as well. The whole XfI system is strange and hard to get your head around. I have two internal servers that are used for smartphone household management. Before XfI is was trivial. Now, not so much. I would love to get a technical explanation of what they are doing. It appears that everything is now managed from the site and the gateway management app, although accessible locally, changes things but they don't take. Right now I am concerned about static IPs. IF the central server caches all IPs and assigns names and other things to them, does this mean that all DHCP IPs are now static, since the gateway cannot make its own changes without getting xFi out of sync?

This does NOT mean that DHCP IPs are static. You can reserve an IP by going to 10.0.0.1, log on and Reserve an IP. Usually, an IP won't change if it's connected as the lease time is 1 week. Reserving the IP assures that it does not change. In the DMZ setting you enter the LAN IP address of the device.
The WAN IP, assigned by Xfinity can change, although mine has not changed in years. I use DynDNS to store my WAN IP address for applications that need to access my device remotely.

Normally I would totally agree with you and that is the way that I always set up my previous gateway. However, xFi is a different animal. On Xfinity servers it knows the local DHCP address of every device. If you change it via 10.0.0.1 it will not be reflected on the web management app. I wonder if the sync between the gateway and the web app is bi-directional. If not, any assignment is essentially static on the web, including their port forwarding, since the web does the forwarding and not the gateway.

I wish someone from Xfinity would just explain exactly how the connection between the web and the Gateway works. I think that it is such a change that all of us are doing things that would have worked in the regular gateway days and complaining that they no longer work.

Port forwarding does work when setup on the web app, but right now I cannot get it to forward using my DDNS URL and I must use the explicit outside address of my gateway.

I have run into PORT FORWARDING issues as of last year.  I will tell you what I know so far, as there is little documentation on the new PORT FORWARDING BUG.

Last year we would edit the port forwarding setting directly on the router logging in cusadmin.

Now it will log you into the router but it will direct you to the CLOUD ACCOUNT assigned to the account to edit the PORT FORWARDING settings. There is no way around this, and if the customer does not know their login good luck, call support and get it sorted out.

Now if you are a Business Account you will not have this problem, it seems they only broke the home accounts, so you know how much they respect you as a customer.

The setting on the router will work.   IF YOU REBOOT THE ROUTER (2) TIMES, what kind of voodoo is that?  Now it will work only for a couple of days and then it will fail again and require another site visit and troubleshooting session.

I produce www.coloradowebcam.net with over 100 webcams and many many routers and port forwarding, so I can tell you, this is indeed a problem for any RESEDENTIAL COMCAST CLIENT.  Every site that is Comcast Residential now has this problem, and it has not been fixed in over one year.

My solution for a short-term fix, Reboot router (2) times in a row......

Good Luck.