Our outbound traffic gets SNATted to claim to come from one of several role IPs. These IPs are hosted on different routers for load distribution purposes. The choice of which role IP to use depends on the exact destination IP address / TCP port number the connection goes to. I'm using the "-j ROUTE" target to force a routing decision for this, but it seems to have the side effect of breaking conntrack. Without -j ROUTE, the outbound connection appears in the conntrack table, so that when incoming replies arrive, they pass an ESTABLISHED test, and are let in. If it needs to -j ROUTE on the way out, then when the reply comes back, no conntrack entry means it fails ESTABLISHED and gets dropped. It seems that "-j ROUTE --continue" doesn't help either, it still goes missing. Can anyone shed any light on this? How to keep the entry in conntrack even though using -j ROUTE. Failing that, how else to perform a routing decision override in a way that won't break conntrack? -- Paul Evans <paul@xxxxxxxxxxxxx> Tel: +44 (0) 845 666 7778 Fax: +44 (0) 870 163 4694 http://www.mxtelecom.com -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
