HOWTO: pfSense 1.2.x Traffic Shaping with Squid Transparent Proxy
-
Is this still relevant with 2.0RC1? I assume it is so after every update I make the changes that it tells you to. Thanks
-
so what should be the order? install squid package first then traffic shaper or the other way around mess first with traffic shaper and install squid last
-
which will be the sequence of installation? do i need to configure first the traffic shaper or install the squid first?
-
Is it the same method for pfsense2.0 rc3. there are several instance of 127.0.0.1 in squid.inc among those which i required to change please explain in details alomg with the traffic shaping way
-
Waiting for the reply in pfsense2.0 rc3 I have installed squid with lusca with squid guard and in squid.inc there are 10 instances of 127.0.0.1 among those whic i required to change
-
Any comments on whether this works in Pfsense 2.0? It would be great to be shaping and caching on the same box.
-
The easy way Traffic Shaping with Squid Transparent Proxy
Add under Firewall RulesAction = Pass
Interface= LAN
Source= LAN subnet
Protocol = TCP
Source = LAN
Destination = any
Destination port range = (Squid Proxy port) eg. 3128Reason http port 80 has moved to the squid proxy port 3128
-
@hyrol - Thanks it works on 1.2.3. Ill test it on 2.1
-
The easy way Traffic Shaping with Squid Transparent Proxy
Add under Firewall RulesAction = Pass
Interface= LAN
Source= LAN subnet
Protocol = TCP
Source = LAN
Destination = any
Destination port range = (Squid Proxy port) eg. 3128Reason http port 80 has moved to the squid proxy port 3128
This works for me on 2.0.1 (tested with various speed settings). Also, you will already have this rule in place if you are have a Deny All rule and are using transparent proxy. So, it's a good idea to take advantage of the rule.
-
@argyx - This doesn't work, all HTTP traffic is still getting dumped into qlandef, which by default receives 1% bandwidth from the wizard.