summaryrefslogtreecommitdiffstats
path: root/src/usr/local/www/services_dhcp.php
Commit message (Collapse)AuthorAgeFilesLines
* Checks for DHCP Relay being enabled/disabled should be skipped when editting ↵Renato Botelho2017-04-271-11/+23
| | | | an additional pool
* Add missing $zone variabledoktornotor2017-02-251-0/+1
|
* Update BIND zones when adding static DHCP leases if needed (Bug #3710)doktornotor2017-02-251-0/+24
|
* Check that DHCP registration isn't enabled for DNS forwarder/resolver when ↵doktornotor2017-02-221-0/+10
| | | | disabling DHCP server
* GET/POST conversion - services part 1Steve Beaver2017-02-141-17/+12
|
* setHelp strings for services*Phil Davis2017-02-081-3/+3
|
* Part Fix #7233 Allow deletion of empty static map entriesPhil Davis2017-02-081-1/+1
|
* Required fields in Services pagesPhil Davis2017-01-301-1/+1
|
* Display client id in DHCP Mapping listPhil Davis2017-01-111-0/+27
|
* Merge pull request #3369 from phil-davis/breadcrumbs_detailRenato Botelho2017-01-111-0/+2
|\
| * Breadcrumb linksPhil Davis2017-01-101-0/+2
| |
* | Report problems applying changesPhil Davis2017-01-031-8/+7
|/ | | | | | | 1) Strictly keep track of the accumulating $retval from calls to various functions that apply changes. 2) Use new function print_apply_result_box() to print a suitable message in a suitable severity based on $retval
* Merge pull request #3307 from blkeller/ignore-client-uidsRenato Botelho2016-12-271-0/+9
|\
| * Add new "Ignore client identifiers" DHCP featureBrett Keller2016-12-221-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Exposes the underlying dhcpd configuration option "ignore-client-uids" in the pfSense "Services / DHCP Server" GUI by adding an "Ignore client identifiers" checkbox. As of ISC dhcpd version 4.3.0+, there is a new configuration statement available, "ignore-client-uids". According to the ISC's documentation, "If the 'ignore-client-uids' statement is present and has a value of 'true' or 'on', the UID for clients will not be recorded." While this behavior does not strictly adhere to the DHCP specification, it can be very useful in environments where devices on the network dual boot or PXE boot. Normally, if the network stacks in a single device's different operating systems (including PXE firmware) make DHCP requests with differing client identifiers, the server will treat each request with a unique identifier as having come from a unique client, even when they come from the same device. Thus, different operating systems on the same device and NIC might hold different leases with different IP addresses. Once activated, the "ignore-client-uids" option tells the DHCP server not to record client identifiers in new DHCP leases, which forces the server to fall back on hardware (MAC) addresses to uniquely identify clients. Now different operating systems on the same device and NIC will hold the same lease (based on MAC address), which should keep a device's IP address consistent regardless of its currently running operating system. Same as with most other general and pool-specific DHCP server options in pfSense, note that turning on this option only affects new leases. Any leases that existed prior to enabling this option will still contain their respective client identifiers. Manually deleting older leases or flushing the entire lease table can expedite a full migration to the new server behavior, if desired.
* | Merge pull request #3248 from phil-davis/ipaddressnopatternRenato Botelho2016-12-271-4/+4
|\ \
| * | Form_IpAddress add types remove patternsPhil Davis2016-12-031-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1) Add alias and host types to Form_IpAddress with the appropriate hover text. 2) Remove the patterns - the UI of those is not so effective anyway, so leave the validation of input to the back end. 3) Update uses of Form_IpAddress to use the appropriate Alias or Host type as needed. 4) Remove explicit setPattern() from those uses of Form_IpAddress.
* | | Modify DHCP Server messagesPhil Davis2016-12-241-3/+5
| | |
* | | Customize DHCP Server on interfaces messagePhil Davis2016-12-241-3/+12
| | |
* | | Fix field type for TFTP in DHCP server settingsjim-p2016-12-231-0/+1
| | |
* | | Disable DHCP server on interfaces with subnet >= 31. Fixes #6930Renato Botelho2016-12-201-7/+23
| |/ |/|
* | DHCP server edit when DHCP Relay enabledPhil Davis2016-12-131-185/+194
|/ | | | | | | | | | | | | | | | | | | Part of Redmine #6997 1) Display the DHCP Server settings even when DHCP Relay is enabled, but disable the "enable" checkbox in this case - so the user cannot enable DHCP Server when DHCP Relay is enabled, but can view and modify the DHCP Server parameters (ready for the day they want to use it). 2) Actually validate the POSTed DHCP Server parameters, even if it is disabled. Previously you could put rubbish values in fields and they would be "happily" saved when DHCP Server was disabled. We want users to be able to setup DHCP Server ready-to-enable and knowing that they have put validated stuff in. 3) When DHCP Server is disabled, allow Range From and Range To to be left empty. When first setting up parameters (e.g. with the UI page up for the first time) it is OK for the user to be able to just press "Save". e.g. they are just pressing Save as a way to get out (as if it is a Cancel button). We do not need to force them to enter range from/to IP addresses.
* Clarified help text for ddnsforcehostname option.Ross Williams2016-11-301-1/+1
|
* Added title to ddnsforcehostname checkboxRoss Williams2016-11-301-1/+1
|
* Add ddnsforcehostname option to DHCP Server configuration editorRoss Williams2016-11-291-1/+11
|
* Improve IPv4 address validation for services_dhcpPhil Davis2016-10-201-14/+25
| | | | The input pattern that goes with Form_IpAddress by default allows for IPv4 and IPv6 valid characters. The back-end validation here is checking for IPv4 addresses, so it seems reasonable that the front-end input pattern checks might as well be restricted to the IPv4 valid characters. Unneeded setPattern have also been removed. The exception is Gateway, where the special string "none" is allowed, so I just left the setPattern as it is (yes, it could be modified to only allow the letters "n" "o" and "e").
* Merge pull request #3151 from EdHurtig/eng/6806Renato Botelho2016-10-121-2/+2
|\
| * Allow Hyphens in DHCP NTP Server form validationEddie Hurtig2016-09-221-2/+2
| | | | | | | | | | | | | | Also removes the ability to have underscores `_` in ntp server FQDNs. Closes #6806
* | Typo staicPhil Davis2016-09-291-1/+1
| |
* | Apply static ARP entries more consistently when adding and removing static ↵jim-p2016-09-281-0/+4
|/ | | | mapping entries. Fixes #6821
* Move copyright from ESF to NetgateRenato Botelho2016-09-061-1/+1
|
* Merge pull request #3083 from doktornotor/patch-2Renato Botelho2016-08-041-4/+4
|\
| * Allow URLs for TFTP Server (Bug #6634)doktornotor2016-07-311-2/+2
| | | | | | The setPattern() thing ain't usable for this and just causes regressions.
| * Typo fixdoktornotor2016-07-311-1/+1
| |
| * Allow URLs for TFTP Server (Bug #6634)doktornotor2016-07-311-2/+2
| | | | | | is_URL() from util.inc is way too limited for this purpose.
* | services_dhcp: Ignore BOOTP queriesJose Luis Duran2016-07-311-0/+9
|/ | | | | | | | | BOOTP leases do not have a maximum lease time by default, this could potentially lead to a DHCP address pool exhaustion. This commit adds an option to ignore BOOTP queries. Redmine #4351
* Clarify that HMAC-MD5 key is required. Ticket #6622Chris Buechler2016-07-171-1/+1
|
* Move to Apache License 2.0Renato Botelho2016-07-151-41/+9
|
* Review license / copyright on all files (final round)Renato Botelho2016-07-151-43/+42
|
* Fix #6050 DHCP - provide Network Booting display/hide advanced buttonPhil Davis2016-07-091-51/+97
| | | This one moves the "Network Booting" above the "Additional BOOTP/DHCP Options". That allows "Network Booting" to be a Display/Hide Advanced group of buttons just like TFTP, LDAP etc. (without a special section header) and for "Additional BOOTP/DHCP Options" to come last on the page.
* Always use require_oncePhil Davis2016-06-271-1/+1
| | | | | | | | | The usage of require() and require_once() throughout the system is inconsistent, and "bugs" come up now and then when the order of "requires" is a bit different and some require() happens after the include file is already included/required. It seems to me that there is no harm at all in always using require_once().
* Fixed #6504 by making table sortableStephen Beaver2016-06-221-1/+1
|
* Allow - in TFTP Server field. Ticket #6433Chris Buechler2016-06-011-1/+1
|
* Miscellanous Textual Corrections - Add missing dots, normalize caseNewEraCracker2016-05-111-3/+3
|
* Fix missing interface in pool edit. Ticket #6303Chris Buechler2016-05-021-1/+1
|
* Hostnames are valid for NTP servers in DHCP Server. Ticket #6239Chris Buechler2016-04-231-4/+4
|
* Services - PunctuationNOYB2016-04-211-9/+9
| | | | Clean up some services menu punctuation.
* Services / DHCP Server - DNS Servers ClarificationNOYB2016-04-121-1/+1
| | | | It reads as though the interfaces IP address is to be entered. Removing "use" makes it a little clearer.
* Services / DHCP - Remove PersonalizationsNOYB2016-03-301-14/+14
| | | | Remove "you" personalizations.
* Reengineer Form_Button setAttributePhil Davis2016-03-201-18/+6
| | | | | | As per what was done for https://github.com/pfsense/pfsense/pull/2765 - do it to the rest of them. Seems to work OK.
* HTML Compliance - Services / DHCP ServerNOYB2016-03-171-1/+1
| | | | Error: The align attribute on the td element is obsolete. Use CSS instead.
OpenPOWER on IntegriCloud