Project

General

Profile

Actions

Bug #6486

closed

Squid fails in transparent proxy mode

Added by Allan Levene about 9 years ago. Updated about 9 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
Squid
Target version:
-
Start date:
06/13/2016
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:

Description

Squid 0.4.18 offers transparent proxy capability under 2.3.1-RELEASE-p1 (latest version) by checking a box - Enable transparent mode, to forward all requests for destination port 80 to the proxy server without any additional configuration being necessary.

I've noticed that when I listen to the radio through my PC when transparent mode is enabled, the radio stops. When transparent mode is stopped, the radio starts again. I'm not sure why port 80 affects the radio, but it does. No amount of bypassing the transparent mode by using these two bypass fields makes a difference -

Bypass Proxy for These Source IPs

Bypass Proxy for These Destination IPs

The only "fix" is to disable transparent mode. Sadly, only one version of Squid is available under 2.3.x.

Ideas?

Actions #1

Updated by Jim Pingle about 9 years ago

  • Status changed from New to Not a Bug
  • Target version deleted (2.3.2)

Not a bug. Post on the forum for help with your configuration.

Actions #2

Updated by Allan Levene about 9 years ago

I reread the forum articles about this bug. The general consensus was that Squid has been broken in the past. My belief is that this sole version available for the latest pfSense release was fixed.

If you know of the article that specifically addresses why transparent proxy of port 80 works fine but radio receipt via another port that transparent proxy shouldn't touch stops when it's turned on, please post that link to this bug fix request.

It looks like a bug to me.

Actions #3

Updated by Jim Pingle about 9 years ago

This is a configuration issue, not a bug. If your client protocol does not work properly, it's probably not speaking HTTP on port 80, so you'll have to setup some sort of bypass, which is a configuration issue. Even if it is HTTP and not working properly, it's either something else that needs solved in your squid configuration or perhaps a problem in squid itself, but not a problem in the pfSense squid package. If you can point to a specific forum thread that identifies a bug in the pfSense squid package code, then a bug entry can be opened. Until then, the discussion should be kept on the forum only. If it's a bug in squid itself, it must be reported directly to squid.

Actions

Also available in: Atom PDF