On 24/10/2015 9:02 a.m., James White wrote:
> I'm literally stumped at this point. The fact TPROXY is working for
> IPv4 indicates that I have the necessary setup in place for TPROXY to
> at least work, but IPv6 not working is a mystery. Like I said the
> Squid box is fully IPv6 capable and clients
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm literally stumped at this point. The fact TPROXY is working for
IPv4 indicates that I have the necessary setup in place for TPROXY to
at least work, but IPv6 not working is a mystery. Like I said the
Squid box is fully IPv6 capable and clients co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Amos,
Thanks for your reply.
I've tried setting the rp_filter values to 1 and 2 and there is no
difference in behaviour.
Traffic isn't being tagged on dport 3128 directly. What I meant was I
needed to exclude the configured outgoing IPv6 address
On 14/10/2015 7:07 a.m., James White wrote:
> Hi all,
>
> I operate a squid box which has two http_port setups:
>
> http_port 3128
> http_port 3129 TPROXY
>
> I have implemented TPROXY to replace my NAT setup on a CentOS 7 Squid
> 3.3 box. Currently the IPv4 connectivity is working great, the IP
Hi all,
I operate a squid box which has two http_port setups:
http_port 3128
http_port 3129 TPROXY
I have implemented TPROXY to replace my NAT setup on a CentOS 7 Squid
3.3 box. Currently the IPv4 connectivity is working great, the IPv6
connectivity is broken when going through TPROXY. All IPv6
