Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.
Message icon:

(Clear Attachment)
(more attachments)
Restrictions: 35 per post, maximum total size 3000KB, maximum individual size 500KB
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
Who runs this web-site?:

shortcuts: hit alt+s to submit/post or alt+p to preview

Topic Summary

Posted by: Edd Noman
« on: April 16, 2017, 09:28:04 PM »

HOW-TO: Use pfSense to separate WebBrowsing and Gaming traffic:

1. Get 2 different ISP connection so you can split and separate the traffic you have out 2 different Gateways

2. Configure and define your WAN1 and WAN2 interfaces in pfSense

3. Configure and define 2 different Gateways in pfSense also removing the "Default" Gateway option from the system.

4. Define what PORTS are used for GAMING traffic and put them in a PORT type Alias  (lots of testing and failing is needed to get this right)

5. Define what IPs is being used by GAMING traffic and put them in a HOST type Alias  (lots of testing and failing is needed to get this right)

6. Create a Alias for WebBrowsing PORTS TCP 80 and TCP 443 for HTTP and HTTPS websites

7. Delete all current Firewall Rules on LAN interface as they can conflict whit the separations of the traffic and the PBR Rules needed to set this up (I recommend enabling the anti-lockout rule before you do this or you will lose access to your firewall)

8. Create Firewall Rule for GAMING Traffic: Pass TCP\UDP from Source: LAN NET to Destination Alias: GamingIP on Ports Custom: GamingPorts then use Gateway: WAN1

9. Create Firewall Rule for WebBrowsing Traffic: Pass TCP from Source: LAN NET to Destination: Any on Ports Custom: BrowsingPorts then use Gateway: WAN2

10. Save, Apply and then Reboot your firewall, test and adjust the GamingIP and GamingPort Aliases as needed to add \ remove connectivity for a game as per needed basis

If you follow this guide and it is not working for you and it broke your system, I am not responsible or liability for that as you should not take anything you read on the internet at face value and you should test settings like this in a lab environment and not on your production servers.