Displaying 1 50 of 28,212 commits (0.060s)

pfSense — etc rc.packages

Make rc.packages deal with fcgicli call
Delta File
+16 -4 etc/rc.packages
+16 -4 1 file

pfSense — etc/inc unbound.inc

Merge pull request #1732 from phil-davis/traffic-graphs-widget
∈ jim-p - 342f5090 - 2015-06-26 13:44:34
    Use interface-automatic for Unbound when the interfaces list is empty (same as All) 
otherwise it breaks with a default CARP config.
Delta File
+2 -0 etc/inc/unbound.inc
+2 -0 1 file

pfSense — etc/inc unbound.inc

    Use interface-automatic for Unbound when the interfaces list is empty (same as All) 
otherwise it breaks with a default CARP config.
Delta File
+2 -0 etc/inc/unbound.inc
+2 -0 1 file

pfSense — etc/inc unbound.inc

    Use interface-automatic for Unbound when the interfaces list is empty (same as All) 
otherwise it breaks with a default CARP config.
Delta File
+2 -0 etc/inc/unbound.inc
+2 -0 1 file

pfSense — usr/local/www/widgets/javascript traffic_graph.js, usr/local/www/widgets/widgets traffic_graphs.widget.php

Only process Traffic Graph object if it is open

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.

    [4 lines not shown]

pfSense — usr/local/www diag_tables.php

Merge pull request #1717 from phil-davis/traffic-graph-description
∈ Renato Botelho - 72e2a428 - 2015-06-25 12:39:11
Merge pull request #1725 from phil-davis/gateways-widget
∈ Renato Botelho - 03e4bd0c - 2015-06-25 11:48:53
Merge pull request #1730 from phil-davis/patch-2
∈ Renato Botelho - 7d6b8b9b - 2015-06-25 11:47:56
Merge pull request #1729 from phil-davis/widget-iform
∈ N0YB - 763afdaf - 2015-06-15 19:25:37
Add semicolon

Fix delete Java Script to match valid HTML ID
Delta File
+3 -2 usr/local/www/diag_tables.php
+3 -2 1 file

pfSense — usr/local/www diag_tables.php

Merge pull request #1725 from phil-davis/gateways-widget
∈ Renato Botelho - 03e4bd0c - 2015-06-25 11:48:53
Merge pull request #1730 from phil-davis/patch-2
∈ Renato Botelho - 7d6b8b9b - 2015-06-25 11:47:56
Merge pull request #1729 from phil-davis/widget-iform
∈ N0YB - 763afdaf - 2015-06-15 19:25:37
Add semicolon

Fix delete Java Script to match valid HTML ID
Delta File
+3 -2 usr/local/www/diag_tables.php
+3 -2 1 file

pfSense — usr/local/www diag_tables.php

Merge pull request #1730 from phil-davis/patch-2
∈ Renato Botelho - 7d6b8b9b - 2015-06-25 11:47:56
Merge pull request #1729 from phil-davis/widget-iform
∈ N0YB - 763afdaf - 2015-06-15 19:25:37
Add semicolon

Fix delete Java Script to match valid HTML ID
Delta File
+3 -2 usr/local/www/diag_tables.php
+3 -2 1 file

pfSense — etc version

Merge pull request #1719 from N0YB/XHTML_Compliance_Diagnostics_Tables
∈ Renato Botelho - 0828f970 - 2015-06-25 11:10:21
Bump version to 2.2.4-DEVELOPMENT
Delta File
+1 -1 etc/version
+1 -1 1 file

pfSense — etc version

Bump version to 2.2.4-DEVELOPMENT
Delta File
+1 -1 etc/version
+1 -1 1 file

pfSense — usr/local/www services_dhcp.php

    Display any advanced DHCP server settings
    
    when the page is first displayed.
    This has annoyed me a few times and it annoyed me again just now. I had some settings 
in one of the advanced boxes that were no longer wanted, but when the services_dhcp page 
is shown the contents of advanced settings are not shown to the user - the user has to 
click on each advanced button to see if there are any settings already there.
    This change displays the settings automatically, if there is something already 
specified. It works the same way as the Firewall Rules advanced boxes.
Delta File
+14 -14 usr/local/www/services_dhcp.php
+14 -14 1 file

pfSense — etc version

It's time for 2.2.3-RELEASE
Delta File
+1 -1 etc/version
+1 -1 1 file

pfSense — etc/inc system.inc

Add D1540-XG.
Delta File
+3 -0 etc/inc/system.inc
+3 -0 1 file

pfSense — etc/inc system.inc

Add D1540-XG.
Delta File
+3 -0 etc/inc/system.inc
+3 -0 1 file

pfSense — etc/inc pfsense-utils.inc system.inc

Introduce Netgate RCC-DFF to the list of known platforms

pfSense — etc/inc pfsense-utils.inc system.inc

Introduce Netgate RCC-DFF to the list of known platforms

pfSense — etc/inc vpn.inc

    rereadall is not enough here, restore reload call to make sure everything works. 
Ticket #4785
Delta File
+1 -0 etc/inc/vpn.inc
+1 -0 1 file

pfSense — etc/inc vpn.inc

    rereadall is not enough here, restore reload call to make sure everything works. 
Ticket #4785
Delta File
+1 -0 etc/inc/vpn.inc
+1 -0 1 file

pfSense — etc/inc vpn.inc

    Replace ipsec rereadsecrets + reload by single rereadall, that will re-read also cert 
changes. Ticket #4785
Delta File
+1 -2 etc/inc/vpn.inc
+1 -2 1 file

pfSense — etc/inc vpn.inc

    Replace ipsec rereadsecrets + reload by single rereadall, that will re-read also cert 
changes. Ticket #4785
Delta File
+1 -2 etc/inc/vpn.inc
+1 -2 1 file

pfSense — etc/inc vpn.inc

    Instead of sending USR1, just call ipsec reload. And before it, call ipsec 
rereadsecrets to make sure new secretes are updated. It should fix #4785
Delta File
+2 -1 etc/inc/vpn.inc
+2 -1 1 file

pfSense — etc/inc vpn.inc

    Instead of sending USR1, just call ipsec reload. And before it, call ipsec 
rereadsecrets to make sure new secretes are updated. It should fix #4785
Delta File
+2 -1 etc/inc/vpn.inc
+2 -1 1 file

pfSense — etc/inc vpn.inc

    Partially revert 019ee2bc8c, this workaround is not necessary. Real fix will be 
committed after this
Delta File
+0 -8 etc/inc/vpn.inc
+0 -8 1 file

pfSense — etc/inc vpn.inc

    Partially revert 019ee2bc8c, this workaround is not necessary. Real fix will be 
committed after this
Delta File
+0 -8 etc/inc/vpn.inc
+0 -8 1 file

pfSense — etc/inc vpn.inc

Add a workaround for ticket #4785:

There was a regression on strongswan between 5.3.0 and 5.3.2 as reported
at [1]. To workaround this issue, add an extra line on ipsec.secrets
with right fqdn.
Delta File
+18 -4 etc/inc/vpn.inc
+18 -4 1 file

pfSense — etc/inc vpn.inc

Add a workaround for ticket #4785:

There was a regression on strongswan between 5.3.0 and 5.3.2 as reported
at [1]. To workaround this issue, add an extra line on ipsec.secrets
with right fqdn.
Delta File
+17 -4 etc/inc/vpn.inc
+17 -4 1 file

pfSense — usr/local/www/widgets/javascript traffic_graph.js, usr/local/www/widgets/widgets log.widget.php picture.widget.php

Standardize widget iform and submit names

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

pfSense — etc/inc shaper.inc

Fix var name typo in shaper.inc
Delta File
+1 -1 etc/inc/shaper.inc
+1 -1 1 file

pfSense — usr/local/www/widgets/widgets gateways.widget.php

Merge pull request #1728 from devnullity/patch-1
∈ Phil Davis - 6538d33a - 2015-06-23 05:53:53
    GW widget input form name-id needs to be unique
    
    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.

pfSense — etc rc

    Don't delete /var/tmp/, that was originally done to clear session data at boot, but no 
longer applicable as session data is no longer in /var/tmp/. Credit to 'aa' on opnsense 
forum.
Delta File
+0 -1 etc/rc
+0 -1 1 file

pfSense — etc rc

    Don't delete /var/tmp/, that was originally done to clear session data at boot, but no 
longer applicable as session data is no longer in /var/tmp/. Credit to 'aa' on opnsense 
forum.
Delta File
+0 -1 etc/rc
+0 -1 1 file

pfSense — etc/inc vpn.inc

Use $myid in ipsec.secrets. Ticket #4785

Conflicts:
        etc/inc/vpn.inc
Delta File
+2 -2 etc/inc/vpn.inc
+2 -2 1 file

pfSense — etc/inc vpn.inc

Use $myid in ipsec.secrets. Ticket #4785
Delta File
+2 -2 etc/inc/vpn.inc
+2 -2 1 file

pfSense — etc/inc ipsec.inc

    This is incomplete. Leaving for 2.3. Revert "Ticket #4683 merge in brainpool for DH 
parameters"
    
    This reverts commit 7dc35024af3af1d644c25b002ca9f40f1d61c05b.
Delta File
+2 -11 etc/inc/ipsec.inc
+2 -11 1 file

pfSense — usr/local/www bandwidth_by_ip.php

Add DNS host override descriptions

since we can sometimes provide a useful description from that config
data also.
Fill the $iplookup array with host or FQDN data if description is blank
or host or FQDN was requested. Then we can use $iplookup in all cases
where we have local data. It simplifies some logic a bit.
Delta File
+30 -14 usr/local/www/bandwidth_by_ip.php
+30 -14 1 file

pfSense — etc/inc shaper.inc

Fix var name typo in shaper.inc

Fix typo so get_bandwidthtype_scale can do more than default to "1".
Delta File
+1 -1 etc/inc/shaper.inc
+1 -1 1 file

pfSense — etc/inc vpn.inc

    Specify $myid rather than %any here, otherwise user manager and mobile PSKs won't 
match. Ticket #4781
Delta File
+7 -6 etc/inc/vpn.inc
+7 -6 1 file

pfSense — etc/inc vpn.inc

    Specify $myid rather than %any here, otherwise user manager and mobile PSKs won't 
match. Ticket #4781
    
    Conflicts:
            etc/inc/vpn.inc
Delta File
+8 -7 etc/inc/vpn.inc
+8 -7 1 file

pfSense — etc pfSense.obsoletedfiles

Obsolete pt_BR.ISO-88591 in favor of UTF-8
Delta File
+1 -1 etc/pfSense.obsoletedfiles
+1 -1 1 file

pfSense — etc/inc pfsense-utils.inc, usr/local/share/locale/pt_BR/LC_MESSAGES pfSense.po

Move pt_BR translation from ISO to UTF-8

pfSense — usr/local/share/locale/pt_BR.ISO8859-1/LC_MESSAGES pfSense.po, usr/local/share/locale/pt_BR/LC_MESSAGES pfSense.po

Move pt_BR directory, it's moving from ISO to UTF-8

pfSense — usr/local/www/includes functions.inc.php, usr/local/www/widgets/widgets gateways.widget.php

Display monitor IP on Gateways widget

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.

pfSense — etc/inc captiveportal.inc, usr/local/www services_captiveportal_hostname_edit.php

Ticket #4746 Correctly set global variables to be used by hostnames cod epaths

pfSense — etc/inc captiveportal.inc, usr/local/www services_captiveportal_hostname_edit.php

Ticket #4746 Correctly set global variables to be used by hostnames cod epaths

pfSense — etc/inc ipsec.inc

Merge pull request #1724 from phil-davis/patch-3
∈ Ermal LUÇI - 7dc35024 - 2015-06-19 10:47:18
Ticket #4683 merge in brainpool for DH parameters
Delta File
+11 -2 etc/inc/ipsec.inc
+11 -2 1 file

pfSense — etc/inc ipsec.inc

Ticket #4683 merge in brainpool for DH parameters
Delta File
+11 -2 etc/inc/ipsec.inc
+11 -2 1 file

pfSense — etc/inc filter.inc, usr/local/www system_advanced_firewall.php

Add a GUI field to increase the pf frag entries limit. Fixes ticket #4775

pfSense — etc/inc filter.inc, usr/local/www system_advanced_firewall.php

Add a GUI field to increase the pf frag entries limit. Fixes ticket #4775

pfSense — etc/rc.d hostid

chmod +x hostid
Delta File
+0 -0 etc/rc.d/hostid
+0 -0 1 file

pfSense — etc/rc.d hostid

chmod +x hostid
Delta File
+0 -0 etc/rc.d/hostid
+0 -0 1 file