| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
| |
removed CAs, certs, or CRLs remain. Ticket #5238
|
|
|
|
| |
settings take precedence. Set logging levels in strongswan.conf to match what's set on a running system via 'ipsec stroke loglevel', and remove log levels that were hard coded in strongswan.conf. Ticket #5242
|
|
|
| |
Because it breaks traffic graphs for people.https://forum.pfsense.org/index.php?topic=87390.0
|
|
|
|
| |
it applies to all types.
|
|
|
|
| |
change auth methods for both peers when using hybrid RSA + xauth with IKEv1
|
| |
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
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
|
|\ |
|
| |
| |
| |
| |
| | |
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.
|
|
|
|
| |
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
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
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
|
|\ \ \ \ \ |
|
| | |_|/ /
| |/| | | |
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
|\ \ \ \ |
|
| | | | | |
|
| | | | | |
|
|\ \ \ \ \ |
|
| | |/ / /
| |/| | | |
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
So that "versions" that probably are the same will be compared the same:
"Utility-1.0" and "utility-1.0"
"2.3.4_5 pkg v1.2" and "2.3.4_5 pkg V1.2" and "2.3.4_5 Pkg V1.2" and...
This will allow people to modify the case of the version text however they like without making the istalled packages list look like there is an upgrade (or downgrade).
|
| | |_|/ /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This function parses and compares two strings to see which one seems to represent the greater "version". It splits the strings into pieces that are digits and pieces that are anything else. e.g.
"utility-24.9_5 pkg v4.5"
becomes
"utility-"
24
"."
9
"_"
5
" pkg v"
4
"."
5
A new version might be:
"utility-24.10_5 pkg v4.5"
Each component is compared.
If both corresponding components are "integer chunks" they are compared using "<" and ">" - that means that 10 becomes greater than 9.
If either component is not "integer" then string comparison is done. This makes the ordinary string changes work as expected and also stuff like "1.05" and "1.1" - a change like this will be seen as an upgrade.
Not that I have left the string comparison case-sensitive. If someone making their version string changes the "fixed text" they have put in the version string then anything is possible :) It is a bit difficult to guess all of that.
Also if people use alphabetic versioning that does not follow strcmp() sort order then there is always trouble - it works by luck with "-BETA" then "-RELEASE" because the English words happen to sort as expected.
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
For RELENG_2_2 - same thing as #1886
This has been broken ever since commited in 420aa48
As noted on https://redmine.pfsense.org/issues/3670 - the get_interface_ipv6() function in /etc/inc/interfaces.php incorrectly identifies the interface as the physical hardware interface. As a result, no global IPv6 address can be found (empty $ifcfgipv6) - https://redmine.pfsense.org/issues/3556
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
the database.
This fix the case where the database is not initialized because the used
field in backup file is empty.
Fix the issue #5113.
|
| |_|_|/ /
|/| | | |
| | | | |
| | | | | |
otherwise ruleset ends up invalid. Ticket #4935
|