summaryrefslogtreecommitdiffstats
path: root/usr/local/www/widgets
Commit message (Collapse)AuthorAgeFilesLines
* Move main pfSense content to src/Renato Botelho2015-08-2544-4792/+0
|
* Introduce a new item to $g global, 'product_version' and stop reading ↵Renato Botelho2015-07-311-3/+2
| | | | /etc/version all around
* Only process Traffic Graph object if it is openPhil Davis2015-06-262-4/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Traffic Graphs widget puts a graph object for every interface into the HTML of the widget. Underneath the graph object for every interface makes the call to graph.php to get data for the graph, and the refresh interval also keeps happening, which keeps gathering the data every refresh interval for every interface. This wastes a lot of CPU back on the pfSense box gathering data repeatedly if the system has a lot of interfaces and only has the Traffic Graph enabled for 1 or a few of them. e.g. on my poor little Alix at home I had setup 6 VLANs to test some stuff, so I had WAN, LAN, OPT1 and 6 tagged VLANS - 9 interfaces. When I enable the Traffic Graphs widget on the dashboard, the Alix CPU is driven 100% trying to keep up with gathering data for 9 interfaces every 10 seconds, even though I only have 1 graph actually opened! I couldn't see a way to enable/disable the graph.php object from executing. So this change puts the object in and out of the HTML: a) At first display the graph.php object HTML is only put in the relevant "div" if the graph is actually set to be shown in the config. b) When a graph is opened by the user, the Java Script puts the necessary graph.php object HTML into the div. The graph data then starts being requested... c) When a graph is minimised by the user, the Java Script removes the graph.php object HTML from the div. The actions of graph.php stop happening. I can see the difference by just watching "top" from the command line on a low-power system and open/minimizing the graphs on the dashboard. If there is a better way to enable/disable an object like this I am happy to learn about it.
* Merge pull request #1725 from phil-davis/gateways-widgetRenato Botelho2015-06-251-10/+91
|\
| * GW widget input form name-id needs to be uniquePhil Davis2015-06-231-1/+1
| | | | | | | | | | among all widget forms. Traffic Graphs widget already uses the vanilla name "iform". Reusing that name causes Traffic Graphs widget graph display state (show/hide) not to be saved if GW widget was also displayed on the dashboard. This fixes it.
| * Display monitor IP on Gateways widgetPhil Davis2015-06-201-10/+91
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change adds a setting for the Gateways dashboard widget so the user can choose to display the Gateway IP, Monitor IP or both. If "both" is chosen and the Gateway IP is the Monitor IP, then only the Gateway IP is shown - i.e. the same IP address is not repeated on the widget display. If "both" is chosen and the Monitor IP is different to the Gateway IP then the Monitor IP is shown in () brackets after the Gateway IP. If "Monitor IP" is chosen and there is no special Monitor IP defined, then the Gateway IP is displayed (which is also the Monitor IP). If "Gateway IP" is chosen then the widget behaves as it does now. "Gateway IP" is the default. I find this handy because the Gateways widget reports RTT (latency) and loss figures that are actually for pings to the Monitor IP. So it seems useful to be able to display the Monitor IP in the widget.
* | Standardize widget iform and submit namesPhil Davis2015-06-237-13/+13
|/ | | | | | | | | | | | | | | | | | | | The log and picture widgets were both using "iforma" and "submita". Actually it did not break anything because it was only the form name repeated, not id. And nothing was using these names. Traffic Graphs widget was using just "iform". That is a bit dangerous for the future. I got tricked when cut-pasting some code to make some settings options for the Gateways widget. I kept "iform" and then wondered for a while why my Traffic Graphs widget show-hide settings would not save. There was traffic graph JS that referred to just "iform" and that started modifying the "iform" in my new Gateways widget code. Rather than having names "iforma", "iformb"... "submita", "submitb"... it seems much less risk of accidental duplication if these are named like: name_of_widget_iform name_of_widget_submit I don't think there is any user-visible bug in 2.2.* - so this standardization could just go into 2.3
* Remove artifacts from latin1 to utf8 conversionsJose Luis Duran2015-05-161-1/+1
| | | | | | String replacement: s/Ermal L.../Ermal Luçi/g
* Widgets code stylePhil Davis2015-04-1721-829/+926
|
* Code style for small things in usr-local-wwwPhil Davis2015-04-144-88/+90
|
* Few minor text typosPhil Davis2015-04-042-5/+4
| | | | | | Note that advertise is spelt with an "s" in other places in the GUI, so making it consistent in services_ntpd - but maybe Americans do spell it "advertize" these days?
* Remove latin-1 encoding of RSS feedPhil Davis2015-02-021-1/+0
| | | | | Many thanks to Gertjan in forum https://forum.pfsense.org/index.php?topic=87504.msg484017#msg484017 Specifically setting the output encoding to latin-1 was causing the "black diamonds" for special characters in the http://blog.pfsense.org RSS feed (e.g. the registered trademark sign after pfSense did not come out). It should all work by letting simplepie do its default stuff with the RSS feed.
* Ticket #3997, teach code to track carp through uniqids(). Missing carp GUI ↵Ermal LUÇI2015-01-151-1/+1
| | | | changes and upgrade code
* Fix IPsec widget for multiple P2, it fixes #4164Renato Botelho2015-01-121-1/+12
|
* Properly rename the var Ticket #4164Ermal LUÇI2015-01-101-3/+3
|
* Do not count twice the phase2 entriesErmal LUÇI2015-01-091-6/+10
|
* Just some reshufling and cleanupErmal LUÇI2015-01-091-5/+4
|
* split is deprecated move to explodeErmal LUÇI2015-01-071-1/+1
|
* Fix lineup of copyright linesPhil Davis2015-01-0121-319/+346
| | | | | and module names and other bits of formatting and typos in header comment sections.
* Welcome 2015Renato Botelho2014-12-3122-22/+22
|
* IPsec Widget allow for old settings that have no iketypePhil Davis2014-12-301-1/+1
| | | | | as mentioned in https://forum.pfsense.org/index.php?topic=84527.msg471919#msg471919 This change makes it work like similar if tests in /usr/local/wwwvpn_ipsec.php, and code in /etc/inc/vpn.inc that effectively defaults to ikev1 when iketype is not specified. This should make the code here be executed and make $ikeid get the correct value to be used in later code.
* Display tunnel description on IPsec widgetPhil Davis2014-12-261-45/+49
| | | | | | | | There was not even code to attempt to display the description. Also, when I first created a phase1 and there were no phase2 yet, the widget spat out the warning for the line: foreach ($config['ipsec']['phase2'] as $ph2ent){ ... So I enclosed that in a block: if (isset($config['ipsec']['phase2'])) { ... } Tabbing that block in makes the diff look big when there really is little change - a diff ignoring spacing will look much nicer!
* Oops remove variable with same name unused!Ermal LUÇI2014-12-241-1/+1
|
* Add checks for ghost phase2 and no need to check for number of phase2 hereErmal LUÇI2014-12-241-3/+3
|
* Correct skipping of disabled tunnelsErmal LUÇI2014-12-241-1/+1
|
* Correct status counter of inactive tunnelsErmal LUÇI2014-12-241-0/+8
|
* Oops do not override ipsec status array!Ermal LUÇI2014-12-231-2/+2
|
* Merge pull request #1397 from phil-davis/patch-15Chris Buechler2014-12-221-27/+25
|\
| * Interfaces widget remove blank line if no IPv4 addressPhil Davis2014-12-201-2/+1
| | | | | | | | If the interface had an IPv6 address but no IPv4 address, there was a blank line where the IPv4 address would have been. There is no need for that, and one day IPv4 will be old legacy and systems will routinely have no IPv4 addresses at all - they will all be IPv6. Might as well make that look ordinary on the display now. The br goes in the div so we can put it in and out from the AJAX also.
| * Interfaces widget create all divPhil Davis2014-12-201-25/+24
| | | | | | All div for the various things need to be created here, so that later AJAX can switch the necessary things on/off and write a new IPv4 or IPv6 address into the div when an interface acquires an address.
* | Merge pull request #1400 from phil-davis/patch-17Chris Buechler2014-12-221-10/+46
|\ \
| * | Handle firewall log widget display formatsPhil Davis2014-12-211-10/+46
| |/ | | | | | | | | | | | | | | | | | | the same way for the initial display and for updated rows done by Java Script. Now we receive the source IP and port, destination IP and port, all in separate fields so they can be put together in whatever combination for display. IPv6 displayed addresses are shown inside "[ ]" so that any following port has the standard syntax like "[a:b::c:d]:123" - this makes it obvious that the last numbers are a port number, and not part of the IPv6 address. The "title" has IP+Port - that is displayed when hovering over the box in general. The href to diag_dns.php has hover text "Reverse Resolve with DNS" and the "?host=" sends just the IP address (without IPv6 square brackets). The text displayed in the link is the IP address (with square brackets if an IPv6 address). For the destination column, if there is a destinaion port, it is displayed in ordinary text ":port" after the IP address. The blank not-displayed row at the end of the table is removed - this fixes the problem with counting the rows of the table where rows would disappear at each update.
* | Correct dashboard with new ipsec generationErmal LUÇI2014-12-221-24/+43
|/
* Tidy up "widgets" XHTMLColin Fleming2014-12-144-10/+16
| | | | | | | | Add CDATA sections to scripts Add ALT to image tags and close image tags DIV tag cannot be inside a STRONG tag, so swap them around SCRIPT cannot be part of TR tag, so place the SCRIPT inside a TD tag but hide it.
* Use proper listr class for Gateways Widget StatusPhil Davis2014-12-051-1/+6
| | | | | The Gateways Widget Status was not using the listr class, and so it was missing the borders for the right and bottom of its box. Use the listr class. Then use javascript to explicitly set the background-color to match the status, overriding the white that is specified in listr.
* Fix gateway widget status updatePhil Davis2014-12-051-1/+1
| | | Redmine #4077
* Use IPv4 for ntpq if IPv6 not allowed in widget #4074Phil Davis2014-12-041-2/+7
| | | Similar code here. Shame it was not in a subroutine called from both places, but not about to re-engineer that now:)
* fix IPsec widget status display after recent changes broke it. Ticket #4045Chris Buechler2014-11-251-10/+15
|
* fix up textChris Buechler2014-11-221-1/+1
|
* Add .inc file for gmirror status widget to give it a better title and link ↵jim-p2014-11-201-0/+4
| | | | to the management page.
* Define a local boolean var for showact to avoid security issues, also pass ↵Renato Botelho2014-11-181-9/+11
| | | | order parameter trough htmlspecialchars()
* Fix whitespace and indentRenato Botelho2014-11-181-23/+38
|
* Merge pull request #1331 from phil-davis/patch-2Renato Botelho2014-11-181-1/+3
|\
| * Reintroduce graphcounter var to traffic_graphs.widget.phpPhil Davis2014-11-071-1/+3
| | | | | | | | | | This counter got lost in commit https://github.com/pfsense/pfsense/commit/ee965a5c7bf37b852795e1201688e3b20bf3d8d1 But the code at line 174 was still using it to offset the start time of each shown graph by 2 seconds, which I guess helps the graph data collection requests back to the pfSense to be staggered, not all having to be serviced at almost exactly the same time. I noticed this while having a quick look at all the traffic graph widget code to see if there was an obvious place where the 2x bandwidth graphing problem happens. The "* 2" here in line 174 has nothing to do with that!
* | Make sure $cpzoneid is defined and use it to call pfSense_ipfw_Tableaction() ↵Renato Botelho2014-11-131-6/+13
| | | | | | | | and pfSense_ipfw_getTablestats(). Also fix fieldnames for captiveportal_hostnames. It should fix #4001
* | Do not display the disabled tunnels since they are not needed in the widget. ↵Ermal2014-11-121-45/+25
| | | | | | | | Ticket #3955
* | Commit the other part of the fix for Ticket #3955Ermal2014-11-121-1/+1
| |
* | Oops do the right thing here by passing proper argument rather than breaking ↵Ermal2014-11-121-1/+4
| | | | | | | | the ipsec status page. Ticket #3955
* | Change copyright statement to reflect realityJim Thompson2014-11-1022-0/+48
|/
* Use a better method of finding disks for SMART.jim-p2014-11-041-1/+1
| | | | Old code was inaccurate and also listed entries that were symlinks to other disks
OpenPOWER on IntegriCloud