pfSense

Set up Policy Based Routing with pfSense based on destination

- by Vikash Jhagroe - Leave a Comment
Reading Time: < 1 minute

In this video, I will show you how to set up Policy Based Routing with pfSense based on destination. A destination can be a URL, hostname, FQDN, or even complete networks based on IP ranges or ASNs. I will show you how to set this up using aliases I create with the pfBlockerNG package on pfSense. To read more about using aliases on pfSense, click here. I am using pfSense 2.7.2 to do this, but the same idea applies to other versions of pfSense.

(Visited 373 times, 1 visits today)

Related posts:

  1. Migrate from pfSense Plus to pfSense CE on your own hardware
  2. Set up Policy Based Routing with pfSense based on client IP
  3. pfSense with routed IPTV and OpenVPN client for private internet access
  4. Protect VMware vCenter management interface with a reverse proxy and LetsEncrypt certificate

Related Posts

Redirect all DNS requests with pfSense to Pi-Hole or AdGuard Home_thumb

Redirect all DNS requests with pfSense to Pi-Hole or AdGuard Home

Set up AdGuard Home on pfSense for adblocking and tracking protection

Set up AdGuard Home on pfSense for ad-blocking and tracking protection

Adding custom domains to block with pfBlockerNG and pfSense

Adding custom domains to block with pfBlockerNG and pfSense

About Vikash Jhagroe

Equipped with more than 15 years of experience working on applications and systems, Vikash is a master at connecting businesses with the tech that is right for them. He is passionate about computers and computer systems, and he is committed to serving his clients well. He is a tech-wizard.

View all posts by Vikash Jhagroe →

Leave a Reply

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.