On Tue, Jun 28, 2022 at 09:01:01PM +0200, Daniel Gröber wrote: > Hi Pablo, > > On Tue, Jun 28, 2022 at 07:13:02PM +0200, Pablo Neira Ayuso wrote: > > You can do > > > > # cat x.nft > > include "./z.nft" > > # cat z.nft > > add table x > > > > then: > > > > # nft -f x.nft > > > > using ./ at the beginning of the path overrides DEFAULT_INCLUDE_PATH. > > > > Is this what you are searching for? > > While that could work its rather a hassle. On my (Debian) system > nftables.service runs in the root directory so I'd have to do ugly stuff > like `include "./etc/nftables/foo.conf"` which I'd rather not. For one the > config would then depend on where `nft -f ...` is run exactly which sucks. Hm, that's one way to put it, yes. > I think my patch is a much cleaner and general solution. I might be missing anything, could you describe your use-case? You also consider that using absolute path in includes is suboptimal?