Re: still having smp/snat problems (Re: Linux 2.4.19-rc3)

[John M Flinchbaugh <glynis@butterfly.hjsoft.com>]

[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]

On Mon, Mar 10, 2003 at 11:39:21AM +0200, Dan Broscoi wrote:
> i'm writing you after reading your post on 
http://hypermail.idiosynkrasia.net/linux-kernel/archived/2002/week28/142
9.html
> I have the same problem, compiling a 2.4.20 kernel on Debian 3.0
> Do you know the fix for this ?

no one could really offer any help in the end.  i think having the
multiple snat rules matching on all interfaces may have been
triggering a race in the conntrack code.  i should probably resubmit
my findings.

anyway, limitting the rules by matching them only to their appropriate
interfaces seemed to alleviate the problem.

so now i use something similar to this:
iptables -t nat -A POSTROUTING -o eth0 -s 192.168.1.0/24 \
-j SNAT --to 10.1.1.15
iptables -t nat -A POSTROUTING -o eth1 -s 192.168.1.0/24 \
-j SNAT --to 192.168.1.1
iptables -t nat -A POSTROUTING -o eth2 -s 192.168.2.0/24 \
-j SNAT --to 192.168.2.1
---

note the -o interface rules.  this keeps it from applying more than
one snat rule to a packet.  it only applies them to the packet going
out the proper interface.

ps. i'm actually going to bounce this to the kernel list again to see
if i can stir up any more noise on this one.
-- 
____________________}John Flinchbaugh{______________________
| glynis@hjsoft.com         http://www.hjsoft.com/~glynis/ |
~~Powered by Linux: Reboots are for hardware upgrades only~~

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]