Changes

PFSense and OPNsense

1,191 bytes added, 4 February
/* Troubleshooting */
The following lines were added (+) and removed (-):
Per HOST or Per USER note:  pfBlockerNG is not the best way to providing filtering while exempting specific hosts on the network.  Although possible, it is problematic and difficult to configure.== Troubleshooting ===== The following CA/Certificate entries are expiring ===Beginning with 2.5.0 pfSense also allows you to renew the certificate in the web GUI in System > Certificate Manager > Certificates.* Certificates are managed from System > Cert Manager, on the Certificates tabUsing pfSense as a Certificate Authority for your network:  For network Chain of Trust.=== Force a DHCP lease to expire without impacting all other client leases ===If you give a static lease assignment after a client already has a dynamic lease, and you wish to trigger that client workstation or device to stop using the old dynamic IP from the previous lease and start using the new IP that was static mapped for it, without having physical access to the client device... here is what you do:# In the GUI, go to Diagnostics/Edit File and load /var/dhcpd/var/db/dhcpd.leases~# Do the same for /var/dhcpd/var/db/dhcpd.leases# goto Services -> DHCP Server and RESTART the DHCP server service.
Bureaucrat, administrator
16,192
edits