Add static IP address to individual device

Here is my issue. I live in Kansas City.  My 5G gateway assigns an IP for Denver.  All apps I try to use assume I'm in Denver and I can't get local channels, for example, on any streaming service.  I called the t-mobile support and they said that for individuals you don't have a choice, but can get a static IP for a business account.  I'm looking at work arounds to set my 5G gateway to a static IP address within the city in which I live. 

bocaboy2591 wrote:

If you're not knowledgable about TCP/IP, it might be better to print this page and then work with your friend to accomplish what you're trying to do. As I'm sure s/he will tell you, this isn't really hard.

I think the bigger question is why you need to set up a static IP for security cams. I have both Blinks and SimplySafe cams and they both are working just fine with my Arcadyan KVD21 5G Gateway. without static iPs. In addition, they didn't even need to be power-cycled in order to recognize the new gateway and get a new IP address.

Did you set up the T-Mobile gateway with the same WiFi name(s) (SSID) as your old system? If you did, the change-over to T-Mobile should be transparent to the devices on your network.

As an example, if the name of your WiFi network was, say, TomR, you should recreate that name in the T-Mobile app. You may have to power-cycle a device like a camera or smart switch to get a new IP address, but it will automatically find and connect to your T-Mobile gateway, which is now acting as your DHCP server. 

OK, that question just pointed out my lack of knowledge on the subject at hand.

Yes, the T-Mo gateway has the same names and pass codes. And if memory serves me, he NVR did not come online. I had my alarm company restore everything remotely.

Here is what I am seeing.

When my NVR looses power and is restarted, it will not display the camera images. My original configuration is offline. The system will search for an online device but not connect. I must go through the setup again to add it. 

I only assumed it was because the IP address has changed. From here, I will contact the service and have their tech determine why that happens.

Thanks again.

Tom R.

If you're not knowledgable about TCP/IP, it might be better to print this page and then work with your friend to accomplish what you're trying to do. As I'm sure s/he will tell you, this isn't really hard.

I think the bigger question is why you need to set up a static IP for security cams. I have both Blinks and SimplySafe cams and they both are working just fine with my Arcadyan KVD21 5G Gateway. without static iPs. In addition, they didn't even need to be power-cycled in order to recognize the new gateway and get a new IP address.

Did you set up the T-Mobile gateway with the same WiFi name(s) (SSID) as your old system? If you did, the change-over to T-Mobile should be transparent to the devices on your network.

As an example, if the name of your WiFi network was, say, TomR, you should recreate that name in the T-Mobile app. You may have to power-cycle a device like a camera or smart switch to get a new IP address, but it will automatically find and connect to your T-Mobile gateway, which is now acting as your DHCP server. 

Thanks for the replying iTinkeralot and Bocaboy2591.

I guess I am referring to client IP addresses. I am upgrading my security cameras and
alarm system. That causes multiple shutdowns and re-starts, then it will use a different
IP address every time.
This is starting to get complicated! I think I better leave it alone and help. 
I have an IT Guru I could ask to do this, but I want to try it myself. When I have totally
screwed it up, I will call him. For some reason, he encourages my tinkering.

Tom Rhymestine
Miami, Florida

Another way to assign a static address is to configure your client to DHCP and let it pick up an address from the gateway (KVD21). After it successfully connects to the network, note the IP assigned by the gateway and then change the wireless settings on the device to Manual. Enter all the same info you got from the device when it was on DHCP and you will have a static IP.

I agree this is a little bass ackwards but it will work.

As an alternative, you could get software like iNet that will quickly scan your network and tell you the IP and MAC of each device. If your goal is to simply be able to access a device over the network, you could consider leaving the device on DHCP and just identifying it when you need to access it. Just a thought.

If you are referring to local clients you have to do that at each client. The DHCP scope runs, as far as I can determine, from 912.168.12.101 - 192.168.12.254. The gateway IP is 192.168.12.1 so you cannot use that IP address. You can provide static IP addresses to clients from .2 to .100 but should avoid setting static addresses in the DHCP scope. 

If you are referring to the external IP address you have no control over that. With a business account subscribers can request a static IP but I am pretty sure that comes with additional cost. The external public facing IPv4 addresses are shared due to how they 464XLAT is done. T-Mobile has an IPv6 network so there are some limitations as to what is allowed and how things are done.