-
Notifications
You must be signed in to change notification settings - Fork 38
Description
Please prefix your issue title with one of the following: [BUG], [ISSUE], [FEATURE REQUEST], [MODULE REQUEST], [OTHER].
Replace everything between stars with current version of your facileManager and module installations:
fM Version : v3.5.7
fmDHCP Version : 0.4.4
In raising this issue, I confirm the following (please check boxes, eg [X]):
- I have read and understood the contributors guide.
- I have checked that the bug-fix I am reporting can be replicated, or that the feature I am suggesting isn't already present.
- I have checked that the issue I'm posting isn't already reported.
- I have checked that the issue I'm posting isn't already solved and no duplicates exist in closed issues and opened issues
- I have checked the pull requests tab for existing solutions/implementations to my issue/suggestion.
(BUG | ISSUE) Expected Behavior:
(a) Select an existing and enabled failover peer (called "") on the "Pools Edit Config" of a pool
(b) Press "Save"
(c) Reopen "Pools Edit Config" of the same pool
=>
(I) The previously selected failover peer "" should be shown in the Drop-Down Box "Failover Peer"
(II) In the generated DHCP configfile the pool section of the mentioned pool should contain the line "failover peer ;"
pool {
failover peer ;
range 192.168.128.180 192.168.128.199;
default-lease-time 3600;
max-lease-time 86400;
allow unknown-clients;
}
(BUG | ISSUE) Actual Behavior:
(I) Drop-Down Box is empty
(II) line "failover peer ""; is missing in generated configfile
pool {
range 192.168.128.180 192.168.128.199;
default-lease-time 3600;
max-lease-time 86400;
allow unknown-clients;
}
(BUG | ISSUE) Steps to reproduce:
(a) Select an existing and enabled failover peer (called "") on the "Pools Edit Config" of a pool
(b) Press "Save"
(c) Reopen "Pools Edit Config" of the same pool