| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
was removed some time ago.
|
|
|
|
| |
unintentionally on a system that doesn't need it.
|
|
|
|
| |
menu. Ticket #6045
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| | |
These should be strings in quotes, otherwise PHP looks for them to be
constants and would be issuing notice level "errors" underneath.
|
|/ |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
redmine. Fixes #7047
Added:
The firewall platform and serial number
ARP Table
NDP Table
Gateway status (See #7046)
ZFS disk/pool info
gmirror status
Limiter info
Load balancer info
Also fixed the captive portal code to show IPFW rules
Reorganized output filenames
Added a new exec method to call a PHP function rather than a shell exec, required to get the gateway status to work efficiently.
|
| |
|
|
|
|
| |
status, for use by a shell script and status.php. Ticket #7046
|
|
|
|
| |
#7045
|
|\ |
|
| |
| |
| | |
While looking at notices.inc I noticed (pardon the pun) that notify_all_remote did exactly the same as these 2 lines of code. notify_all_remote() might as well be used here, to save having the same code repeated.
|
|\ \ |
|
| |/
| |
| |
| | |
When looking into how the notices features work these days, I found that these functions are no longer used anywhere.
Maybe they should be deleted?
|
|\ \ |
|
| | | |
|
| |/
| |
| |
| | |
This looks to me like the var name here should be $category
Note: I don't see where this get_notices() inside class pfsense_xmlrpc_server is ever unused anyway - so maybe get_notices() can just be deleted from here?
|
|\ \ |
|
| |/
| |
| |
| | |
If the user does not have access to index.php then the "Mark All as Read" button for the notices popup does not work for them anyway, so do not show it.
This fixes the obvious UI inconsistency - where the user has a button that they press, but it is not effective.
|
|\ \
| |/
|/| |
|
| | |
|
|/ |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| | |
Add a function to disconnect all logged in users and a button to call it in the captive portal status page.
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
|\ \ \ |
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
dhcpv6_pd_str_help
Add case for 59 to prefix functions merge_ipv6_delegated_prefix / dhcpv6_pd_str_help
|
| | | | |
| | | | |
| | | | | |
Maybe these functions should have a case added for prefix length 59?
|
| |/ / /
| | | |
| | | |
| | | | |
client does
|
| | | | |
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
1) util.inc - add parameter to get_staticroutes() so the caller can
choose to see all static routes or only the ones that are currently
enabled.
2) filter.inc - just process enabled static routes when making direct
networks list, tonathosts etc.
3) services.inc - only include enabled static routes when making confogs
for DHCP(6) Relay.
4) unbound.inc - only include enable static routes in
unbound_acls_config
5) rc.newroutedns - only trigger if there is an enabled static route.
Note: GUI validation has been left as-is. e.g. in system_gateways we don
not allow to delete a gateway if there is a disabled static route using
it... If people want to delete "higher level" stuff, then they need to
first delete the disabled static route(s). Otherwise it will get rather
"risky" having disabled static routes in the config that refer to
gateways that no longer exist, or have a subnet range that now matches a
local interafce or...
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Make $use_filterdns a parameter. It needs to be persistent across
recursive calls otherwise it ends up not adding necessary items to
filterdns depending of how items are sorted
|
| | | | | |
|
|\ \ \ \ \ |
|
|/ / / / /
| | | | |
| | | | | |
Now that Form_IpAddress() supports a range of types of input, this can be specified as HOSTV4.
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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.
|
|\ \ \ \ \ \ |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
in the status page
|
|\ \ \ \ \ \ \
| |_|_|/ / / /
|/| | | | | | |
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | | |
If I enter a DNS server IP address that is on a locally connected network, and choose a gateway for it, this code was supposed to give an error message. But no error was given because $_POST[$dnsgwitem] is actually the name of the gateway, but old line 197 called interface_has_gateway() which was expecting an interface to be passed.
Just get rid of the interface_has_gateway() test, and come into this foreach() whenever the users chooses a gateway that is not "none".
|