Re: nf_conntrack_ipv4 must be loaded explicitly

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jan Engelhardt wrote
in recent git kernels, I experience the following "regression" that no packets traverse the nat table (esp. the POSTROUTING counters just stand still) - and hence things like ping+SNAT do not work. Bisect nailed it down to:

ff09b7493c8f433d3ffd6a31ad58d190f82ef0c5 is first bad commit
commit ff09b7493c8f433d3ffd6a31ad58d190f82ef0c5
Author: Yasuyuki Kozakai <[email protected]>
Date:   Sat Jul 7 22:25:28 2007 -0700

    [NETFILTER]: nf_nat: remove unused nf_nat_module_is_loaded

    Signed-off-by: Yasuyuki Kozakai <[email protected]>
    Signed-off-by: Patrick McHardy <[email protected]>
    Signed-off-by: David S. Miller <[email protected]>

:040000 040000 177886eca60385293ac736c8e4861a2d4910d90a 32e63b6a9399e1ea65dc6cd0b357ca811e4dc835 M      include
:040000 040000 e1c20c3db28c927af62df067b2a20f8604a5fe06 84a277d1f81e3be9ce37ce6040c6d814ca20b3b0 M      net


The diff from ff09b7^...ff09b7 made me think...

End result:

After loading nf_conntrack_ipv4.ko, everything works again (also with the "bad" ff09b7). But I have to load it explicitly, and I think that unfortunately breaks a lot of setups (such as mine) which assume ipv4 connection tracking is always there.

I already have a patch for this queued. I'll push it upstream once
I get a new power supply for the box I keep that tree on, hopefully
tommorrow.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux