Skip to main content

    Support

    Offers

U
user_64b70c
1st Topic
1st Like
1st Reply

Visitor

 • 

2 Messages

Monday, November 15th, 2021 1:44 AM

Closed

Enter ip When port forwarding

This issue is talked about allot online from what I have searched, but for the love of god let me enter an ip instead of selecting a device. I cannot believe they removed that functionality in the first place. I have a couple Linux vms running, and they all show up as generic Linux laptop/pc.... To find their ip I need to get through 3 menus, and when I go to port forward they are still all just called generic Linux laptop/pc and I CANNOT view their ip addresses until after it has been port forwarded. AND AFTER 5 HOURS OF TRYING, I realized that the reason I can't find a device is because, Xfinity Xfi has got it in its head that one of my vms has an ip that it in fact does not(10.0.0.3 instead of 10.0.0.142, Has the correct mac address though). Making port forwarding to that device impossible without changing ITS ip. How did removing a basic feature of a router. and slapping it behind some [Edited: "Language"] api help at all. Supposedly if you turn off the device so it appears offline in Xfi, you can remove it and when it joins back it should have the correct ip address. HOWEVER I turned off the vm 10 minutes ago and it is still appears online (I Tried pinging it, and it does not respond). I am now writing this as I wait for the router to restart. Dumbing down software to the point it does not even work is an impressive amount of justifying your job done by some Xfi dev. 

Question

 • 

Updated 

3 years ago

 • Edited

574

2

user_64b70c

Visitor

 • 

2 Messages

3 years ago

Update: the device is now not appearing at all after an hour..... I hate it here.

0

0

CC_Tony

Retired Employee

 • 

1.4K Messages

3 years ago

@user_64b70c I am sorry to hear that you are having issues with your Port Forwarding. Have you tried logging directly into the router to configure the settings instead of using xFi?

2

0

user_f45cd3

Visitor

 • 

2 Messages

@XfinityTony  Your routers have all of these features completely locked down -- we are FORCED to use the website to configure the router for all but the most basic settings.  

I can confirm user_64b70c's experience and maybe provide a little more guidance.   There is DEFINITELY a bug or issue with the website and/or how it sends instructions to the router.  

I just factory reset my router last night, waited for DHCP to provide MYPCNAME with an IP, 10.0.0.64.  Then I configured Port 1234 to forward to MYPCNAME.  Everything worked great.   Today, DHCP decided it was time to give me a new IP, 10.0.0.12.   Port forwarding no longer works.  Despite the following verbiage taken directly from your documentation found here: https://www.xfinity.com/support/articles/xfi-port-forwarding  

"xFi Port Forwarding & Static IPs
With xFi, you no longer need to set a static IP for devices you wish to port forward. xFi port forwarding relies on the devices getting an IP address from the DHCP. "

When I go back into the port forwarding configuration, it now shows Port 1234 for "No associated device" is forwarding to 10.0.0.64.

So that's the first problem. What makes it even weirder is that while still on the xFi website I can look at device details and it shows MYPCNAME = 10.0.0.12, but when I delete and a new port forward and choose MYPCNAME from the dropdown, it still port fowards to 10.0.0.64 and shows the device as "no associated device."

For grins, I tried port forwarding to another machine and it works no problem.    I've done this twice now with factory resets in between to clear out the bad reference or whatever is FIXATING the port forwarding on the old IP.

3 years ago

0

user_f45cd3

Visitor

 • 

2 Messages

Quick update:  I changed my ip to static ("Preserved" in your website) and then had to wait 24 hours before the website would assign the correct ip to port forwarding.  My guess is that whatever updates the website with the current ip settings from the router only occurs every so often, and it's not nearly often enough.  But overnight seemed to do the trick.   So static IP works (eventually) but the documentation claiming that port fowarding would chase whatever ip you get from DHCP is not working at all.  This is not enough to solve @user_64b70c's problem with the VM's , sorry.

3 years ago

0

forum icon

New to the Community?

Start Here