Project

General

Profile

Feature #579

Restricting Bandwidth To A Single IP Address With pfSense

Added by Daniel Curtis over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Firewall/Router
Target version:
Start date:
03/08/2015
Due date:
% Done:

100%

Estimated time:
0.50 h
Spent time:

Description

This is a simple guide for restricting bandwidth usage of a single IP address on pfSense 2.2. Start by logging into the pfSense admin panel.

Create the Limiters

  • Open Firewall -> Traffic Shaper -> Limiter.
  • Select Create new limiter.
  • Create the first limiter named uploadThrottle.
    • Click Enable limiter and its children .
    • Enter Name uploadThrottle.
    • In the bandwidth section, click on the [+] and enter 5, and set Bw type to Kbit/s
    • In the Mask section, use pull-down menu and select Source addresses and the IPV4 mask bits enter 32.
    • Enter a Description
    • Click Save
  • Create the second limiter named downloadThrottle.
    • Click Enable limiter and its children .
    • Enter Name downloadThrottle.
    • In the bandwidth section, click on the [+] and enter 28, and set Bw type to Kbit/s
    • In the Mask section, use pull-down menu and select Source addresses and the IPV4 mask bits enter 32.
    • Enter a Description
    • Click Save

NOTE: This will effectively create a limiter with the speed equivalent to a dialup connection. Adjust accordingly

Setup The Firewall Rule

  • Open Firewall -> Rules -> LAN.
  • Select [+] Add new rule.
    • In the Source Type pull-down menu select Single host or alias
    • In the Source Address enter the IP Address of the host being throttled.
    • Set the Destination to Any.
    • In the Advanced In/Out section click on Advanced, then set uploadThrottle / downloadThrottle
    • Click Save
  • Click on Apply

NOTE: Once the rule is in effect the IP address set will have a throttled connection.

History

#1 Updated by Daniel Curtis over 5 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

#2 Updated by Daniel Curtis over 5 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF