Bobcares

pfSense Anti Lockout Rule | Setup Guide

by | Nov 23, 2022

Let’s look into the details of anti lockout rule in pfSense. Bobcares, as a part of our Server Management Services, offers solutions to every query that comes our way.

The Anti-lockout rule in pfSense

pfSense has an anti-lockout rule by default to prevent admins from being locked out of the web interface. We can set it up under Anti-lockout on the System >> Advanced page. This automatically applied rule allows traffic from any source within the network to any firewall admin protocol listening on the LAN IP address.

We must disable it and modify the LAN rules for environments that need more security. So that only an alias of trusted hosts can use the admin interfaces. We can disable it easily by going to System >> Advanced >> Admin Access tab. Check Disable webConfigurator anti-lockout rule. And when we click the Save option, the rule will no longer exist.

How to set up the Anti-lockout rule in pfSense?

We can set up the rules as needed to restrict access to the admin interface. So we are taking an example.

1. Here, we must make a ManagementPorts alias containing SSH and HTTPS ports. Because SSH and HTTPS are used for management.

2. Now, for hosts and/or networks that will have access to the admin interfaces, create an alias.

3. The Alias List will appear then.

4. The LAN firewall rules must then be set up to enable access to the previously identified hosts. Also, deny access to everyone else. There are several methods for this, depending on the context and outflow filtering treatment. Now the firewall rules are configured.

5. Go to the System >> Advanced page and disable the WebGUI anti-lockout rule.

6. Finally, mark the box and click Save.

If the admin interface is no longer accessible after disabling the anti-lockout rule, the firewall rules were not properly set up. Re-enable the anti-lockout rule by selecting Set Interface(s) IP address from the console menu, then selecting Reset LAN IP address. We must set it to its current IP address, and the rule will be re-active immediately.

[Searching for a solution to a different question? We’re available 24/7.]

Conclusion

In this article, we provide the steps to set up the anti-lockout rule on pfSense. We also included the steps from our Tech team to enable/disable it.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF