On 23/05/16 19:32, Amos Jeffries wrote:
There are two other things to check then.
Firstly, if the router receiving the wm0 traffic is the one doing WCCP
divert into Squid. It needs a similar excemption of that outgoing traffic.
Its a different router.
Secondly,
in squid.conf enable
On 23/05/2016 7:01 p.m., Mark Davies wrote:
>
>
> On 23/05/16 18:48, Amos Jeffries wrote:
>>> ext_if="wm0"
>>> int_if="bnx0"
>>>
>>> set skip on lo0
>>>
>>> rdr pass on $int_if inet proto tcp from 130.195.0.0/20 to any port 80 ->
>>> 127.0.0.1 port 8081
>>
>> What prevents Squids outgoing
On 23/05/16 18:48, Amos Jeffries wrote:
ext_if="wm0"
int_if="bnx0"
set skip on lo0
rdr pass on $int_if inet proto tcp from 130.195.0.0/20 to any port 80 ->
127.0.0.1 port 8081
What prevents Squids outgoing traffic (to port 80) from being diverted
back into Squid again?
I would expect the
On 23/05/2016 4:41 p.m., Mark Davies wrote:
> I know this comes up repeatedly but I'm now hitting this and can't see why.
>
> I have a traditional squid setup that works fine for clients that
> explicitly point at it but I also want to allow transparent access for some
> destinations for only
I know this comes up repeatedly but I'm now hitting this and can't see why.
I have a traditional squid setup that works fine for clients that
explicitly point at it but I also want to allow transparent access for some
destinations for only port 80. So I have wccp2 set up between a cisco
On 26/05/11 01:38, Daniel Anliker wrote:
hi,
we have a problem with squid 3.1.6 (debian 6.0.1) and wccp2.
the normal http traffic works like it should with:
wccp2_router 192.168.200.1
wccp2_forwarding_method gre
wccp2_return_method gre
wccp2_service standard 0
but we also like to have some
hi,
we have a problem with squid 3.1.6 (debian 6.0.1) and wccp2.
the normal http traffic works like it should with:
wccp2_router 192.168.200.1
wccp2_forwarding_method gre
wccp2_return_method gre
wccp2_service standard 0
but we also like to have some other ports on the squid.
i tried with:
Hello Amos,
Thanks for the prompt reply.
The only NAT I have in place is on the router and squid box. On the
router I have
ip nat inside source list 1 interface FastEthernet0/1 overload
and on the squid box I have,
iptables -t nat -A PREROUTING -i wccp0 -p tcp -m tcp --dport 80 -j
DNAT
On 23/05/11 18:37, Tux Mason wrote:
Hello,
The global connections will go back to the Cisco with the Squid box IP and then go
through whatever border NAT you have in place. The private client IP will
never touch the global Internet directly.
Please explain.
That was the simple
Hello,
Am having trouble getting WCCP2 to work with a Cisco 1800 series router.
The problem I have noticed is traffic sent to the squid box with a
private IP. The output of netstat:
netstat -ntlpua
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address
On 22/05/11 09:57, Tux Mason wrote:
Hello,
Am having trouble getting WCCP2 to work with a Cisco 1800 series router.
The problem I have noticed is traffic sent to the squid box with a
private IP. The output of netstat:
netstat -ntlpua
Active Internet connections (servers and established)
Proto
Amos Jeffries wrote:
I had a WCCP2 configuration (using a gre tunnel) working with Squid 3.0
+ sslBump patches, but would like to move up to Squid 3.1 to resolve
some quirks.
Here is the wccp configuration I was using with Squid 3.0:
wccp2_router 10.10.10.1
wccp2_address 10.10.10.250
(sorry - replying to myself after further investigation)
Guy Helmer wrote:
Amos Jeffries wrote:
I had a WCCP2 configuration (using a gre tunnel) working with Squid 3.0
+ sslBump patches, but would like to move up to Squid 3.1 to resolve
some quirks.
Here is the wccp configuration I was using
Guy Helmer wrote:
(sorry - replying to myself after further investigation)
Guy Helmer wrote:
Amos Jeffries wrote:
I had a WCCP2 configuration (using a gre tunnel) working with Squid 3.0
+ sslBump patches, but would like to move up to Squid 3.1 to resolve
some quirks.
Here is the wccp
I had a WCCP2 configuration (using a gre tunnel) working with Squid 3.0
+ sslBump patches, but would like to move up to Squid 3.1 to resolve
some quirks.
Here is the wccp configuration I was using with Squid 3.0:
wccp2_router 10.10.10.1
wccp2_address 10.10.10.250
wccp2_service dynamic 80
I had a WCCP2 configuration (using a gre tunnel) working with Squid 3.0
+ sslBump patches, but would like to move up to Squid 3.1 to resolve
some quirks.
Here is the wccp configuration I was using with Squid 3.0:
wccp2_router 10.10.10.1
wccp2_address 10.10.10.250
wccp2_service dynamic 80
16 matches
Mail list logo
