HOWTO: pfSense 1.2.x Traffic Shaping with Squid Transparent Proxy

Meulator

Hey there,

something i didn't get… in squid.inc, do i have to change every "127.0.0.1" by "my.pfsense.lan.ip" ? Or only 3 times?

Cause i tried by changing all, changing the default https port & firewall rule, rebooted the pfsense box... and then i could not get the capitve portal page...

javerleo

Thanks iBeej.
This hack is what I've been looking for a long time ago. It worked fine on pfsense 1.2 but now squidguard filter rules seem not to be working.
Some clues?

i_robot73

This seemed to work for me:

add

function squid_resync_general() {
	global $g, $config, $valid_acls;

	$WAN_IP = "0.0.0.0.0";
	foreach (explode(",", $ifaces) as $i => $iface) {
		$real_ifaces[] = squid_get_real_interface_address($iface);
		if($real_ifaces[$i][0]) {
			$WAN_IP = "{$real_ifaces[$i][0]}";
		}
	}

Change things like:

if (($settings['transparent_proxy'] == 'on')) {
		$conf .= "http_port 127.0.0.1:80 transparent\n";
	}

to

if (($settings['transparent_proxy'] == 'on')) $conf .= "http_port {$WAN_IP}:80 transparent\n";

lifeboy

You said this worked for you, but:

@i_robot73:

function squid_resync_general() {
	global $g, $config, $valid_acls;

	$WAN_IP = "0.0.0.0.0";
	foreach (explode(",", $ifaces) as $i => $iface) {
		$real_ifaces[] = squid_get_real_interface_address($iface);
		if($real_ifaces[$i][0]) {
			$WAN_IP = "{$real_ifaces[$i][0]}";
		}
	}

Why do you use $WAN_IP here? I thought we are looking to let squid send traffic to LAN_IP?

I have rules on the LAN (to provide loadbalancing/failover), which are also not triggered when running a transparent proxy. So changing to WAN_IP above will not be the same as the hack that was described at the top of this post.

The you say:

@i_robot73:

Change things like:

if (($settings['transparent_proxy'] == 'on')) {
		$conf .= "http_port 127.0.0.1:80 transparent\n";
	}

to

if (($settings['transparent_proxy'] == 'on')) $conf .= "http_port {$WAN_IP}:80 transparent\n";

Does this mean that the references below need to be changed as well?

acl localhost src 127.0.0.1/255.255.255.255

and

foreach ($ifaces as $iface) {
$rules .= "rdr on $iface proto tcp from any to !($iface) port 80 -> 127.0.0.1 port 80\n";
}
/* Handle PPPOE case /
if($config['pppoe']['mode'] == "server" && $config['pppoe']['localip']) {
$rules .= "rdr on $PPPOE_ALIAS proto tcp from any to 127.0.0.1 port 80 -> 127.0.0.1 port 80\n";
}
/ Handle PPTP case */
if($config['pptpd']['mode'] == "server" && $config['pptpd']['localip']) {
$rules .= "rdr on $PPTP_ALIAS proto tcp from any to !127.0.0.1 port 80 -> 172.0.0.1 port 80\n";

Please comment, since this seems a little mixed up to me.

dondos

I also tried this hack. I changed every instance of 127.0.0.1 with 192.168.10.1 (my LAN ip address):


Search "192.168.10.1" (9 hits in 1 files)
	Line 603: 		$conf .= "http_port 192.168.10.1:80 transparent\n";
	Line 766: acl localhost src 192.168.10.1/255.255.255.255
	Line 1285: 				$rules .= "rdr on $iface proto tcp from any to !($iface) port 80 -> 192.168.10.1 port 80\n";
	Line 1289: 				$rules .= "rdr on $PPPOE_ALIAS proto tcp from any to !192.168.10.1 port 80 -> 192.168.10.1 port 80\n";
	Line 1289: 				$rules .= "rdr on $PPPOE_ALIAS proto tcp from any to !192.168.10.1 port 80 -> 192.168.10.1 port 80\n";
	Line 1293: 				$rules .= "rdr on $PPTP_ALIAS proto tcp from any to !192.168.10.1 port 80 -> 192.168.10.1 port 80\n";
	Line 1293: 				$rules .= "rdr on $PPTP_ALIAS proto tcp from any to !192.168.10.1 port 80 -> 192.168.10.1 port 80\n";
	Line 1306: 				$rules .= "pass in quick on $PPPOE_ALIAS proto tcp from any to !192.168.10.1 port $port flags S/SA keep state\n";			
	Line 1309: 				$rules .= "pass in quick on $PPTP_ALIAS proto tcp from any to !192.168.10.1 port $port flags S/SA keep state\n";

but I ended up with a state table table full with almost 60.000 connections:

I think I´ve done something wrong…

Hulk-pingu_3223.png_thumb

cylent

i have 1.2.3-release and this REALLY slowed my net and webgui management to a crawl!!!

either it doesnt work with 1.2.3 or i did something wrong.

pls advise

rdlugosz

So I'm using 1.2.3 with the transparent proxy enabled (and verified on b/c it's showing hits in the lightsquid logs). I am NOT seeing the behavior described in the first post. On my system, I see P2P traffic in the P2P queues and web traffic seems to go into the qOthersDownH queue.

Also curious is that I do not see any packets in my queues related to my VoIP adapter now that I've re-run the wizard and gave it the IP Address of the adapter. One of the first rules is that anything on that IP routes to the qVOIP queues… I saw some traffic being registered there when it was just set up to route the SIP port packets to those queues, but for whatever reason it doesn't show up when the whole IP is sent there.

Anyway, my main point in posting is to say that I'm NOT seeing the behavior of web traffic going to the default queues due to the proxy. It's possible that I've got something configured incorrectly, but it appears that the shaper is doing its job. Any thoughts?

moonspud

Does this work with penalty ip shapping?

udhaya

Hello iBeej,

I tried as you said, I am able to penalize the download and not the upload. Is there anything I need to follow. Please suggest me with more ideas. I am new to this.

Ver: 1.2.3-Release

bailer

I installed 1.2.3 and followed this guide. I noticed that there is 9 entries of 127.0.0.1 in the conf file instead of 3 but by reviewing the code abit I only changed the first 3 entries of 127.0.0.1 to the gateway IP and everything seems to be working fine for me!

splippity

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

kirlox_kitoy

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

kirlox_kitoy

which will be the sequence of installation? do i need to configure first the traffic shaper or install the squid first?

anagh

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

anagh

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

tacfit

Any comments on whether this works in Pfsense 2.0? It would be great to be shaping and caching on the same box.

hyrol

The easy way Traffic Shaping with Squid Transparent Proxy
Add under Firewall Rules

Action = Pass
Interface= LAN
Source= LAN subnet
Protocol = TCP
Source = LAN
Destination = any
Destination port range = (Squid Proxy port) eg. 3128

Reason http port 80 has moved to the squid proxy port 3128

jigpe

@hyrol - Thanks it works on 1.2.3. Ill test it on 2.1

argyx

@hyrol:

The easy way Traffic Shaping with Squid Transparent Proxy
Add under Firewall Rules

Action = Pass
Interface= LAN
Source= LAN subnet
Protocol = TCP
Source = LAN
Destination = any
Destination port range = (Squid Proxy port) eg. 3128

Reason 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.

ScottNJ

@argyx - This doesn't work, all HTTP traffic is still getting dumped into qlandef, which by default receives 1% bandwidth from the wizard.