Hi List, I am trying to tweak my transparent tor-proxyfying netfilter setup (Tor Stable, Debian Wheezy, GNU/Linux, iptables v1.4.12.2, Kernel 3.2.0-amd64). So far, redirection and torification works fine. I have have several users, some of them have their TCP traffic redirected to Tor, some are allowed to send packets directly. It works splendid. There is just one issue. About every once or twice a second there is a tcp packet running along my filter (that is the iptables -t filter) table that has no associated UID. This is what those packets look like: IN= OUT=eth0 SRC=192.168.178.50 DST=some-target LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=TCP SPT=50447 DPT=443 WINDOW=1002 RES=0x00 ACK URGP=0 Always 40 to 60 bytes. This packet is https, most likely generated by my firefox user when I was browsing a website. How is it possible for a packet not to have an associated uid? What am I missing? -- John ______________________________________________________ powered by Secure-Mail.biz - anonymous and secure e-mail accounts. -- 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
