summaryrefslogtreecommitdiffstats
path: root/etc/inc/upgrade_config.inc
diff options
context:
space:
mode:
authorChris Buechler <cmb@pfsense.org>2013-06-17 00:32:27 -0500
committerChris Buechler <cmb@pfsense.org>2013-06-17 00:32:27 -0500
commit4cdf35a43378b335390ebe832277b5a8ddf6753b (patch)
treec6e27ef9c3c8120204dac7da53bd1a84638834b3 /etc/inc/upgrade_config.inc
parent9a0a9fc1a85b815481e8a4d9d281d3b845f9f9dc (diff)
downloadpfsense-4cdf35a43378b335390ebe832277b5a8ddf6753b.zip
pfsense-4cdf35a43378b335390ebe832277b5a8ddf6753b.tar.gz
Don't flip the IPv6 allow setting just because people are upgrading. Just upgrading versions shouldn't change this behavior. As much as most of us would like people to start deploying IPv6, the vast majority aren't going to be immediately post-upgrade, and changing this can change the firewall policy behavior by allowing v6 that previously wasn't allowed. Upgrades should never change the firewall behavior like that. At the time it was done, everyone using the 2.1 code base was using it for IPv6, so of course it tripped up quite a few people.
Diffstat (limited to 'etc/inc/upgrade_config.inc')
-rw-r--r--etc/inc/upgrade_config.inc4
1 files changed, 1 insertions, 3 deletions
diff --git a/etc/inc/upgrade_config.inc b/etc/inc/upgrade_config.inc
index da45129..91de2f5 100644
--- a/etc/inc/upgrade_config.inc
+++ b/etc/inc/upgrade_config.inc
@@ -2792,9 +2792,7 @@ function upgrade_080_to_081() {
}
function upgrade_081_to_082() {
- global $config, $g;
- /* enable the allow IPv6 toggle */
- $config['system']['ipv6allow'] = true;
+ /* don't enable the allow IPv6 toggle */
}
function upgrade_082_to_083() {
OpenPOWER on IntegriCloud