@Clive_A - no I'm using a full Festa system. FR365 gateway, 3x FS308GP switches and 2x F65 APs.

I understand that the IP addresses come from the router and I erroneously referred to rebooting the switch. The location that the Fixed IP is set in the Festa Cloud Controller is in the client settings.

My point was that once the Fixed IP is set, rebooting the client triggers the router to issue a new IP address, not the fixed one. Surely this should work in the Festa ecosystem?

  @Mr_Orange 

Mr_Orange wrote

  @Clive_A - no I'm using a full Festa system. FR365 gateway, 3x FS308GP switches and 2x F65 APs.

 

I understand that the IP addresses come from the router amd I erroneously referred to rebooting the switch. The location that the Fixed IP is set in the Festa Cloud Controller is in the client settings.

 

My point was that once the Fixed IP is set, rebooting the client triggers the router to issue a new IP address, not the fixed one. Surely this should work in the Festa ecosystem?

Go to the DHCP reservation page and check if there is a rule that matches what you configured in the picture. If it's there and the status is enabled, the DHCP should assign the proper IP to the device that has this MAC address. 

Clive_A wrote

  @Mr_Orange 

Mr_Orange wrote

  @Clive_A - no I'm using a full Festa system. FR365 gateway, 3x FS308GP switches and 2x F65 APs.

 

I understand that the IP addresses come from the router amd I erroneously referred to rebooting the switch. The location that the Fixed IP is set in the Festa Cloud Controller is in the client settings.

 

My point was that once the Fixed IP is set, rebooting the client triggers the router to issue a new IP address, not the fixed one. Surely this should work in the Festa ecosystem?

Go to the DHCP reservation page and check if there is a rule that matches what you configured in the picture. If it's there and the status is enabled, the DHCP should assign the proper IP to the device that has this MAC address. 

  @Clive_A - there isn't an overview DHCP reservation page. The Fixed IP is set in the Client settings:

Despite the Festa FR365 being hardware identical to one of the Omada gateways, the firmware is different and the Festa Cloud Controller does not expose the same level of settings as Omada.

The point is that rebooting the client shouldn't cause the gateway to assign a new IP when a Fixed IP has been assigned. This is a bug, as far as I am concerned.

  @Mr_Orange 

Mr_Orange wrote

Clive_A wrote

  @Mr_Orange 

Mr_Orange wrote

  @Clive_A - no I'm using a full Festa system. FR365 gateway, 3x FS308GP switches and 2x F65 APs.

 

I understand that the IP addresses come from the router amd I erroneously referred to rebooting the switch. The location that the Fixed IP is set in the Festa Cloud Controller is in the client settings.

 

My point was that once the Fixed IP is set, rebooting the client triggers the router to issue a new IP address, not the fixed one. Surely this should work in the Festa ecosystem?

Go to the DHCP reservation page and check if there is a rule that matches what you configured in the picture. If it's there and the status is enabled, the DHCP should assign the proper IP to the device that has this MAC address. 

  @Clive_A - there isn't an overview DHCP reservation page. The Fixed IP is set in the Client settings:

 

 

Despite the Festa FR365 being hardware identical to one of the Omada gateways, the firmware is different and the Festa Cloud Controller does not expose the same level of settings as Omada.

 

The point is that rebooting the client shouldn't cause the gateway to assign a new IP when a Fixed IP has been assigned. This is a bug, as far as I am concerned.

I could use this information:

• Firmware of the FR365. 
• Festa controller version. 
• When you set the fixed IP, please provide a screenshot of the IP you set.
• And go to the NAS, reboot it and screenshot its network parameters. What's the IP reading? And what IP mode is it?
• Is it directly connected to the router? If no, make a direct connection and use the steps above. 

Clive_A wrote

  @Mr_Orange 

Mr_Orange wrote

Clive_A wrote

  @Mr_Orange 

Mr_Orange wrote

  @Clive_A - no I'm using a full Festa system. FR365 gateway, 3x FS308GP switches and 2x F65 APs.

 

I understand that the IP addresses come from the router amd I erroneously referred to rebooting the switch. The location that the Fixed IP is set in the Festa Cloud Controller is in the client settings.

 

My point was that once the Fixed IP is set, rebooting the client triggers the router to issue a new IP address, not the fixed one. Surely this should work in the Festa ecosystem?

Go to the DHCP reservation page and check if there is a rule that matches what you configured in the picture. If it's there and the status is enabled, the DHCP should assign the proper IP to the device that has this MAC address. 

  @Clive_A - there isn't an overview DHCP reservation page. The Fixed IP is set in the Client settings:

 

 

Despite the Festa FR365 being hardware identical to one of the Omada gateways, the firmware is different and the Festa Cloud Controller does not expose the same level of settings as Omada.

 

The point is that rebooting the client shouldn't cause the gateway to assign a new IP when a Fixed IP has been assigned. This is a bug, as far as I am concerned.

I could use this information:

• Firmware of the FR365. 
• Festa controller version. 
• When you set the fixed IP, please provide a screenshot of the IP you set.
• And go to the NAS, reboot it and screenshot its network parameters. What's the IP reading? And what IP mode is it?
• Is it directly connected to the router? If no, make a direct connection and use the steps above. 

  @Clive_A 

This is happening to multiple devices, including those that do not get rebooted, such as a Logitech Harmony Remote Hub, my AV processor (which just goes into standby). There are others. These clients all need fixed IP addresses as they are all integrated with my home automation server (Home Assistant) which also needs a fixed IP address.

No clients are directly connected to the router. They are connected via FS308GP switches, which are connected to the router. For completeness, the switch details are:

The NAS is set to DHCP:

I could set it to fixed but this is not an option for other clients so isn't a true fix.

The NAS is currently configured with the following "fixed" IP:

This reflects the most recent IP address assigned by the DHCP server which is different from the previously assigned address as shown in post #1.

I really don't want to have to reboot it as I will have to go through a whole discovery and set up process with the Squeezebox clients that are connected to the server that runs on the NAS.

Honestly, every other router that I have used, that offered fixed IP address functionality, just worked. This is a total fail by TP-Link at this point in time with a premium range of networking hardware.

  @Mr_Orange 

Mr_Orange wrote

Clive_A wrote

  @Mr_Orange 

Mr_Orange wrote

Clive_A wrote

  @Mr_Orange 

Mr_Orange wrote

  @Clive_A - no I'm using a full Festa system. FR365 gateway, 3x FS308GP switches and 2x F65 APs.

 

I understand that the IP addresses come from the router amd I erroneously referred to rebooting the switch. The location that the Fixed IP is set in the Festa Cloud Controller is in the client settings.

 

My point was that once the Fixed IP is set, rebooting the client triggers the router to issue a new IP address, not the fixed one. Surely this should work in the Festa ecosystem?

Go to the DHCP reservation page and check if there is a rule that matches what you configured in the picture. If it's there and the status is enabled, the DHCP should assign the proper IP to the device that has this MAC address. 

  @Clive_A - there isn't an overview DHCP reservation page. The Fixed IP is set in the Client settings:

 

 

Despite the Festa FR365 being hardware identical to one of the Omada gateways, the firmware is different and the Festa Cloud Controller does not expose the same level of settings as Omada.

 

The point is that rebooting the client shouldn't cause the gateway to assign a new IP when a Fixed IP has been assigned. This is a bug, as far as I am concerned.

I could use this information:

• Firmware of the FR365. 
• Festa controller version. 
• When you set the fixed IP, please provide a screenshot of the IP you set.
• And go to the NAS, reboot it and screenshot its network parameters. What's the IP reading? And what IP mode is it?
• Is it directly connected to the router? If no, make a direct connection and use the steps above. 

  @Clive_A 

 

 

This is happening to multiple devices, including those that do not get rebooted, such as a Logitech Harmony Remote Hub, my AV processor (which just goes into standby). There are others. These clients all need fixed IP addresses as they are all integrated with my home automation server (Home Assistant) which also needs a fixed IP address.

 

No clients are directly connected to the router. They are connected via FS308GP switches, which are connected to the router. For completeness, the switch details are:

 

 

The NAS is set to DHCP:

 

 

I could set it to fixed but this is not an option for other clients so isn't a true fix.

 

The NAS is currently configured with the following "fixed" IP:

 

 

This reflects the most recent IP address assigned by the DHCP server which is different from the previously assigned address as shown in post #1.

 

I really don't want to have to reboot it as I will have to go through a whole discovery and set up process with the Squeezebox clients that are connected to the server that runs on the NAS.

 

Honestly, every other router that I have used, that offered fixed IP address functionality, just worked. This is a total fail by TP-Link at this point in time with a premium range of networking hardware.

You don't have to reboot the router. But you need to reboot the clients so they request the new IP address from the DHCP server.

I am not sure what you mean by now as you showed a picture that fits the expectation of the Fixed IP thing.

Not sure your definition of true fix either. Anything, if they have previously got an IP from the DHCP server, they'll wait for the next renew or request to get a new IP if you have set an IP to it but it does not instantly change. This is expected for anything using the DHCP service unless it restarts the DHCP service individually. 

So, while the players, speakers, and hubs are connected to the WIFI and getting an IP, you set the fixed IP and reboot these devices and let them refresh their IP address. 

As for the controller, the sync could delay. Check the devices, they should get the new IP after the reboot. 

And, your firmware can be upgraded: https://www.tp-link.com/en/support/download/festa-fr365/#Firmware

Not sure why you did not upgrade it to the latest as the controller can check the firmware online. 

Clive_A wrote

  @Mr_Orange 

Mr_Orange wrote

Clive_A wrote

  @Mr_Orange 

Mr_Orange wrote

Clive_A wrote

  @Mr_Orange 

Mr_Orange wrote

  @Clive_A - no I'm using a full Festa system. FR365 gateway, 3x FS308GP switches and 2x F65 APs.

 

I understand that the IP addresses come from the router amd I erroneously referred to rebooting the switch. The location that the Fixed IP is set in the Festa Cloud Controller is in the client settings.

 

My point was that once the Fixed IP is set, rebooting the client triggers the router to issue a new IP address, not the fixed one. Surely this should work in the Festa ecosystem?

Go to the DHCP reservation page and check if there is a rule that matches what you configured in the picture. If it's there and the status is enabled, the DHCP should assign the proper IP to the device that has this MAC address. 

  @Clive_A - there isn't an overview DHCP reservation page. The Fixed IP is set in the Client settings:

 

 

Despite the Festa FR365 being hardware identical to one of the Omada gateways, the firmware is different and the Festa Cloud Controller does not expose the same level of settings as Omada.

 

The point is that rebooting the client shouldn't cause the gateway to assign a new IP when a Fixed IP has been assigned. This is a bug, as far as I am concerned.

I could use this information:

• Firmware of the FR365. 
• Festa controller version. 
• When you set the fixed IP, please provide a screenshot of the IP you set.
• And go to the NAS, reboot it and screenshot its network parameters. What's the IP reading? And what IP mode is it?
• Is it directly connected to the router? If no, make a direct connection and use the steps above. 

  @Clive_A 

 

 

This is happening to multiple devices, including those that do not get rebooted, such as a Logitech Harmony Remote Hub, my AV processor (which just goes into standby). There are others. These clients all need fixed IP addresses as they are all integrated with my home automation server (Home Assistant) which also needs a fixed IP address.

 

No clients are directly connected to the router. They are connected via FS308GP switches, which are connected to the router. For completeness, the switch details are:

 

 

The NAS is set to DHCP:

 

 

I could set it to fixed but this is not an option for other clients so isn't a true fix.

 

The NAS is currently configured with the following "fixed" IP:

 

 

This reflects the most recent IP address assigned by the DHCP server which is different from the previously assigned address as shown in post #1.

 

I really don't want to have to reboot it as I will have to go through a whole discovery and set up process with the Squeezebox clients that are connected to the server that runs on the NAS.

 

Honestly, every other router that I have used, that offered fixed IP address functionality, just worked. This is a total fail by TP-Link at this point in time with a premium range of networking hardware.

You don't have to reboot the router. But you need to reboot the clients so they request the new IP address from the DHCP server.

I am not sure what you mean by now as you showed a picture that fits the expectation of the Fixed IP thing.

 

Not sure your definition of true fix either. Anything, if they have previously got an IP from the DHCP server, they'll wait for the next renew or request to get a new IP if you have set an IP to it but it does not instantly change. This is expected for anything using the DHCP service unless it restarts the DHCP service individually. 

So, while the players, speakers, and hubs are connected to the WIFI and getting an IP, you set the fixed IP and reboot these devices and let them refresh their IP address. 

As for the controller, the sync could delay. Check the devices, they should get the new IP after the reboot. 

 

And, your firmware can be upgraded: https://www.tp-link.com/en/support/download/festa-fr365/#Firmware

Not sure why you did not upgrade it to the latest as the controller can check the firmware online. 

  @Clive_A 

The fixed IP matches the assigned IP because I changed the fixed IP to match the one assigned since the router is ignoring the fact that I specified a fixed IP.

Any request or renew, where a fixed IP has been specified, should result in the fixed address being issued or renewed.

The Cloud Controller obviously isn't working wrt firmware upgrades then because I have clicked the check update button a few times and nothing has come up.

I'll start with the firmware upgrade and see how this issue behaves after that. Maybe it has already been fixed.

Also, I am in Australia and the support page for the FR365 on the regional site does not show any firmware upgrade: Festa FR365 Support - AU.

Are you sure that I can use the firmware from the page that you linked to? I don't want to brick my router!

  @Mr_Orange 

Mr_Orange wrote

Also, I am in Australia and the support page for the FR365 on the regional site does not show any firmware upgrade: Festa FR365 Support - AU.

 

Are you sure that I can use the firmware from the page that you linked to? I don't want to brick my router!

Label of the router. I need to read the model number so I know if that firmware is good for you or not.