Re: AXE11000 RBSE960 System receives 400 Bad Request while appying static IP address
When I added reservations for my RBSs so I always knew there they were IP-wise, in my range of 192.168.1.2-150, I made them 148 and 149. There was no conflict with anything else. And, I noticed it was not immediate but they did eventually get moved to those IP addresses.
When I added reservations for my RBSs so I always knew there they were IP-wise, in my range of 192.168.1.2-150, I made them 148 and 149. There was no conflict with anything else. And, I noticed it was not immediate but they did eventually get moved to those IP addresses.
Patience is indeed a virtue, but one I struggle with. It's a computer. Things should happen NOW!
Re: AXE11000 RBSE960 System receives 400 Bad Request while appying static IP address
For some devices that you set IP address reservations for on the RBR, after you hit apply and the RBR does it's thing, these device may not sense the change or auto update, thus a power cycle or reboot will be needed to update there IP address tables.
So outside the 400 error which I think I can manage by not trying to assign an address reservation to a MAC which is already in use through DHCP. How can I get a device to use a new address reservation (excuse me if I sometime say static IP. I've meant a DHCP reservation through this entire thread)? I have a camera on ...1.41 that I want to move to ....1.200. When I hit APPLY, it is still on 1.41. If I reboot the modem, it is still on 1.41. I know it isn't a browser cache issue since I can access the camera on 1.41.
Any idea - perhaps I am missing something basic. This will help my debugging because I need to move/reassign devices to make room for the DHCP reservations.
Re: AXE11000 RBSE960 System receives 400 Bad Request while appying static IP address
I was thinking about this last night and concluded the same as what you said. The ARP cache remains between some operations. I was also thinking I could disable a device that is on an address I need, and then re-enable it. Hopefully the disable is by MAC, not IP. A Power Failure would help, but a software "Flush/Disconnect/Allow device to re-establish connection" would be nice. A short bounce in the network can happen during certain times of the week.
