Problem with allocating a fixed IP address

[#1]

I've looked at this thread 

https://community.plus.net/t5/Tech-Help-Software-Hardware-etc/How-to-allocate-fixed-DHCP-Addresses-i...

but I still cannot get my Hub 2 to allocate a fixed IP address to a device. It keeps reverting back to the value originally allocated by DHCP. I have tried all possible combinations of saving the new value, rebooting the device in question and restarting the Hub 2. No change - I still can't get the IP address I want to set.

Am I missing something?

[#2]

@phil917k 

What is the device that you are trying to fix the IP address for?

Does it have in its Settings the ability to set up a manual IP address as opposed to DHCP?

.

[#3]

@phil917k 

I would say you are not missing anything, the problems you have encountered I have as well. Assigning an IP Address did work but for me it stopped working sometime back.

I have a wireless access point with a built in DHCP server which I now use, this allows me to assign IP Address to a given MAC address.

If the device allows follow @Mr_Paul advice, setup the IP Address manually rather than using the Hub DHCP server.

A point of interest are you using the default IP Address range (192.168.1.0/24) for the Hub or have you changed it to something else?

[#4]

It's for a Raspberry Pi that will be used on a camera system. I believe that I can set up an IP address on the device so i'll give it a try. I've always been able to do it from the router before though and I must have done it before on the Hub 2 as I have a separate Raspberry Pi running a media server that has a fixed IP. It sure as hell doesn't work now though 😞

[#5]

I've set the Hub 2 so that DHCP allocates addresses in the 192.168.1.2-99 range as this replicates behaviour that I had on a previous home network. I do also have a spare modem/router that is presently configured just to act as an access point so I could play around with that too.

[#6]

The reasoning behind my question is, I have changed my Hub two to be 192.168.10.1 and I'm wondering if the issue is caused by the Hubs IP Address and DHCP pool not using the default and that was the cause of the annoyance.

My current DHCP server is running on a TP-Link AX53 configured to be a WAP. 

[#7]

OK, I tried the suggestion from @Mr_Paul and set the Pi to have a fixed IP address. After rebooting it, I was then able to SSH to it using this new address. However, in the device table on the Hub 2 it was still showing as having its previously-allocated-by-DHCP address. It was also unable to contact external networks, possibly because of this IP address conflict? 

I'd still really like to understand why the Hub 2 doesn't correctly set the fixed IP address. Is it a firmware bug or something stupid like that?

[#8]

Are you saying the device is in the list twice with the same MAC address and connected to the same LAN port?

I have encountered  this situation as you occasionally.

This has worked for me changing the LAN port the device is connected to, power if off first and leave it off for a few minutes before switching back on.

The DHCP server on the Hub two is not the best in my opinion maybe  the Hub Two is best suited for the average user with no special requirements.