| commit | cce5a5c3029f731b5ea17a8a9a953ff742abf0d6 | |
| author | Maximilian Engelhardt <maxi@daemonizer.de> | |
| Mon, 24 Aug 2009 17:24:54 +0000 (24 19:24 +0200) | ||
| committer | Patrick McHardy <kaber@trash.net> | |
| Mon, 24 Aug 2009 17:24:54 +0000 (24 19:24 +0200) | ||
| tree | fe5e4c8366c3e2dc277885cd9d2bff276044b5f9 | treesnapshot (tar.gz zip) |
| parent | 35aad0ffdf548617940ca1e78be1f2e0bafc4496 | commitdiff |
netfilter: nf_nat: fix inverted logic for persistent NAT mappings
Kernel 2.6.30 introduced a patch [1] for the persistent option in the
netfilter SNAT target. This is exactly what we need here so I had a quick look
at the code and noticed that the patch is wrong. The logic is simply inverted.
The patch below fixes this.
Also note that because of this the default behavior of the SNAT target has
changed since kernel 2.6.30 as it now ignores the destination IP in choosing
the source IP for nating (which should only be the case if the persistent
option is set).
[1] http://git.eu.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=98d500d66cb7940747b424b245fc6a51ecfbf005
Signed-off-by: Maximilian Engelhardt <maxi@daemonizer.de>
Signed-off-by: Patrick McHardy <kaber@trash.net>
Kernel 2.6.30 introduced a patch [1] for the persistent option in the
netfilter SNAT target. This is exactly what we need here so I had a quick look
at the code and noticed that the patch is wrong. The logic is simply inverted.
The patch below fixes this.
Also note that because of this the default behavior of the SNAT target has
changed since kernel 2.6.30 as it now ignores the destination IP in choosing
the source IP for nating (which should only be the case if the persistent
option is set).
[1] http://git.eu.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=98d500d66cb7940747b424b245fc6a51ecfbf005
Signed-off-by: Maximilian Engelhardt <maxi@daemonizer.de>
Signed-off-by: Patrick McHardy <kaber@trash.net>
| net/ipv4/netfilter/nf_nat_core.c | diffblobblamehistory |