Bad iptables command on Ubuntu 22 LTS

[krizhanovsky]

ERROR: test_chains (http_rules.test_http_tables.HttpTablesTestMarkRules)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/root/tempesta-test/helpers/remote.py", line 96, in run_cmd
    assert p.returncode == 0, \
AssertionError: Cmd: 'iptables -t mangle -A PREROUTING -p tcp -j MARK --set-mark 1' return code is not 0 (4).

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/root/tempesta-test/http_rules/test_http_tables.py", line 376, in test_chains
    self.set_nf_mark(mark)
  File "/root/tempesta-test/http_rules/test_http_tables.py", line 347, in set_nf_mark
    remote.tempesta.run_cmd(cmd, timeout=30)
  File "/root/tempesta-test/helpers/remote.py", line 104, in run_cmd
    raise CmdError(f"Сmd {cmd} exited with return code {p.returncode}",
helpers.remote.CmdError: ('Сmd iptables -t mangle -A PREROUTING -p tcp -j MARK --set-mark 1 exited with return code 4', b'', b'iptables v1.8.7 (nf_tables):  CHAIN_ADD failed (Operation not supported): chain PREROUTING\n', 4)

----------------------------------------------------------------------
Ran 1 test in 4.225s

FAILED (errors=1)

# iptables -t mangle -A PREROUTING -p tcp -j MARK --set-mark 1
iptables v1.8.7 (nf_tables):  CHAIN_ADD failed (Operation not supported): chain PREROUTING
root@ubuntu:~/tempesta-test# cat /etc/issue
Ubuntu 22.04 LTS \n \l

[krizhanovsky]

I tested the iptables command on vanilla Ubuntu kernel and it works fine, so it seems the problem is in the Tempesta kernel config, which I used. I'm attaching the config.
285-linux-config.txt

The problem with the issue is that we clearly have dependence on a Linux kernel module (iptables/netfilter?), but https://github.com/tempesta-tech/tempesta/wiki/Install-from-Sources#configure-kernel does not specify the requirement. So need to explore which module is missed and add it to the doc.

[RomanBelozerov]

I added dependencies to documentation. The problem is missing CONFIG_NF_TABLES_IPV4, CONFIG_NF_TABLES_IPV6 and CONFIG_NF_TABLES