Harald Welte wrote:
Hi Patrick, Dave,
I think we really need a solution for the last (known) remaining
dependency problem with 2.6.14. Please see the description
below. I _think_ the patch is fine, at least I couldn't find any case
where we could leak anything by splitting the code in two modules.
There's a slight semantic change, though. If the user unloads
iptable_nat, all existing connections (including their configured NAT
mappings) will continue to work. Only when ip_nat.ko is unloaded, the
NAT mappings are evicted from the conntrack table. I like it that way,
since it's logical.
I agree, its more logical than having the table and the conntrack
part in one module.