Arch Linux

facat

Member

Registered: 2023-03-07

Posts: 3

[Resolved]Extension limit revision 0 not supported, missing kernel mod

I'd like to use iptables to limit bandwidth speed.
Some commands I use are as follow:

sudo iptables -I DOCKER-USER -p tcp -d 172.17.0.1 --dport 51970 -m limit --limit 5/sec  -j ACCEPT
Warning: Extension limit revision 0 not supported, missing kernel module?
iptables: No chain/target/match by that name.

sudo iptables -m limit -h
Warning: Extension limit revision 0 not supported, missing kernel module?
iptables v1.8.9 (legacy)

The first command doesn't succeed, chain DOCKER-USER  is empty.

It's something like my OS lacks limit module?

My archlinux kernel version:
Linux archlinux 6.1.12-arch1-1 #1 SMP PREEMPT_DYNAMIC Tue, 14 Feb 2023 22:08:08 +0000 x86_64 GNU/Linux

Last edited by facat (2023-03-08 13:37:05)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,726

Re: [Resolved]Extension limit revision 0 not supported, missing kernel mod

I'd bet that pacman -Q linux shows something different. This is common when you update the kernel without rebooting.

facat

Member

Registered: 2023-03-07

Posts: 3

Re: [Resolved]Extension limit revision 0 not supported, missing kernel mod

I'd bet that pacman -Q linux shows something different. This is common when you update the kernel without rebooting.

Yes.

# pacman -Q linux
linux 6.2.2.arch1-1

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,707

Re: [Resolved]Extension limit revision 0 not supported, missing kernel mod

So you either didn't reboot or forgot to mount the /boot partition when updating the kernel.

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

facat

Member

Registered: 2023-03-07

Posts: 3

Re: [Resolved]Extension limit revision 0 not supported, missing kernel mod

This problem is solved after reboot.