| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
mounted as MFS
|
|
|
|
| |
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.
|
|\ |
|
| |
| |
| |
| | |
SVG MIME type is `image/svg+xml`.
|
| |
| |
| |
| | |
without printing anything
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
are too short to be a valid voucher.
Discussed with: Jim P
Issue: #4985
|
| |
| |
| |
| | |
dynamic interface scanning support. This seems to be the source of crashes in ntpd as described in Ticket #4155, and appears to be unnecessary.
|
| | |
|
|\ \ |
|
| | | |
|
| | |
| | |
| | |
| | | |
fields
|
| | |
| | |
| | |
| | | |
Resubmit of #1793
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Resubmit of #1812
The current implementation isn't working due to API change. Credits: det0nat3 @ https://forum.pfsense.org/index.php?topic=87436.msg534817#msg534817
|
| | | |
|
|\ \ \ |
|
| | | |
| | | |
| | | | |
Partial resubmit of PR #1798 (not really convinced the second part is wanted or correct).
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Do not call conf_mount_ro just before call write_config(),
write_config() calls conf_mount_(rw|ro), and if filesystem is already
mounted in rw state, it'll only increase the refcounter
|
|\ \ \ |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ /
|/| | |
|
|\ \ \
| | | |
| | | |
| | | | |
itshari-bootstrap
|
| | | | |
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Cleaner version of https://github.com/pfsense/pfsense/pull/1846
|
|/ / / /
| | | |
| | | |
| | | | |
to improve the English.
Resubmit of PR https://github.com/pfsense/pfsense/pull/1847
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
DHCP6
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 notices are currently keyed by the Unix time stamp second. If
file_notice() is called more than once in the same second, then the
previous notice is overwritten. Only the last notice in any second
actually ends up in /tmp/notices and thus on the webGUI flashing
display.
The $queuekey value seems to be used to work out the actual time of the
event for display, so it is a bit tricky to change that to a
finer-grained key - callers of these functions are expecting an array
key that is the Unix time in seconds, so all calls to this stuff would
have to be examined and adjusted...
The workaround here is to increment the key if the existing key is
already in use. This allows all notices in the same second to be saved,
but the time of each one will be an incrementing seconds counter, even
though the events all happened in the same second. Maybe that is a
reasonable/practical workaround for now? Given that there should not be
too many notices filed at the same second.
This is a resubmit of PR #1782 integrated with the current master.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
- Remove PPTP server and all related code
- Bump config version 12.2
- Write upgrade config code to remove pptpd section and also cleanup
firewall and NAT rules using PPTP interface or src/des
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
- Remove PPTP server and all related code
- Bump config version 12.2
- Write upgrade config code to remove pptpd section and also cleanup
firewall and NAT rules using PPTP interface or src/des
|
| | | | | | |
|