wrong order of received packets/bytes and sent packets/bytes with local incoming connections
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
Quoted 11 lines · On Saturday 2012-04-21 20:33, [email protected] wrote:
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 do not see any error here. The first bytes/packet= field shows bytes flowing in the "original direction", and the other is the reply direction.
Quoted 10 lines · Jan Engelhardt
Quoted 7 lines · On Saturday 2012-04-21 20:33, [email protected] wrote:
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.
Quoted 10 lines
Quoted 5 lines
with local outbound connections or forwarding connections these fields are correct filled.
is there anywhere a configuation option to fix this?
I do not see any error here. The first bytes/packet= field shows bytes flowing in the "original direction", and the other is the reply direction.
got it, it was my mistake ... thanks. ;)
Alois