Re: iptables-1.8.12 systemctl errors- BLFS 13.0
"rhubarbpieguy" ([email protected] via blfs-support Mailing List) <[email protected]> Tue, 14 Apr 2026 16:22:18 -0500
| Newsgroups | gmane.linux.lfs.beyond.support |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format... ------------=_1776201758-1253-23893 Content-Type: multipart/alternative; boundary="------------ZvreluCa4deOPiQ4yXv3Sg0O" Content-Language: en-US This is a multi-part message in MIME format. --------------ZvreluCa4deOPiQ4yXv3Sg0O Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 4/13/26 4:50 PM, Bruce Dubbs ([email protected] via blfs-support Mailing List) wrote: > On 4/13/26 4:17 PM, rhubarbpieguy ([email protected] via > blfs-support Mailing List) wrote: >> >> On 4/12/26 8:51 PM, Bruce Dubbs ([email protected] via >> blfs-support Mailing List) wrote: >>> On 4/12/26 4:16 PM, rhubarbpieguy ([email protected] via >>> blfs-support Mailing List) wrote: >>>> >>>> I see the following systemctl iptables errors: >>>> >>>> × iptables.service - Load Iptables Rules >>>> Loaded: loaded (/usr/lib/systemd/system/iptables.service; >>>> enabled; preset: enabled) >>>> Active: failed (Result: exit-code) since Fri 2026-04-10 >>>> 12:20:25 CDT; 11min ago >>>> Invocation: ba482abfd6a947f793bc2c161eca712a >>>> Process: 351 ExecStart=/etc/systemd/scripts/iptables >>>> (code=exited, status=3) >>>> Mem peak: 5.3M >>>> CPU: 35ms >>>> >>>> Apr 10 12:20:25 lfs iptables[373]: Perhaps iptables or your kernel >>>> needs to be upgraded. >>>> Apr 10 12:20:25 lfs iptables[380]: modprobe: ERROR: could not >>>> insert 'ip_tables': Exec format error >>>> Apr 10 12:20:25 lfs iptables[375]: iptables v1.8.12 (legacy): can't >>>> initialize iptables table `filter': Table does not exist (do you >>>> need to insmod?) >>>> Apr 10 12:20:25 lfs iptables[375]: Perhaps iptables or your kernel >>>> needs to be upgraded. >>>> Apr 10 12:20:25 lfs iptables[383]: modprobe: ERROR: could not >>>> insert 'ip_tables': Exec format error >>>> Apr 10 12:20:25 lfs iptables[381]: iptables v1.8.12 (legacy): can't >>>> initialize iptables table `filter': Table does not exist (do you >>>> need to insmod?) >>>> Apr 10 12:20:25 lfs iptables[381]: Perhaps iptables or your kernel >>>> needs to be upgraded. >>>> Apr 10 12:20:25 lfs systemd[1]: iptables.service: Control process >>>> exited, code=exited, status=3/NOTIMPLEMENTED >>>> Apr 10 12:20:25 lfs systemd[1]: iptables.service: Failed with >>>> result 'exit-code'. >>>> Apr 10 12:20:25 lfs systemd[1]: Failed to start Load Iptables Rules. >>>> >>>> I compiled iptables-1.8.12 and built all kernel options (including >>>> legacy) shown in the documentation. I'm using the Personal >>>> Firewall and see the /etc/systemd/ scripts/ iptables script. >>> >>> Did you build the kernel options as modules or did you build them >>> into the kernel? >>> You have two modprobe errors. If you built modules, did you do the >>> kernel 'modules_install' command? If you built the modules into the >>> kernel then you need to remove/comment out the modprobe commands in >>> the /etc/systemd/scripts/iptables file. >>> >>> -- Bruce >>> >>> >>> >> I ran make modules_install and /lib/modules ... is populated. I have >> the following lines in /etc/systemd/scripts/iptables: >> >> #modprobe nf_conntrack >> modprobe xt_LOG >> >> My .config shows: >> >> CONFIG_NET=y >> CONFIG_NETFILTER=y >> CONFIG_NETFILTER_ADVANCED=y >> CONFIG_NF_CONNTRACK=y >> CONFIG_NETFILTER_XTABLES=y >> CONFIG_NETFILTER_XTABLES_LEGACY=y >> CONFIG_NETFILTER_XT_TARGET_LOG=m >> CONFIG_IP_NF_IPTABLES=y >> CONFIG_IP_NF_NAT=m >> >> And in addition to the errors shown with 'systemctl status >> iptables.service -l' I see unknown symbol errors with journalctl: >> >> Apr 13 15:47:08 lfs iptables[357]: modprobe: ERROR: could not insert >> 'ip_tables': Unknown symbol in module, or unknown parameter (see dmesg) >> Apr 13 15:47:08 lfs iptables[359]: modprobe: ERROR: could not insert >> 'ip_tables': Unknown symbol in module, or unknown parameter (see dmesg) >> Apr 13 15:47:08 lfs iptables[361]: modprobe: ERROR: could not insert >> 'ip_tables': Unknown symbol in module, or unknown parameter (see dmesg) >> Apr 13 15:47:08 lfs iptables[363]: modprobe: ERROR: could not insert >> 'ip_tables': Unknown symbol in module, or unknown parameter (see dmesg) >> Apr 13 15:47:08 lfs iptables[365]: modprobe: ERROR: could not insert >> 'ip_tables': Unknown symbol in module, or unknown parameter (see dmesg) >> Apr 13 15:47:08 lfs iptables[367]: modprobe: ERROR: could not insert >> 'ip_tables': Unknown symbol in module, or unknown parameter (see dmesg) >> Apr 13 15:47:08 lfs iptables[369]: modprobe: ERROR: could not insert >> 'ip_tables': Unknown symbol in module, or unknown parameter (see dmesg) >> Apr 13 15:47:08 lfs iptables[371]: modprobe: ERROR: could not insert >> 'ip_tables': Unknown symbol in module, or unknown parameter (see dmesg) >> Apr 13 15:47:08 lfs iptables[373]: modprobe: ERROR: could not insert >> 'ip_tables': Unknown symbol in module, or unknown parameter (see dmesg) >> Apr 13 15:47:08 lfs iptables[379]: modprobe: ERROR: could not insert >> 'ip_tables': Unknown symbol in module, or unknown parameter (see dmesg) >> Apr 13 15:47:08 lfs iptables[382]: modprobe: ERROR: could not insert >> 'ip_tables': Unknown symbol in module, or unknown parameter (see dmesg) >> >> I should mention I believe iptables is working as I test with a 3rd >> party site and the test passes. > > If iptables is working you can just check with 'sudo iptables -L' > > In that case we need to figure out what is going on with systemd. In > sysV what we are doing is just running a script at > /etc/rc.d/rc.iptables. In systemd it should just be running the same > script located at /etc/systemd/scripts/iptables > > The systemd service file should be: > > $ cat ./system/iptables.service > [Unit] > Description=Load Iptables Rules > ConditionFileIsExecutable=/etc/systemd/scripts/iptables > After=network.target > > [Service] > Type=forking > ExecStart=/etc/systemd/scripts/iptables > TimeoutSec=0 > RemainAfterExit=yes > > [Install] > WantedBy=multi-user.target > > So really it should just be running that script. > > -- Bruce > > I have a clarification as I was quite unclear. Iptables is working on my old box with 12.4-699 using the same iptables and kernel options. I was trying to identify variables but did nothing but muddy the waters. Iptables is not working with 13.0 on my new box. But I don't mean to imply there's a problem with 13.0. I'm sure the problem is something I've done wrong. I see the same output you listed for /usr/lib/systemd/iptables.service. 'iptables -L shows: modprobe: ERROR: could not insert 'ip_tables': Unknown symbol in module, or unknown parameter (see dmesg) iptables v1.8.12 (legacy): can't initialize iptables table `filter': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. As I see unknown xt_ symbols and module references I thought I'd try building Netfilter xtables support as a module. It's probably nothing but I noticed I have no such option although the documentation says otherwise. The documentation lists: <*/M> Netfilter Xtables support (required for ip_tables). However, my menuconfig lists: -*- Netfilter Xtables support (required for ip_tables). --------------ZvreluCa4deOPiQ4yXv3Sg0O Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit <!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <p><br> </p> <div class="moz-cite-prefix">On 4/13/26 4:50 PM, Bruce Dubbs (<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:[email protected]">[email protected]</a> via blfs-support Mailing List) wrote:<br> </div> <blockquote type="cite" cite="mid:[email protected]">On 4/13/26 4:17 PM, rhubarbpieguy (<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:[email protected]">[email protected]</a> via blfs-support Mailing List) wrote: <br> <blockquote type="cite"> <br> On 4/12/26 8:51 PM, Bruce Dubbs (<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:[email protected]">[email protected]</a> via blfs-support Mailing List) wrote: <br> <blockquote type="cite">On 4/12/26 4:16 PM, rhubarbpieguy (<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:[email protected]">[email protected]</a> via blfs-support Mailing List) wrote: <br> <blockquote type="cite"> <br> I see the following systemctl iptables errors: <br> <br> × iptables.service - Load Iptables Rules <br> Loaded: loaded (/usr/lib/systemd/system/iptables.service; enabled; preset: enabled) <br> Active: failed (Result: exit-code) since Fri 2026-04-10 12:20:25 CDT; 11min ago <br> Invocation: ba482abfd6a947f793bc2c161eca712a <br> Process: 351 ExecStart=/etc/systemd/scripts/iptables (code=exited, status=3) <br> Mem peak: 5.3M <br> CPU: 35ms <br> <br> Apr 10 12:20:25 lfs iptables[373]: Perhaps iptables or your kernel needs to be upgraded. <br> Apr 10 12:20:25 lfs iptables[380]: modprobe: ERROR: could not insert 'ip_tables': Exec format error <br> Apr 10 12:20:25 lfs iptables[375]: iptables v1.8.12 (legacy): can't initialize iptables table `filter': Table does not exist (do you need to insmod?) <br> Apr 10 12:20:25 lfs iptables[375]: Perhaps iptables or your kernel needs to be upgraded. <br> Apr 10 12:20:25 lfs iptables[383]: modprobe: ERROR: could not insert 'ip_tables': Exec format error <br> Apr 10 12:20:25 lfs iptables[381]: iptables v1.8.12 (legacy): can't initialize iptables table `filter': Table does not exist (do you need to insmod?) <br> Apr 10 12:20:25 lfs iptables[381]: Perhaps iptables or your kernel needs to be upgraded. <br> Apr 10 12:20:25 lfs systemd[1]: iptables.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED <br> Apr 10 12:20:25 lfs systemd[1]: iptables.service: Failed with result 'exit-code'. <br> Apr 10 12:20:25 lfs systemd[1]: Failed to start Load Iptables Rules. <br> <br> I compiled iptables-1.8.12 and built all kernel options (including legacy) shown in the documentation. I'm using the Personal Firewall and see the /etc/systemd/ scripts/ iptables script. <br> </blockquote> <br> Did you build the kernel options as modules or did you build them into the kernel? <br> You have two modprobe errors. If you built modules, did you do the kernel 'modules_install' command? If you built the modules into the kernel then you need to remove/comment out the modprobe commands in the /etc/systemd/scripts/iptables file. <br> <br> -- Bruce <br> <br> <br> <br> </blockquote> I ran make modules_install and /lib/modules ... is populated. I have the following lines in /etc/systemd/scripts/iptables: <br> <br> #modprobe nf_conntrack <br> modprobe xt_LOG <br> <br> My .config shows: <br> <br> CONFIG_NET=y <br> CONFIG_NETFILTER=y <br> CONFIG_NETFILTER_ADVANCED=y <br> CONFIG_NF_CONNTRACK=y <br> CONFIG_NETFILTER_XTABLES=y <br> CONFIG_NETFILTER_XTABLES_LEGACY=y <br> CONFIG_NETFILTER_XT_TARGET_LOG=m <br> CONFIG_IP_NF_IPTABLES=y <br> CONFIG_IP_NF_NAT=m <br> <br> And in addition to the errors shown with 'systemctl status iptables.service -l' I see unknown symbol errors with journalctl: <br> <br> Apr 13 15:47:08 lfs iptables[357]: modprobe: ERROR: could not insert 'ip_tables': Unknown symbol in module, or unknown parameter (see dmesg) <br> Apr 13 15:47:08 lfs iptables[359]: modprobe: ERROR: could not insert 'ip_tables': Unknown symbol in module, or unknown parameter (see dmesg) <br> Apr 13 15:47:08 lfs iptables[361]: modprobe: ERROR: could not insert 'ip_tables': Unknown symbol in module, or unknown parameter (see dmesg) <br> Apr 13 15:47:08 lfs iptables[363]: modprobe: ERROR: could not insert 'ip_tables': Unknown symbol in module, or unknown parameter (see dmesg) <br> Apr 13 15:47:08 lfs iptables[365]: modprobe: ERROR: could not insert 'ip_tables': Unknown symbol in module, or unknown parameter (see dmesg) <br> Apr 13 15:47:08 lfs iptables[367]: modprobe: ERROR: could not insert 'ip_tables': Unknown symbol in module, or unknown parameter (see dmesg) <br> Apr 13 15:47:08 lfs iptables[369]: modprobe: ERROR: could not insert 'ip_tables': Unknown symbol in module, or unknown parameter (see dmesg) <br> Apr 13 15:47:08 lfs iptables[371]: modprobe: ERROR: could not insert 'ip_tables': Unknown symbol in module, or unknown parameter (see dmesg) <br> Apr 13 15:47:08 lfs iptables[373]: modprobe: ERROR: could not insert 'ip_tables': Unknown symbol in module, or unknown parameter (see dmesg) <br> Apr 13 15:47:08 lfs iptables[379]: modprobe: ERROR: could not insert 'ip_tables': Unknown symbol in module, or unknown parameter (see dmesg) <br> Apr 13 15:47:08 lfs iptables[382]: modprobe: ERROR: could not insert 'ip_tables': Unknown symbol in module, or unknown parameter (see dmesg) <br> <br> I should mention I believe iptables is working as I test with a 3rd party site and the test passes. <br> </blockquote> <br> If iptables is working you can just check with 'sudo iptables -L' <br> <br> In that case we need to figure out what is going on with systemd. In sysV what we are doing is just running a script at /etc/rc.d/rc.iptables. In systemd it should just be running the same script located at /etc/systemd/scripts/iptables <br> <br> The systemd service file should be: <br> <br> $ cat ./system/iptables.service <br> [Unit] <br> Description=Load Iptables Rules <br> ConditionFileIsExecutable=/etc/systemd/scripts/iptables <br> After=network.target <br> <br> [Service] <br> Type=forking <br> ExecStart=/etc/systemd/scripts/iptables <br> TimeoutSec=0 <br> RemainAfterExit=yes <br> <br> [Install] <br> WantedBy=multi-user.target <br> <br> So really it should just be running that script. <br> <br> -- Bruce <br> <br> <br> </blockquote> <p>I have a clarification as I was quite unclear. Iptables is working on my old box with 12.4-699 using the same iptables and kernel options. I was trying to identify variables but did nothing but muddy the waters. Iptables is not working with 13.0 on my new box. But I don't mean to imply there's a problem with 13.0. I'm sure the problem is something I've done wrong.</p> <p>I see the same output you listed for /usr/lib/systemd/iptables.service.</p> <p>'iptables -L shows:</p> <p>modprobe: ERROR: could not insert 'ip_tables': Unknown symbol in module, or unknown parameter (see dmesg)<br> iptables v1.8.12 (legacy): can't initialize iptables table `filter': Table does not exist (do you need to insmod?)<br> Perhaps iptables or your kernel needs to be upgraded.</p> <p>As I see unknown xt_ symbols and module references I thought I'd try building Netfilter xtables support as a module. It's probably nothing but I noticed I have no such option although the documentation says otherwise.</p> <p>The documentation lists: <*/M> Netfilter Xtables support (required for ip_tables). However, my menuconfig lists: -*- Netfilter Xtables support (required for ip_tables).</p> <p><br> </p> <p> <style type="text/css">pre { font-size: 10pt; font-family: "Liberation Mono", monospace; background: transparent }p { margin-bottom: 0.1in; line-height: 115%; background: transparent }</style></p> <br> </body> </html> --------------ZvreluCa4deOPiQ4yXv3Sg0O-- ------------=_1776201758-1253-23893 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- http://lists.linuxfromscratch.org/sympa/info/blfs-support Unsubscribe: See the above information page ------------=_1776201758-1253-23893--