01-06-2023 10:31 PM
I have replaced a PC on my network with a different PC on the same IP address and when I attempt to create port forwarding to go to the new PC it creates it using the MAC address of the old device (despite selecting the new device). This is only a problem because the router uses the MAC address of the connected device to determine if the port forwarding should be activated or not. Ideally it should be possible to create port forwarding rules whether the device is active or not, and it should be similarly possible to make them active irrespective of the MAC address of the connected device. This is a terrible design.
Answered! Go to the Recommended Answer.
01-07-2023 04:07 PM
I found that I had an old entry in the DHCP IP Reservations with the old MAC address and IP address. I had to remove that and replace with a new reservation before I was able to properly create the port forwarding rule. There was no error or warning message, so this is still a bug, but at least I was able to find a working solution for me.
01-07-2023 06:57 AM
The old MAC address should be forgotten after 30 days. Yeah, not ideal.
Either use a different IP address, or factory reset Nest Wifi and set it up from scratch.
01-07-2023 09:39 AM
Thanks for the response. Not ideal is an understatement. This is a significant bug.
01-07-2023 09:40 AM - edited 01-07-2023 09:44 AM
It is, but based on years of history Google won't fix it any time soon. Thus, if you want it solved now, the options I mentioned are likely the easiest way.
01-07-2023 04:07 PM
I found that I had an old entry in the DHCP IP Reservations with the old MAC address and IP address. I had to remove that and replace with a new reservation before I was able to properly create the port forwarding rule. There was no error or warning message, so this is still a bug, but at least I was able to find a working solution for me.
01-07-2023 10:22 PM - edited 01-07-2023 10:23 PM
Nice. I based my reply on that this was not the case, and assumed that Google Home/Nest Wifi had some blocking ghost object. But great that you got it solved. 🙂
01-10-2023 10:25 PM
01-14-2023 04:54 PM
Hi nsimon,
We’d like to check in again in case you have any further questions or concerns. Feel free to reply to this thread and we’ll help you out.
Best,
Abi
01-15-2023 10:23 PM
Hello nsimon,
Just one quick final check in here since activity has slowed down. We'll be locking the thread in the next 24 hours, but if you still need help, I would be happy to keep it open. If there's more we can do, just let me know.
Regards,
Abi