And also by replacing port 192.168.13.1:3128 with 3128
Now squid tells that it listens to 0.0.0.0:3128, which seems not very right,
but it works
Wed, 21 Mar 2012 15:22:25 +0400 от zozo zozo :
> Resolved by allowing port 3128 in iptables for ppp0.
> For eth0 it for some reason wasn'
Resolved by allowing port 3128 in iptables for ppp0.
For eth0 it for some reason wasn't required - allowing ESTABLISHED was enough
Tue, 20 Mar 2012 15:53:57 +1300 от Amos Jeffries :
> On 20.03.2012 15:30, zozo zozo wrote:
> > Hi all
> >
> > I've setup squid and it
Hi all
I've setup squid and it works if I forward network from eth0 to wlan0 (ap mode)
But if instead of ethernet I try to use ppp0 packets, squid doesn't forward
stuff, and in access log entries were something like 0_ABORTED (don't have
those logs at hand, will provide more info tomorrow)
Ports
Anyway, squid.pid isn't cleared in case of such exit, and squid -k ...
complains on non-existent process
Tue, 20 Mar 2012 01:57:37 +0400 от zozo zozo :
> OK, if anyone encounters this, the interface that had the IP wasn't up at the
> moment (it's wireless and is cfg-ed via
e it helps :)
Mon, 19 Mar 2012 13:59:42 +0100 от Fried Wil :
> Hi Igor,
>
> Any same port is open ?
>
> Squid works on 3128/tcp or other ?
>
> Could you netstat -anop | grep PORT to know if u have any other software
> tooks the same port.
>
> On Mon, Mar 19, 2
That's what I get in syslog. squid starts, then dies after a few seconds. Cache
log doesn't show anything about exit reasons.
userdemo@ubuntu-demo:~$ sudo cat /var/log/syslog |tail
Mar 19 16:01:01 ubuntu-demo (squid-1): Unable to open HTTP Socket
Mar 19 16:01:01 ubuntu-demo squid[1173]: Squid Par
> > I.e. I can't put my transparent proxy to internet, I need it to be in
> > same IP space as my network interface?
>
> You can put it anywhere you like. There are only two requirements:
>
> 1) NAT happens on the same OS.
> So Squid can have direct access to the NAT data to undo the
> d
> > Does it mean that now intercepting squid can only work on the gateway
> > machine?
>
> No. It means that routers like yours need to be configured for policy
> routing (aka "packet forwarding") instead of NAT port mapping (aka "port
> forwarding").
>
> This config was written particularly fo
rding from DD-WRT router to
the server, obviously I can't have squid on router.
On Ubuntu I have Squid v3.1.11, is it new feature in 3.2?
18 октября 2011, 06:57 от Amos Jeffries :
> On Tue, 18 Oct 2011 04:14:28 +0400, zozo zozo wrote:
> > Port 80 is redirected from another machine
> Maybe I am missing it, but where is the rule to REDIRECT port 80 to 13128
> in iptables ?
>
> Cheers,
>
> Pieter
>
> On Tue, 18 Oct 2011, zozo zozo wrote:
>
> > I'm trying to make squid work as transparent proxy on CentOS, squid ver is
> > 3.2
I'm trying to make squid work as transparent proxy on CentOS, squid ver is
3.2.0.12, with ecap enabled.
The problem is that squid doesn't work on transparent port and responds on
non-transparent port.
I've simplified configuration as possible to exclude access errors
Here's my squid.conf:
http
11 matches
Mail list logo
