Project

General

Profile

Actions

Bug #5916

closed

General Setup page cannot be saved with blank DNS server slots

Added by Mark Furneaux over 5 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Web Interface
Target version:
Start date:
02/20/2016
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.3
Affected Architecture:
All

Description

If there are 2 or more blank DNS server addresses on the System/General Setup page, saving the page will result in the following error:

The following input errors were detected:
Each configured DNS server must have a unique IP address. Remove the duplicated IP.

The sanitizer doesn't seem to ignore blank fields anymore.

Actions #2

Updated by Phillip Davis over 5 years ago

Now I see that there is an alternative solution already in pull request https://github.com/pfsense/pfsense/pull/2678
Take your pick.

Actions #3

Updated by Phillip Davis over 5 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #4

Updated by Steve Beaver over 5 years ago

  • Status changed from Feedback to Resolved

No harm in applying both.

Actions #5

Updated by Steve Beaver over 5 years ago

  • Status changed from Resolved to Feedback
  • Assignee set to Mark Furneaux
Actions #6

Updated by Mark Furneaux over 5 years ago

Actually there is harm in both. The change in https://github.com/pfsense/pfsense/pull/2680 will cause a crash if all DNS server slots are empty when array_filter() is called. One of the two patches needs to be reverted.

Actions #7

Updated by Mark Furneaux over 5 years ago

On a second look, 2680 will always crash when no servers are populated, so it is the one which must be reverted.

Actions #8

Updated by Steve Beaver over 5 years ago

2680 reverted.

Actions #9

Updated by Mark Furneaux over 5 years ago

Tested in 2.3.b.20160226.1008 and everything looks good. I think this can be closed.

Actions #10

Updated by Chris Buechler over 5 years ago

  • Category set to Web Interface
  • Status changed from Feedback to Resolved
  • Target version set to 2.3

yeah this is all good, thanks! pointy hat to me for not thinking of this use case

Actions

Also available in: Atom PDF