summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* Fix indent and spacesRenato Botelho2014-12-111-5/+7
|
* Fix #4099:Renato Botelho2014-12-111-1/+3
| | | | | | - When interface is 'lo0', strpos returns 0, that is erroneously considered false (boolean) on the test. Be more strict on strpos return to avoid skiping lo0 ip aliases during sync.
* Fix #3790:Renato Botelho2014-12-111-15/+38
| | | | | - Do not let 2 interfaces to setup the same track6 prefix id - Show correct prefix id range for each interface
* Change text and color delimiter to carat signPhil Davis2014-12-111-1/+1
| | | | To match change made in functions.inc.php
* Gateway Status Widget keep IP address boldPhil Davis2014-12-111-2/+2
| | | | | | | | Forum: https://forum.pfsense.org/index.php?topic=85187.msg467438#msg467438 The bold is specified literally in gateways.widget.php for the gateway IP box, so we need to send it bold from here also when providing an update. Because this now uses a "/" in the string (to terminate the bold) have to choose another delimiter between the status text and status color - picked "^" because I can't think where it will appear elsewhere in the real data. This whole string of stuff that is returned by getstats.php back to the browser is a long string with a bunch of delimiters inside delimiters already (vertical bar separated fields, inside that comma-separated fields...) and is already subject to stuff going wrong if any of the real text in the fields contains a vertical bar or comma or... Not about to try to re-engineer all that right now!
* Improve check if no OpenVPN definedPhil Davis2014-12-111-1/+2
| | | | | | Alternate version of https://github.com/pfsense/pfsense/pull/1376 This version retains the is_array() checks and then only does the count() if the is_array() is true. Take whichever version you like.
* Setup ddb on all platforms. On full install it will save the dump, on ↵jim-p2014-12-102-6/+6
| | | | | | NanoBSD it will print to console and auto-reboot. This way, a router running NanoBSD won't sit at a db> prompt indefinitely if it crashes.
* Fixup text rule should be routePhil Davis2014-12-101-6/+6
| | | | This code was obviously taken from firewall rules and reused here without changing the word "rule" to "route".
* Remove spurious '>', fixes #4091Renato Botelho2014-12-101-1/+1
|
* Make sure this message is only displayed on consoleRenato Botelho2014-12-101-1/+2
|
* get_failover_interface() is already called inside get_interface_ip(v6), no ↵Renato Botelho2014-12-101-4/+2
| | | | need to call it twice. It should fix #4089
* Use exit instead of return here, otherwise script's return code is always 0 ↵Renato Botelho2014-12-081-4/+4
| | | | and user with wrong password is authenticated
* Standardise css list paddingPhil Davis2014-12-071-5/+5
| | | | for _corporate
* Standardise css list paddingPhil Davis2014-12-071-5/+5
| | | | for code-red theme
* Standardise css list paddingPhil Davis2014-12-071-5/+5
| | | | for metallic theme
* Standardise css list paddingPhil Davis2014-12-071-5/+5
| | | | for nervecenter theme
* Standardise css list paddingPhil Davis2014-12-071-5/+5
| | | | for pfsense-dropdown theme
* Standardise css list paddingPhil Davis2014-12-071-5/+5
| | | | for pfsense theme
* Standardise css list paddingPhil Davis2014-12-071-5/+5
| | | | for pfsense_ng_fs theme
* Standardise css list paddingPhil Davis2014-12-071-5/+5
| | | | for the_wall theme
* Provide success return indication from console_configure_dhcpdPhil Davis2014-12-071-0/+1
| | | | | | | Recent commit https://github.com/pfsense/pfsense/commit/9ea554ee5cb25ea3bf5bb6bf7997c6c7379ce349 added testing of the return status of console_configure_dhcpd() - this let a user effectively abort from doing anything if they have answered "y" to prompt_for_enable_dhcp_server() and are being asked for the start and end of the range, and then decide they do not want to proceed. However, even when they gave good answers, status 0 was being returned. This prevented changes ever being implemented. Redmine: https://redmine.pfsense.org/issues/4080 The fix is to return 1 at the routine end, when all is good and the code should proceed.
* Standardise css list paddingPhil Davis2014-12-071-5/+5
| | | | | | | | | | | | | | | | | On Status->Services, the Services Status widget when a service status is down, the red "x" button does not line up with the green "running" button in the column. This is because listbg has: padding-right: 16px; But the normal listr has: padding-right: 6px; It seems really odd that listbg as 16 pixels right padding. I expected it to have all the same padding as listr, just with a different color. listn and listbggrey have the same "feature" of extra padding-right. listn does not seem to be used anywhere anyway - might as well "fix" it in case something uses it some time. listbggrey seems to only be used by pkg_mgr_installed.php in the case when an installed package version is in advance of the online version - quite an unusual thing! Changing padding-right from 16px back to 6px is fine for that. Then the "feature" is lso in listhdr and listhdrr - lots of examples like firewall_aliases.php have the column headings as listhdr or listhdrr, so in theory if the column is not so wide already, it will put 16px on the right after the column heading text. But the actual rows of data underneath use listr and listbg, which only specify 6px right padding. In the end it usually does not make any difference - there is space already and the browser lines it all up anyway. But it seems to me an odd difference in the css. listtopic also has this 16px right padding thing - but it seems to be used just for text display that is not in columns, so I did not mess with that. Changing this css fixes the lineup of the red "x" in the services status column and does not seem to break anything else. In theory it could make other things better also. Someone who knows how the css was intended to be used could comment on this! If I have got the right idea, and these "16px" things were just a mistake from the past, then it should be checked in the css for all themes and corrected appropriately... I am happy to do that, once someone confirms it is the thing to do.
* Typo CIDR in UPnP GUI pagePhil Davis2014-12-071-4/+4
| | | | As reported by johnpoz https://forum.pfsense.org/index.php?topic=84964.0
* Disable RC4 ciphers in lighttpdChris Buechler2014-12-051-2/+2
|
* Call filter_configure_sync() is a better fix for #4066, as pointed by ErmalRenato Botelho2014-12-051-3/+2
|
* Fix #4066:Renato Botelho2014-12-051-3/+12
| | | | | | | Make sure pf is configured before other services are restarted when WAN IP changes. The way it was before, 'pass out' rules with route-to still have old IP set as 'from' and some Dynamic DNS ended up not being updated.
* Add RELENG_2_2 to gitsyncRenato Botelho2014-12-051-0/+1
|
* Set text and color of Gateways Widget StatusPhil Davis2014-12-051-1/+5
| | | | | | | getstats.php calls functions.inc.php get_stats(), which calls get_gatewaystats(). get_gatewaystats() now returns the text for each field and an optional color separated by "/" - "text/color" e.g. "Online/#90EE90" Parse the the new format, separating out text and color. If color is specified, then also set it with jQuery to css.
* Explicitly pass gateway status and colorPhil Davis2014-12-051-1/+1
| | | | | | This code was passing a whole load of html to attempt to set various properties of the Gateways Widget Status column so that it would display the new status (Online, Offline...) and in the appropriate color. Now that I am using class=listr, the css fro listr already specifies white. Setting bgcolor in HTML does not override that. Pass both the status text and color as ordinary text, separated by "/". The consumer of this output can do their thing with jQuery to set the color as well as text of the element.
* 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
* dyn.dns.he.net uses a self-signed cert, disable verification for it.Chris Buechler2014-12-041-0/+1
|
* Don't try to launch 3gstats unless it's on a valid device.Chris Buechler2014-12-041-2/+4
|
* Proper CA certificates are in place to validate SSL in these cases where it ↵Chris Buechler2014-12-041-22/+3
| | | | previously couldn't be, remove disabling of verification.
* replace spaces with tabsChris Buechler2014-12-041-2/+2
|
* After discussion with Ermal, remove this to force consumers to send thingsChris Buechler2014-12-041-7/+0
| | | | | properly. I fixed the scenario in Unbound where it was sending IPs to these functions rather than an interface, so this has no functional diff.
* Don't include link-locals as unbound interface candidatesJean Cyr2014-12-042-3/+3
| | | | Unbound does not presently support link-local interfaces.
* The time has come - bump to 2.2-RCChris Buechler2014-12-041-1/+1
|
* Fix update url since now we have RELENG_2_2Renato Botelho2014-12-041-1/+1
|
* Proper fix was put on f658bacErmal LUÇI2014-12-041-1/+2
| | | | | | Revert "Can't skip this if booting, ends up breaking config. Ticket #4071" This reverts commit effb3a3cfe4e57b781f35ba8a145eb627014d8ce.
* Properly unset booting flags to allow dynamic ipsec tunnels to work correctlyErmal LUÇI2014-12-042-3/+6
|
* Provide friendly descr in error message in Interfaces AssignPhil Davis2014-12-041-1/+1
| | | | | I was doing drastic things testing some stuff, swapping WAN and OPT1 interfaces in Interfaces->Assign. I accidentally pressed Save when I had the same real device selected for both. Thankfully there was input validation! But I noticed that the error message reported just the names WAN and OPT1, but actual I had them named as different things. So the names in the error message did not match the names (friendly descriptions) in the table of interfaces. This change makes it display both like FRIENDLY_DESC (FRIENDLY_NAME) so there is less room for confusion.
* Put -4 in the right place in ntpq clockver command #4074Phil Davis2014-12-041-1/+1
| | | | | I had pasted it in here between "-c" and "clockvar", that was not good. That's all I have for #4074 (I hope)
* 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:)
* change the ordering of dhcpd_configure and unbound_configure here, claims on ↵Chris Buechler2014-12-041-3/+3
| | | | forum it fixes issue I can't seem to replicate.
* Merge pull request #1361 from phil-davis/patch-2Chris Buechler2014-12-041-2/+6
|\
| * Use IPv4 for ntpq if IPv6 not allowedPhil Davis2014-12-041-2/+6
|/ | | Forum: https://forum.pfsense.org/index.php?topic=84890.0
* Merge pull request #1360 from jean-m-cyr/masterChris Buechler2014-12-031-5/+7
|\
| * Link local interfaces don't have subnet.. don't create access-control statementJean Cyr2014-12-031-5/+7
| | | | | | | | | | | | Selecting link local interface for unbound causes invalid access-control statement in unbound config since link local address doesn't have subnet.
* | Can't skip this if booting, ends up breaking config. Ticket #4071Chris Buechler2014-12-031-2/+1
|/
OpenPOWER on IntegriCloud