Weird, mine can't work with port_attr string>, then I guess we should wait for
Alan to fix these :) I'm waiting for him also (TS-816)
Regards,
Alvin
On 10/06/2011 11:26, Steve Cole wrote:
On June 10, 2011 12:20:30 PM [email protected] wrote:
And your ATS was built with --enable-tproxy?
Yes.
My iptables rules are the same as yours, and my ATS working just fine with
port_attr STRING =
When I used it, I saw ATS intercepting incoming client requests, but it would
not connect to any external site. It was giving errors off that it could not
connect in error.log
What's more, connecting to ATS with the browser in explicit proxy mode did not
work. With the> string it does both.
Do you have this :
Ip route add local 0.0.0.0/0 dev eth0 (or whatever interface ur Tproxy on)
table 100 ?
Yes.
With port_attr STRING>, do you get the desired transparency?
Yes.
