| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
done on 2.1.1 for Ticket #3441
|
|
|
|
| |
exec() calls by php functions like symlink, copy, unlink, mkdir
|
|
|
|
| |
even for nat for later usage while here.
|
| |
|
|
|
|
| |
through with a blank/null name.
|
| |
|
|
|
|
| |
that from existing configs
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Rename some privileges:
page-diag-system-activity => page-diagnostics-system-activity
page-interfacess-groups => page-interfaces-groups
page-interfacess-lagg => page-interfaces-lagg
page-interfacess-qinq => page-interfaces-qinq
- Write an upgrade function to replace above privileges by the new name
- Remove unused privilege page-diagnostics-logs-wireless
- Remove duplicated privileges
- Fix limiter-info, pf-info and system-pftop that were using wrong name
- Add privs for edit pages (interfaces_groups, interfaces_lagg,
interfaces_qinq and services-igmpproxy)
- Fix ID for acptiveportal allowedhostnames and editallowedhostnames
- Fix some wrong matches
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Add 2 new outbound NAT modes, hybrid and disabled, manual and advanced
keep working the same way
- Hybrid mode applies manual rules first, automatic after
- Disabled do no create any outbound NAT rules
- Remove ipsecpassthru config field and rename advancedoutbound to
outbound
- Save mode on $config['nat']['outbound']['mode'] to simplify the logic
- Modify config.default to reflect changes
- Add code to upgrade config, and change latest_version to 10.3
- Use html to align modes and remove some hacks to align using
|
|
|
|
| |
settings on OpenVPN (unset, off, on, adaptive) rather than a simple off/on switch that either doesn't set the value or enables it with adaptive (OpenVPN's default).
|
| |
|
| |
|
|
|
|
| |
was renamed sometime in 2.1 but upgrade code didn't follow. Also shuffle the upgrade code blocks a bit since we need these on 2.1.x and nobody should be on 2.2 yet, so the impact should be minimal to renumber the one bit specific to 2.2.
|
| |
|
|
|
|
|
| |
Updating the the RRD graphs causes two copies of each RRD's XML file to be stored in /tmp.
On Nanobsd, the default /tmp size is 40mb. It doesn't require very many RRD XML dumps before this is exhausted.
|
| |
|
| |
|
|
|
|
|
|
| |
. Create a function to replace strings on deep associative arrays
. Use the recent created function array_replace_values_recursive to fix
VIP interface names instead of touch config.xml directly
|
|
|
|
| |
backup is done after. It should fix #2159
|
|
|
|
| |
and private network rules. Add upgrade code to obey the existing behavior for users (if default block logging was disabled, so is bogon/private rule blocking). Also add a checkbox to disable the lighttpd log for people who don't want their system log spammed by lighty.
|
| |
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
. Change max value for traffic and packets graphs to 20GigE
. Bump config version to 9.6
. Write a config upgrade function to tune current rrd files to the new
max value
|
|
|
|
|
|
|
| |
. Always initialize it to 0 when it's undefined
. Remove unecessary initializations and checks
. Bump config version to 9.5
. Write an upgrade config function to initialize old configs properly
|
|
|
|
|
|
|
|
| |
fields.
We now perform a search and replace on the XML contents to add fields instead of reading the XML into a PHP array.
A conversion with a 2.0 config on a 128MB VM without swap is succesful, needs more testing.
Ticket #2950
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
- Create RRD configs per zone
- Add tabs to see graphs per zone
- Migrate existing rrd files to default cpZone
- While I'm here, call unset() for $rrdcreate and $rrdupdatesh
Resolves #2655
|
|
|
|
|
|
| |
- Replace find that was being called with wrong parameters at
upgrade_054_to_055() and upgrade_080_to_081() by return_dir_as_array()
call.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- When delete interface, do not touch outbound NAT rules
- Skip outbound NAT rules when interface doesn't exist
- Bump latest_config to 9.2
- Since rules with no interface were considered as wan, convert old
rules adding interface 'wan' to avoid breaking old configs
It should fix #2338
|
|
|
|
| |
that period
|
|
|
|
| |
variable to something else so it's not interpreted as an array.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
to be present for the gateways.
This should prevent duplicate gateway entries for people coming from 2.0 that have dynamic interfaces
|
|
|
|
| |
http://forum.pfsense.org/index.php/topic,50182.0.html
|
|
|
|
| |
upgrade code for existing configs. The same fix is necessary for 2.0.x though not sure how this should be committed there.
|
|
|
|
| |
Several parts of the config upgrade relay on functions in these.
|
|
|
|
| |
during upgrade which is triggered from gwlb.inc
|
| |
|
|
|
|
| |
upgrade code if no carp vip defined. Ticket #2445
|
| |
|
| |
|
| |
|