Project

General

Profile

Bug #6218

input validation should prevent v6 aliases with v4 CARP parent and vice versa

Added by Chris Buechler about 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Category:
Virtual IPs
Target version:
Start date:
04/20/2016
Due date:
% Done:

0%

Estimated time:
Affected Version:
All
Affected Architecture:

Description

It's not possible to configure an IP alias with a CARP parent where one is IPv6 and the other is IPv4. Input validation should prevent such configurations.

Associated revisions

Revision 58b33af6 (diff)
Added by Chris Buechler about 3 years ago

Add validation of address family on IP aliases with CARP parent. Ticket #6218

Revision c0358d44 (diff)
Added by Chris Buechler about 3 years ago

Add validation of address family on IP aliases with CARP parent. Ticket #6218

History

#1 Updated by Chris Buechler about 3 years ago

  • Status changed from Confirmed to Feedback

fix pushed

#2 Updated by Chris Buechler about 3 years ago

  • Status changed from Feedback to Resolved

works

Also available in: Atom PDF