Search squid archive

Re: Squid3.1 TProxy weirdness

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I've just tested squid 3.1.0.16 on kernel 2.6.32.7 aqnd the result using
tproxy is:

2010/02/04 18:35:34.711| Processing: 'http_port 3129 tproxy'
2010/02/04 18:35:34.711| http(s)_port: found Listen on Port: 3129
2010/02/04 18:35:34.711| http(s)_port: found Listen on wildcard address:
[::]:3129
2010/02/04 18:35:34.711| Starting IP Spoofing on port [::]:3129
2010/02/04 18:35:34.711| Disabling Authentication on port [::]:3129 (IP
spoofing enabled)
2010/02/04 18:35:34.711| Detect TPROXY support on port [::]:3129
2010/02/04 18:35:34.711| ...Probing for IPv6 TPROXY support.
2010/02/04 18:35:34.711| FATAL: http(s)_port: TPROXY support in the system
does not work.
2010/02/04 18:35:34.711| leave_suid: PID 711 called
2010/02/04 18:35:34.711| leave_suid: PID 711 giving up root, becoming
'squid'
FATAL: Bungled squid.conf line 2: http_port 3129 tproxy
Squid Cache (Version 3.1.0.16): Terminated abnormally.
CPU Usage: 0.014 seconds = 0.008 user + 0.006 sys
Maximum Resident Size: 23056 KB
Page faults with physical i/o: 0

seems like there is no condition to jump over IPv6 failure , am i right? it
did not get to IPv4 tproxy support.

-- 
View this message in context: http://n4.nabble.com/Squid3-1-TProxy-weirdness-tp1042775p1468938.html
Sent from the Squid - Users mailing list archive at Nabble.com.

[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux