From: "alois.klingler@chello.at" <alois.klingler@chello.at>
To: netfilter-devel@vger.kernel.org
Subject: wrong order of received packets/bytes and sent packets/bytes with local incoming connections
Date: Sat, 21 Apr 2012 20:33:03 +0200 [thread overview]
Message-ID: <4F92FD5F.5010204@chello.at> (raw)
hi,
in /proc/net/nf_conntrack (and also in conntrack -L) i can see received
packets/bytes and sent packets/bytes.
with connections, which are local incoming connections (i.e. a
ssh-connection from anywhere to my machine) these fields are mixed,
means that the received packets/bytes are the sent packets/bytes and vice versa.
with local outbound connections or forwarding connections these fields
are correct filled.
is there anywhere a configuation option to fix this?
I am using kernel 3.3.2 (I can see this issue already very long, not
since this kernel) and conntrack 0.9.14 (debian squeeze).
Thanks!
Best regards
Alois
next reply other threads:[~2012-04-21 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-21 18:33 alois.klingler [this message]
2012-04-22 15:55 ` wrong order of received packets/bytes and sent packets/bytes with local incoming connections Jan Engelhardt
2012-04-22 17:25 ` alois.klingler
-- strict thread matches above, loose matches on Subject: below --
2012-04-18 19:13 MadLoisae
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=4F92FD5F.5010204@chello.at \
--to=alois.klingler@chello.at \
--cc=netfilter-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.