| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
(cherry picked from commit 6924a2bf34a70cd33284a28ca3575f33f9834375)
|
|
|
|
|
| |
- allow showing different graphs to be shown on different browser tabs (dont use localstorage for graphs to query)
- show interface name in graph instead of realname
|
|
|
|
|
|
|
|
|
|
|
| |
SureGPS and make optional.
- Parse GPS initialization commands for explicitly configured GPS commands
- Add extended GPS status if GPGSV or GPGGA are explicitly configured
- Add config option to toggle extended status
- Clean up some variables on status page and widget.
(cherry picked from commit d627983d2504e56015e14f1f85a4eb6b70a5eea9)
|
|
|
|
|
| |
Noticed while looking in widget code, might as well fix it.
(cherry picked from commit a80ce1a7e03ca4fa61f83166b747b4f72dddd4ba)
|
|
|
|
|
|
|
| |
When doing testing I had the Interfaces widget open as well as Interface Statistics. $ifdescrs was already populated as an array by the Interfaces widget, so Interface Statistics had (accidentally) gained the benefit.
If you have just the Interface Statistics widget on the dashboard then you get the reported PHP error, in the code that sets up the checkbox array of selectable interfaces. The problem is fixed by always calling get_configured_interface_with_descr() at the top of this code, rather than calls that were just inside various if() cases.
Note: get_configured_interface_with_descr() in util.inc always returns an array, even if an empty one, so the ```if (!is_array($ifdescrs))``` testing should not be needed.
(cherry picked from commit 8f94fc33f07718141f332a567df7b30f91c38c93)
|
|
|
|
| |
Fixes #7134
|
|
|
|
| |
(cherry picked from commit 22e8fa1f6aec0b1536f0c07e1573ac78a291891f)
|
|
|
|
| |
(cherry picked from commit 27bf84fc10d723deebb814a38ee9303014b41711)
|
|
|
|
| |
(cherry picked from commit a670560bf9a3de550e9e4e20df4ffe1ed2d4f05c)
|
|
|
|
|
| |
Does not make sense otherwise, can only contain stale data.
(cherry picked from commit 8ed692516534248e58a20aec70f8cf3035d35348)
|
|
|
|
| |
(cherry picked from commit 47b35618f025082b5504eae5518d89c772ae8bd5)
|
|
|
|
| |
(cherry picked from commit 5f8a3dc09e550f3aa2ef086c03e7133f78756913)
|
|
|
|
| |
(cherry picked from commit 35310a493f19d6758747cbc8e9961c2ca3395246)
|
|
|
|
| |
(cherry picked from commit 84a7e840eac8f62a95ccb900089faf14a9a9fc65)
|
|
|
|
| |
(cherry picked from commit d82c5cbf4f693d70e55b5a484a34ea84f88fa250)
|
|
|
|
|
|
|
|
| |
Tidy up <script> tags by adding TYPE attribute
(https://doc.pfsense.org/index.php/Developer_Style_Guide#HTML_Specific_Rules)
(cherry picked from commit 463456964709015d4b1c591aa4251c831a39c71d)
|
|
|
|
| |
(cherry picked from commit 7b3d8a4b8cee0588ed2ccd272588026002369433)
|
|
|
|
| |
(cherry picked from commit b84126b5e74473b1e6a576f38da2149a95ab03fc)
|
|
|
|
| |
(cherry picked from commit ada6bfa7ca68169408b80af6325afe3948ee85f7)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If an alternate monitor IP has been entered and saved, then the user
checks "Disable Gateway Monitoring" and saves, the alternate monitor IP
is retained in the config - that is handy for when unchecking "Disable
Gateway Monitoring" later on.
But the Gateways widget and Status Gateways do not correctly understand
this combination. The gateway status shows as "Online" when it is
intended to show "Online (unmonitored)".
This PR corrects this.
(cherry picked from commit 0c5d4e8d3e4dc81a9c7eb883a40296493e9faa2b)
|
|
|
|
|
|
|
|
|
| |
- trim sat in use
- gps ok for GPGLL
- lat & lon direction for GPGGA & GPGLL
- sat in use text position fixed
(cherry picked from commit fdb0479758339e083f7745d738c9999d86af150f)
|
|
|
|
| |
(cherry picked from commit 605a9e6c1f1fae786468b81bf7c911a874048fad)
|
|
|
|
|
| |
This only updates after the refresh period set in System - General Setup - Dashboard update period; should not be hardcoded.
(cherry picked from commit 827c3f1e2bd99a4b27e65d0fa317bcb3b8944943)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
without disabling gateway monitoring.
This allows the user to continue to monitor the gateway with dpinger, so
they can see how it is performing, but for the system not to take any
real action if the latency/loss exceeds the given limits.
A typical use case for this would be on a single-WAN system. There is no
failover option, so there is no point taking any real action when the
latency/loss is high. Having stuff try to failover (and stop/start
stuff...) is just disruptive.
In ths case the use could have disabled monitoring completely, but then
they get no feedback abut gateway performance.
(cherry picked from commit f396d2b715b27312c9bc056b3423db8198f7d52a)
|
|
|
|
|
|
| |
Note: corresponding change to upgrade_config.inc to come in master to
correctly implement the upgrade_155_to_156 code, that is master only and
will become upgrade_158_to_159
|
|
|
|
| |
(cherry picked from commit cd2c59c9839e38fa7cbd4ae217fe14883b086145)
|
|
|
|
|
|
|
|
| |
user from admin UI
When a user is disconnected by the administrator using the pfSense captive portal status page or widget set the value of the Acct-Terminate-Cause in the RADIUS accounting stop packet to "Admin Reset" (6) as per RFC 2866.
(cherry picked from commit 2a119ed3cbf6bd4bc438e5b1993bd4c55c2663c6)
|
|
|
|
| |
Added code for IPv6 Dynamic DNS
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
(cherry picked from commit 516e609ccb7a39fb27f52a69f11eee68f86974df)
|
|
|
|
| |
(cherry picked from commit 8da4847472e03195aeb73a1acedbc27f8af520d1)
|
|
|
|
| |
(cherry picked from commit 134ee13df54280441c25b047b406628eeebbb8db)
|
|
|
|
|
|
|
| |
Start each widget refresh system after a short random delay to prevent all widgets hitting the server at the exactsame time
Fix issues wherein two widgets were resetting the refresh timer from the AJAX call, not the call-back function, thereby risking stepping on themselves
(cherry picked from commit 512f2c10af716243046bdd08140856bb8e45222b)
|
|
|
|
|
|
| |
by making the OpenVPN widget update dynamically
(cherry picked from commit f30e6bd49c773de28b5ec143add30fc900e7874d)
|
|
|
|
|
|
| |
No functional change - just making style consistent
(cherry picked from commit 9d3e8723171c727cf43338bd8e95ab2bb7e6a66c)
|
|
|
|
|
|
|
|
|
| |
For users that have "custom settings" enabled, save the "tool" settings
of their widgets on a per-user basis.
User that do not have "custom settings" enabled will continue to use and
save widget settings to/from the system-wide settings.
(cherry picked from commit 2b7d0520818248920ec88514fde2c9b86c2a70af)
|
|
|
|
|
|
| |
Read widget config before adding a new one. (Was starting a new array)
(cherry picked from commit 236e6a54e9a93284ca170b68aa1188dfaa195c3d)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
(cherry picked from commit 658180daffe0fe5f005b6fe6b528c758309dffef)
|
|
|
|
| |
(cherry picked from commit 8d0b16a11c6a2a61fe51507a9b43b3bcad3aab80)
|