diff options
| author | Fernando Fernandez Mancera <ffmancera@riseup.net> | 2019-07-15 21:31:49 +0200 |
|---|---|---|
| committer | Pablo Neira Ayuso <pablo@netfilter.org> | 2019-07-18 20:55:53 +0200 |
| commit | e971ceb803e147e47c15cbb7c5b84327c6453786 (patch) | |
| tree | a3827f6d81a000fbff143ad65eec2f492126d442 /net/ipv4 | |
| parent | b4f1483cbfa5fafca4874e90063f75603edbc210 (diff) | |
| download | linux-e971ceb803e147e47c15cbb7c5b84327c6453786.tar.gz linux-e971ceb803e147e47c15cbb7c5b84327c6453786.tar.bz2 linux-e971ceb803e147e47c15cbb7c5b84327c6453786.zip | |
netfilter: synproxy: fix rst sequence number mismatch
14:51:00.024418 IP 192.168.122.1.41462 > netfilter.90: Flags [S], seq
4023580551,
14:51:00.024454 IP netfilter.90 > 192.168.122.1.41462: Flags [S.], seq
727560212, ack 4023580552,
14:51:00.024524 IP 192.168.122.1.41462 > netfilter.90: Flags [.], ack 1,
Note: here, synproxy will send a SYN to the real server, as the 3whs was
completed sucessfully. Instead of a syn/ack that we can intercept, we instead
received a reset packet from the real backend, that we forward to the original
client. However, we don't use the correct sequence number, so the reset is not
effective in closing the connection coming from the client.
14:51:00.024550 IP netfilter.90 > 192.168.122.1.41462: Flags [R.], seq
3567407084,
14:51:00.231196 IP 192.168.122.1.41462 > netfilter.90: Flags [.], ack 1,
14:51:00.647911 IP 192.168.122.1.41462 > netfilter.90: Flags [.], ack 1,
14:51:01.474395 IP 192.168.122.1.41462 > netfilter.90: Flags [.], ack 1,
Fixes: 48b1de4c110a ("netfilter: add SYNPROXY core/target")
Signed-off-by: Fernando Fernandez Mancera <ffmancera@riseup.net>
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
Diffstat (limited to 'net/ipv4')
0 files changed, 0 insertions, 0 deletions