From: "Secure-Mail User" <johnmurphy@secure-mail.biz>
To: netfilter@vger.kernel.org
Subject: tcp packets without uid
Date: Sat, 05 May 2012 15:36:54 +0200 [thread overview]
Message-ID: <cfc4da83cf5be64518284737f708c186@mail.secure-mail.biz> (raw)
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.
reply other threads:[~2012-05-05 13:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cfc4da83cf5be64518284737f708c186@mail.secure-mail.biz \
--to=johnmurphy@secure-mail.biz \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).