Differences in package pre-requisites

For Developers
1

Hi,

I have an observation about some differences in the package pre-requisites when I try to compile my own firmware. This is specifically related to luci-app-sqm and I think sqm-scripts.

I have an XR500 and I want to setup the build system so I can easily create new images for upgrading. I setup my XR500 using the default 22.03.0-rc1 firmware and downloaded all of the packages I want.
Then, I tried to setup a build directory so I can compile my own firmware. I went through menu config and selected all of my packages. Then I compared to list of packages from my running XR500 and the list of packages in my newly compiled firmware. This is when I noticed the differences.

For some reason, my build environment is selecting extra packages that my running XR500 didn't install.

  • iptables-legacy, libip4tc2, libip6tc2

Is this something to be concerned about or can I use my self compiled image?

Thanks

2

'Concerned', perhaps not - it will 'work' nevertheless, but it's not an ideal situation.

It's caused by

which relies on OpenWrt's peculiar 2-stage buildsystem, where the first stage doesn't know about the feed packages, so the direct dependency on the old iptables won't interfere with fw4/ nftables (and later, at runtime, the virtual package is observed).
However, if you do build yourself, you'll typically do so in a single stage, including the feeds - and the iptables dependencies then causes iptables-legacy to be pulled in, instead of the more fitting iptables-nft.

Personally I do carry a revert for that locally:

--- a/feeds/packages/net/sqm-scripts/Makefile
+++ b/feeds/packages/net/sqm-scripts/Makefile
@@ -24,7 +24,7 @@ include $(INCLUDE_DIR)/package.mk
 define Package/sqm-scripts
   SECTION:=net
   CATEGORY:=Base system
-  DEPENDS:=+tc +kmod-sched-cake +kmod-ifb +iptables +iptables-mod-ipopt
+  DEPENDS:=+tc +kmod-sched-cake +kmod-ifb +iptables-nft +iptables-mod-ipopt
   TITLE:=SQM Scripts (QoS)
   PKGARCH:=all
 endef

@champtar do you see a better solution for this?

3 Likes
3

Hi @slh, the discussion to fix this issue is here https://github.com/openwrt/openwrt/pull/9648

3 Likes
4

Thanks for the help @slh and @champtar

I'll give the image builder a try, instead of compiling, and see if I can avoid this issue.