Show Posts
1
General Discussion / Re: Static DHCP lease on VLAN
« on: September 10, 2023, 01:49:08 am »
No, this is a bug!
When I create a static DHCPv4 mapping (ie: 10.10.1.200) for a device on a XXX subnet in the range (10.10.1.100 - 10.10.1.254) I incorrectly get the error "The IP address must lie in the XXX subnet" when I press save.
Work around: If I go to the Interfaces/[XXX] page and just press Save followed by Apply (you may have to do this more than once), I am now able to save the static mapping without an error!
It seems like the static DHCP mapping page is comparing the entered IP to the IP range of the last saved interface, not the one associated with the page. I have two NICs with their own subnet ranges and DHCP assignments. I can only enter static IP mappings for the interface that I last saved and applied.
I noticed that if you go to the Interfaces/Overview page and open both interfaces (in my case, LAN and DMZ), you will see that only the last saved interface will have the "IPv4 address" row. The other interface will be missing it. For this reason, I would assume this bug effects the entire product. Maybe related to the "interfaces_primary_address" function? I have no idea.
Note: This problem seems to randomly occur, as I can't seem to reproduce it right now.
When I create a static DHCPv4 mapping (ie: 10.10.1.200) for a device on a XXX subnet in the range (10.10.1.100 - 10.10.1.254) I incorrectly get the error "The IP address must lie in the XXX subnet" when I press save.
Work around: If I go to the Interfaces/[XXX] page and just press Save followed by Apply (you may have to do this more than once), I am now able to save the static mapping without an error!
It seems like the static DHCP mapping page is comparing the entered IP to the IP range of the last saved interface, not the one associated with the page. I have two NICs with their own subnet ranges and DHCP assignments. I can only enter static IP mappings for the interface that I last saved and applied.
I noticed that if you go to the Interfaces/Overview page and open both interfaces (in my case, LAN and DMZ), you will see that only the last saved interface will have the "IPv4 address" row. The other interface will be missing it. For this reason, I would assume this bug effects the entire product. Maybe related to the "interfaces_primary_address" function? I have no idea.
Note: This problem seems to randomly occur, as I can't seem to reproduce it right now.