question about TPROXY, --on-port and the fact it doesn't alter the packet header in any way

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

 




Hello,

I've been playing with TPROXY with squid3, and it's working fine so far,
but there is one thing (at least!) i do not understand:

if I use it with, e.g., --on-port 3129, for packet matching 'tcp dport
80', it then ends up in the INPUT chain, but still on tcp dport 80 (*)

squid3 is listening on tcp port 3129, so how does it get there?


Thanks in advance!

sam

(*) -> paquet header ot modified, and this is confirmed with the TRACE
'jump'

--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux