Bobcares

Remote Access Pfsense WebGui Via SSH Tunnel: How To?

by | Jun 22, 2023

Let us look at how to set up Remote Access Pfsense WebGui  Via SSH Tunnel with the support of our pFsense support services at Bobcares.

Setup SSH Tunnel On Pfsense for Remote Access

Remote Access Pfsense WebGui Via SSH Tunnel

The default configuration of pfsense does not enable SSH access, so we need to activate it first and then allow it through firewall rules for WAN access. Let’s proceed with the steps one by one.

Log in using the admin credentials to the pfsense firewall, and if we are using the pfsense default credentials, such as username admin and password pfsense, change the password to something strong.

To change the password, go to System-User Manager from the top menu, then Users, then the pencil symbol (Edit) for admin under Actions, and then change the default password.

Assuming the password is now something more secure, let’s enable SSH access. To do so, go to System-Advance, then pick the Admin Access tab, and scroll down to the Secure Shell section.

Enable Secure Shell by checking the option, then save the settings with the default parameters.

Enable Pfsense secure shell

It is better to grant Strict Access to the Pfsense Web Interface IP. Create a list of IP addresses that will be authorized to visit the pfsense web Interface address from the outside for a Strict visit.

Firewall Rule For Remote SSH Access

By default, pfsense employs a firewall rule known as the Anti Lockout Rule, which restricts remote access to the pfsense web interface while simultaneously preventing the user from being locked out of the firewall if the firewall rules are incorrectly set.

We have to disable this rule in order to allow remote web access.

To disable it, go to the main menu System>Advance and uncheck Disable webConfigurator anti-lockout rule on the Admin Access Tab.

As the last step in Remote Access configuration, we must establish a firewall Pass rule and use Alias in the authorized Source box, as seen in the picture below.

How to create a firewall rule?

To create a firewall rule, go to the top menu and pick Firewall-Rules, then the WAN Interface, and finally Add.

Allow Remote SSH firewall rule for Remote Access in Pfsense.

As we wish to enable SSH communication from the distant WAN, we set Action: to PASS.

WAN interface, which will be our local WAN interface.

TCP as SSH uses TCP port 22 by default.

Source: Single host or Alias; we will select Remote_WAN_IPs since it will appear when we begin inputting the name of our Alias.

Destination: This Firewall (self) reflects our firewall’s Management IP Address.

Once we’ve finished inputting your setup settings, click the Save button to finish the configuration.

[Need assistance with similar queries? We are here to help]

Conclusion

To sum up we have now seen how to set up the Remote Access Pfsense WebGui  Via SSH Tunnel with the support of our tech support team.

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