| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| | |
This is a merge of pfSense/master at this point:
c0d5c1435ee8f90d1ee62f5fb4a4fac48aacda77
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
retain previous behavior.
Conflicts:
etc/inc/upgrade_config.inc
|
| | |
|
| |\ |
|
| | |
| | |
| | | |
Unset any old CA and Cert in the system section that might still be there from when upgrade_066_to_067 did not unset them. That will tidy up old configs that had the conversion done originally but these old sections were left behind.
|
| | |
| | |
| | |
| | |
| | | |
This looked odd. Why would we leave behind the old "ca" and "cert" section in $config["system"]?
I guess it would do no harm, but seems confusing for the future to have some unused entries like this remaining in the config.
Should a piece of code be put into the latest upgrade function to clean out these in any current config?
|
| |\ \ |
|
| | |/
| | |
| | | |
It would be quite unusual to have no filter rules array, but if that is indeed the case then the first part of this code that sets dnpipe and dnqueue numbers should execute anyway.
|
| |/
| |
| | |
With the typo, this empty() test would always have been true. So maybe on upgrade some existing captive portal zoneid values have been getting overwritten by this even number counter? Or?
|
| |
| |
| |
| |
| | |
- Add a upgrade code to fix asn1dn string format to match strongSwan needs
- Bump config version to 11.8
|
| |
| |
| |
| |
| |
| |
| | |
and other random stuff I noticed.
I think this finishes messing with code style. The codebase should match
the developer style guide closely enough that 99.9% of changes will not
feel the need to also massage the formatting.
|
| | |
|
| |
| |
| |
| | |
a config setting to disable, rather than enable, this functionality since it's enabled by default so the tag isn't necessary in the default config. Remove now unnecessary config upgrade code.
|
|\ \
| |/ |
|
| | |
|
| |
| |
| |
| | |
lan from ipsec. Ticket #4504
|
|\ \
| |/ |
|
| |
| |
| |
| | |
provide upgrade code to make sure old configs are converted. Since there was a config upgrade version 11.7 only on master, I pushed it to 11.8 and used dns_split one as 11.7 to be able to backport it to RELENG_2_2. Ticket #4418
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This code looked silly the way it was, with the construct:
$var = $var;
unset($var);
Seems it was accidentally changed to this way many years ago by https://github.com/pfsense/pfsense/commit/588a183b0e58f09932ffef35cc0003cca2313aba
IMHO we want to do the conversion to $config['system']['gateway'] here so that later config conversion will then process it as expected.
Note that in a current (2.2) config there is not $config['system']['gateway'] but that is switched over later in upgrade_021_to_022 - which switches back to $config['interfaces']['wan']['gateway'] and then later config conversions do their thing with that.
I guess this will only effect people who upgrade from some really old config (or monowall?)
|
| |
| |
| |
| | |
that I noticed.
|
| |
| |
| |
| | |
remove empty values
|
| |
| |
| |
| | |
upgrade config code so old entries not lost during upgrade
|
|/
|
|
|
|
|
| |
* $x; > $x = null;
* removed duplicated cases
* fixed useless statement: (int)$x = $y
* removed poetic: if (!$x && $x) $x = $x
|
|
|
|
|
|
|
|
|
| |
strongswan config.
To be able to manage this first upgrade the config to assign each phase2 an reqid
Second use that during config generation
Ticket #4208
|
|
|
|
|
|
|
|
|
| |
- Unbound advanced options may contain double quotes and it breaks the
syntax when a backup is restored because newlines are trimmed. Save it
in base64 format is a safe way to prevent it
- Bump config version to 11.5
- Provide upgrade code to encode current config or the one that came
from unbound package on 2.1.5
|
| |
|
|
|
|
|
| |
and module names and other bits of formatting and typos in header
comment sections.
|
|
|
|
| |
11.4. It fixes #4163
|
|
|
|
| |
It fixes #4134
|
|
|
|
| |
it's related to ticket #4090
|
|
|
|
| |
upgrade code. This fixes #4122
|
|
|
|
| |
should fix #4104
|
| |
|
| |
|
| |
|
|
|
|
| |
that doing the right checks
|
| |
|
| |
|
| |
|
|
|
|
| |
things can go really bad with functions redeclared un base and package unbound.inc and config corrupted when upgrading from 2.1.x with unbound installed to 2.2. PBI and package section are both removed later during package upgrade
|
| |
|
|
|
|
| |
2.2 base. Bump config version to 11.1. It fixes #3880
|
|
|
|
| |
mistakes when modifying and editing them.
|
| |
|
| |
|
| |
|
|
|
|
| |
config.xml. This is a proper fix for #3688
|
|
|
|
| |
also bump config version and write a function to keep the current status on upgrades
|