summaryrefslogtreecommitdiffstats
path: root/src/etc/inc/services.inc
Commit message (Collapse)AuthorAgeFilesLines
...
* s/ip/IP/ it got lost on revert. Spotted by @phil-davisRenato Botelho2015-10-141-1/+1
|
* Revert "remove the destination server's interface(s) from dhcrelay. Ticket ↵Renato Botelho2015-10-141-4/+133
| | | | | | #4908" This reverts commit f791f28d6794c3b0601259f0de7acdebf6a367a8
* Use product_name global variable in more placesRenato Botelho2015-09-301-2/+2
|
* Disable DHS as a dynamic DNS provider option. It's never worked, andChris Buechler2015-09-291-2/+2
| | | | | | | 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.
* Redmine #5200 be less aggressive about DHCP Pool Notice V2Phil Davis2015-09-281-2/+21
| | | | | | 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.
* Redmine #5046 UEFI network booting arch 00:09Phil Davis2015-09-171-0/+2
|
* Merge pull request #1848 from phil-davis/bootstrap-reviewjim-p2015-09-021-26/+32
|\
| * Integrate bootstrap etc/inc with masterPhil Davis2015-08-301-26/+32
| | | | | | | | | | | | This applies the little changes in etc/inc master to the bootstrap branch so that etc/inc in bootstrap will now just have the real differences that are due to real bootstrap changes.
* | Merge branch 'master' into bootstrapRenato Botelho2015-09-011-1/+14
|\ \ | |/ |/|
| * Merge pull request #1824 from phil-davis/dhcp-pools-rangeRenato Botelho2015-08-281-0/+8
| |\
| | * Ignore DHCP pools that are out of rangePhil Davis2015-08-261-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If the user changes the subnet of an interface then applies without adjusting the DHCP pool range/s to be in the new subnet, then an invalid dhcpd.conf is generated. The DHCP server complains about it and exits. If you have only 1 LAN with DHCP then it does not make a difference - you are not going to get DHCP whatever happens because there is no valid pool data. But if there are multiple LAN-style interfaces with DHCP then you can cause no DHCP-service on LAN when you are messing with settings on OPT1/OPT2... I did this to myself last night, and even after rebooting got no DHCP for either my LAN or OPT1, just because the OPT1 pool settings were bad. This change checks that the pool ranges are in the interface subnet. If they are not, then they are excluded from dhcpd.conf and a notice os filed. The user gets the flashing notice stuff on the webGUI to tell them what is wrong. And any other good DHCP interfaces+pools continue to work. This is a resubmit of PR #1783 after integrating to the current master.
| * | Indentation fixdoktornotor2015-08-281-1/+1
| | |
| * | make sure that cron is running before reconfiguring itdoktornotor2015-08-281-0/+5
| |/ | | | | | | | | This is a resubmit of #1814. (When cron goes away for whatever reason, you can keep reconfiguring it till blue in face but nothing will happen.)
* | Merge branch 'master' into bootstrapRenato Botelho2015-08-261-34/+28
|/
* Move main pfSense content to src/Renato Botelho2015-08-251-0/+2541
OpenPOWER on IntegriCloud