My IP Address Changed after Several Years - Why?

[RequestTimedOut]

Hi

Long time customer, however for the past 4-5 years - I've had the same IP Address.  This has been through different router changes by ensuring I used the same Mac address when connecting to the VM hub (which is in modem mode).

A few days ago, my IP Address changed - why?

I've restarted both my hub and router, ensured the mac address is still the same one I've used for years etc.

I do understand that our IP addresses are not fixed, but I checked with another VM user on the street who's IP Address has not been changed.  My old IP was listed for my job as an allowed IP address etc

1. Why did I get a new IP Address?
2 Is there any way to get my previous IP address back

Kindest Regards,

[Client62]

My old IP was listed for my job as an allowed IP address etc

In 30+ years of IT Delivery I have never asked an employee / contractor / supplier for their Public IP address when providing remote access to platforms in the central government or the finance / commercial sector. The reasons are we cannot predict what the Public IP is going to be when at home / on a client site / in a hotel or at an airport etc.

[Tudor]

1) Probably VM did a reconfiguration on the segment or CMTS.

2) No way whatsoever.

Get a URL and use DDDNS.

[RequestTimedOut]

Thank you for your reply, yes and I agree that IP Addresses alone should never be used as the only security measure.

However, in some situations IP Address filtering exists.  Examples over the past few years:

1. SQL Server - IP address needed to be whitelisted before I was even able to attempt to connect
2. Rate Limiting Bypass - eg: Services behind Cloudflare 
3. SSH / SFTP / FTP - Many services are locked behind firewalls which block all ports - unless your IP is 'on the list'

As I said, I completely agree that IP Addresses which may change over time are not a good security choice.. but if used in conjunction with other security measures - are still another form of defence.

It's 

[RequestTimedOut]

Thank you for your response.

My first thing was to check if there were any errors in my hub to see if there was anything about an update (pretty sure nothing would be listed there anyway)

Do these kind of messages appear to give the impression there was "reconfiguration on the segment or CMTS"

```
10/09/2023 22:46:22 critical No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;

10/09/2023 16:23:18 notice LAN login Success;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;

10/09/2023 16:23:12 Warning! LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;

10/09/2023 06:48:13 critical No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;

09/09/2023 15:24:53 notice DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;

09/09/2023 15:24:53 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;

08/09/2023 12:31:35 critical No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;

07/09/2023 17:09:46 notice LAN login Success;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;

07/09/2023 17:09:27 Warning! LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;

04/09/2023 13:22:17 notice DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;

04/09/2023 13:22:17 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;

02/09/2023 10:42:25 critical No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;

01/09/2023 01:22:17 notice DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
```
😕