ipv6 addresses in dhcpd.conf

Bug #2027621 reported by Jorge Merlino
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Status tracked in 3.5
3.0
Fix Committed
Medium
Jorge Merlino
3.1
Fix Committed
Medium
Jorge Merlino
3.2
Fix Released
Medium
Jorge Merlino
3.3
Fix Committed
High
Jacopo Rota
3.4
Fix Released
High
Jacopo Rota
3.5
Fix Committed
High
Jacopo Rota

Bug Description

This issue occurs in HA installations, when there are ipv6 and ipv4 addresses configured in the same interface and the same VLAN where DHCP is enabled. Sometimes ipv6 addresses are used in the address and peer address parameters on the failover DHCP configuration on dhcpd.conf.

It seems that MAAS does not check the type of the ip addresses when building the failover configuration in the make_failover_peer_config method on dhcpd.conf.

I'm using snap version 3.2.8-12050-g.fc2c8d020.

Example:

- Secondary DHCP node:

#
# Failover Peers
#
failover peer "failover-vlan-5001" {
  secondary;
  address 192.168.133.6;
  peer address 2001:1890:f804:5f05:e643:4bff:fea6:8aa7;
  max-response-delay 60;
  max-unacked-updates 10;
  load balance max seconds 3;
}

- Primary DHCP node:

#
# Failover Peers
#
failover peer "failover-vlan-5001" {
  primary;
  address 2001:1890:f804:5f05:e643:4bff:fea6:8aa7;
  peer address 192.168.133.6;
  max-response-delay 60;
  max-unacked-updates 10;
  load balance max seconds 3;
  mclt 3600;
  split 255;
}

Tags: sts

Related branches

tags: added: sts
Jacopo Rota (r00ta)
Changed in maas:
assignee: nobody → Jacopo Rota (r00ta)
milestone: none → 3.4.0
Jacopo Rota (r00ta)
Changed in maas:
importance: Undecided → High
status: New → Triaged
status: Triaged → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.