| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| | |
fine with IKEv2
|
| |
| |
| |
| | |
Ticket #3858
|
| | |
|
| |
| |
| |
| | |
Fixes PSK mismatches from iOS clients.
|
| |
| |
| |
| | |
IP addresses from RADIUS instead. (Will need an IP address defined for each account.) Doesn't seem to be possible to pull from either RADIUS *or* a local pool that I can see from experimenting and looking at strongSwan's docs.
|
|/
|
|
| |
actually works.
|
| |
|
|
|
|
|
| |
"ipfw zone" command, breaking CP for any system that doesn't have VIPs
defined.
|
| |
|
| |
|
|
|
|
|
|
| |
just a synonym for IKEv2. Ticket #4873"
This reverts commit 47f802694a1e1dfbbd011d7ec431c0948358b5c3.
|
|
|
|
| |
Ticket #4990
|
|
|
|
| |
changed. Ticket #5214
|
|
|
|
|
|
|
| |
fixing is more complex than just fixing the variable screw up and
disabling cert validation for their SSLLabs F-graded site. Updates made on
their site even take quite some time to be reflected, seems to be a largely
abandoned service.
|
|
|
|
| |
over-matching. Ticket #5211
|
|
|
|
| |
craft a full name and read the file. Fixes #5203.
|
|\ |
|
| |
| |
| |
| |
| | |
This one will log_error() the DHCP pool message when it detects the inconsistency at the end of the setup wizard during reload all.
That way it can still be seen in the system log that this happened, and one day someone might chase down all the steps in the "reload all" process.
Compare this with https://github.com/pfsense/pfsense/pull/1935 and choose which way you would like to go.
|
|\ \
| |/
|/| |
|
| | |
|
|/
|
| |
The remove_text_from_file() is not needed at all. However, system_syslogd_start() must be run after the package entries are gone from config.xml, otherwise system_syslogd_start() just re-adds the (now almost removed) package logging configuration from there.
|
|
|
|
| |
default. Fixes #5199
|
|\ |
|
|/
|
|
| |
The correct text is already displayed under the DNS server boxes at line 892.
This should also be done to master once the conversion of services_dhcp.php to bootstrap is stable.
|
|
|
|
| |
gateway groups this way, and cache doesn't really matter here. Partial fix for Ticket #4990
|
|
|
|
|
|
|
| |
are too short to be a valid voucher.
Discussed with: Jim P
Issue: #4985
|
|\ |
|
|/
|
|
|
|
| |
RELENG_2_2 Vagain
with errors fixed.
Supersedes https://github.com/pfsense/pfsense/pull/1781
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes Redmine #4884
1) Line 778-780 - If the fetch of any of the package additional files
fails then bail out. This prevents half-installed packages that look
like they had a successful install.
2) Line 1458 - use the return boolean value from
download_file_with_progress_bar() to determine success or failure here,
like is done in the other places in this file. I had a case of
installing a package with an error (timeout) and the download (I presume
it was the download code) had left an empty file
/usr/local/pkg/autoconfigbackup.xml - it passed the file_exists() check
and the rest of the code went on to happily install the "nothing" in the
package and then claim the package was successfully installed :(
After the above 2 changes I could get reliable indication of
success/failure of the package install and the code would abort nicely
if a download went wrong.
3) Package installs happen either:
i) On the end of a boot after upgrade or config restore, or;
ii) Online while the main system is running (happily)
Therefore there is no need to rush to abort if the download of a package
file is taking some time to get started. It seems better to me to wait a
decent amount of time rather than abort.
Thus I have increased the connect timeout for this from the default (5)
to 30 seconds.
This makes my crap sites load packages much better :)
|
| |
| |
| |
| | |
Resubmit of #1793
|
| |
| |
| |
| |
| | |
https://redmine.pfsense.org/issues/4830
https://forum.pfsense.org/index.php?topic=95908.0
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
newly added fields
Backport from PR #1906 / PR #1787 for RELENG_2_2.
Check if the actual $fieldname element is present in the $a_pkg[$id] array before trying to assign its value. Do same with default_value. Fixes issue where default value was not being populated for newly added fields.
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | | |
Backport of #1812 to RELENG_2_2
The current implementation isn't working due to API change. Credits: det0nat3 @ https://forum.pfsense.org/index.php?topic=87436.msg534817#msg534817
|
|\ \ \ |
|
| | | | |
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | | |
Backport of https://github.com/pfsense/pfsense/pull/1824
|
|\ \ \ \ \ |
|
| | |_|/ /
| |/| | | |
|
|\ \ \ \ \ |
|
| |/ / / /
| | | | |
| | | | |
| | | | | |
config backup - RELENG_2_2
|
|\ \ \ \ \ |
|
| |/ / / / |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
|
| | | | |
| | | | |
| | | | | |
Remove leftover :
|
| | | | | |
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When using VGA console, interface assignment can be a real pain in the ass because of the standard 80 columns width.
Dmesg reports the many interface description names in very long strings that don't fit in a row, this breaks the nice appearance of the interface list in the assignment menu.
The aestethics is one thing, but the real pain is that the interface list goes off screen by the time the menu asks for the WAN interface name, if there are many interfaces present. It's a real problem to choose from a list which is not visible anymore.
One fix is to maximize the length of the interface description to 48 chars.
The second fix (and also improvement for better overlooking when the list really goes off) is to print a small list of the interface names at each question. This is necessary because when somebody wants to assign the first interface to the last Optional port, the big list will be way off screen by then, and the name of it won't be visible.
This also makes it nice clean and straightforward.
|