# Standard kernel modules e.g ipset **URL:** \ **Category:** OCTEON CN9130\ **Created:** [February 2, 2022, 7:57pm UTC](https://community.solid-run.com/t/standard-kernel-modules-e-g-ipset/234 "2022-02-02T19:57:21Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![RoutingLoop](https://avatars.discourse-cdn.com/v4/letter/r/ac8455/32.png) [@RoutingLoop](https://community.solid-run.com/u/RoutingLoop)\ **Post date:** [February 2, 2022, 7:57pm UTC](https://community.solid-run.com/t/standard-kernel-modules-e-g-ipset/234/1 "2022-02-02T19:57:21Z")
Hi, I’ve been trying to get ipset module installed as unfortunately it was missing from the build I did using the build script (December time). I was going to compile ipset module from git, but realised don’t have the kernel headers for the custom kernel. So before I go and start attempting to compile a whole new kernel for my build. I’ve since noticed some pre built images now available to download, do these images have more of the standard kernel modules pre-compiled that’d you find with Debian (etc). And or the kernel headers included? Regards ---
**Author:** ![Alon](https://avatars.discourse-cdn.com/v4/letter/a/f05b48/32.png) [@Alon](https://community.solid-run.com/u/Alon)\ **Post date:** [February 3, 2022, 11:16am UTC](https://community.solid-run.com/t/standard-kernel-modules-e-g-ipset/234/2 "2022-02-03T11:16:35Z")
we’ve updated the kernel version to 5.15, howerver we didn’t add new modules to be compiled with the kernel. ---
**Author:** ![RoutingLoop](https://avatars.discourse-cdn.com/v4/letter/r/ac8455/32.png) [@RoutingLoop](https://community.solid-run.com/u/RoutingLoop)\ **Post date:** [February 3, 2022, 12:51pm UTC](https://community.solid-run.com/t/standard-kernel-modules-e-g-ipset/234/3 "2022-02-03T12:51:23Z")
Thanks Alon, I’m looking at compiling a new kernel to include conntrack and ipset (maybe a few others). just looking for advice/opinion. 1. would it best to add some custom config options in something like “configs/linux/cn913x\_additions.config” and build a whole new image using runme.sh ? or 2. Or could i pull the linux 5.15 kernel tarball down on my current image and build a new kernel directly on that? (ensuring i add the patches). regards ---
**Author:** ![Alon](https://avatars.discourse-cdn.com/v4/letter/a/f05b48/32.png) [@Alon](https://community.solid-run.com/u/Alon)\ **Post date:** [February 3, 2022, 1:09pm UTC](https://community.solid-run.com/t/standard-kernel-modules-e-g-ipset/234/4 "2022-02-03T13:09:58Z")
i think both ways are fine. the runme script will make it easier for you as it creates a ready to deploy image, and save you some time vs compiling it yourself. ---
**Author:** ![RoutingLoop](https://avatars.discourse-cdn.com/v4/letter/r/ac8455/32.png) [@RoutingLoop](https://community.solid-run.com/u/RoutingLoop)\ **Post date:** [February 5, 2022, 10:48pm UTC](https://community.solid-run.com/t/standard-kernel-modules-e-g-ipset/234/5 "2022-02-05T22:48:48Z")
cheers i decided to build a new kernel,(based on v5.15.19), rather than a full new image, mainly because i’d done quite a lot of modifications post build. Anyway the new kernel seems to working well. Added several options around routing and firewalling,e.g IPSET, CONNTRACK. I’ll use my config additions when i build new images in the future. thanks for you help ---
**Author:** ![RoutingLoop](https://avatars.discourse-cdn.com/v4/letter/r/ac8455/32.png) [@RoutingLoop](https://community.solid-run.com/u/RoutingLoop)\ **Post date:** [February 5, 2022, 10:54pm UTC](https://community.solid-run.com/t/standard-kernel-modules-e-g-ipset/234/6 "2022-02-05T22:54:21Z")
oh another thought, i ran menuconifg on default .config following defconfig. I decided not to change much, but I think there a lot of options enabled as part of defconfig, which could be removed for a bespoke slimline kernel.