Actions
Bug #14477
open
Defining IP address on an Interface doesn't check defined VIPs for possible IP address overlapping
Status:
New
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
Affected Architecture:
Description
When attempting to create a VIP (Alias type) with an IP address that has already been defined on the interface, the system performs a check and alerts the user about the IP overlap. However, that's not the case when you define Interface IP overlapping with an existing VIP using the same address. As a consequence, dpinger service won't start.
Steps to reproduce:
1) Define VIP Alias type using the WAN interface as the parent interface with an IP address, e.g., 192.168.33.21.
2) Change the existing WAN interface IP to the address used for creating the Alias (192.168.33.21)
3) Check the gateway status for the WAN interface.
Updated by
Actions