Hi Dave, can I make a suggestion: the old Shorewall checked and listed
required kernel settings ... shorewall-nft only had an ambiguous message
that I didn't connect with missing kernel settings. Maybe a look at
this area is warranted?
BillK
On 10/11/26 08:34, Dave Kempe wrote:
Thanks for the info. I'm happy to take updates/thoughts via github and
I can include better feedback for this problem in the output for the
next release. I won't be able to test all the combinations of
platforms and distros that shorewall runs on currently without more
help, so I appreciate any assistance.
Dave
On Thu, 5 Nov 2026 at 13:15, William Kenworthy <[email protected]>
wrote:
OK, shorewall -nft is now working fine on arm32 so far: the
problem was
missing settings in the kernel. The hosts I am using are around
10yrs
(2016 or so) with kernels continually being upgraded using "make
oldconfig" - the end result is almost random holes in the
configuration
including some nft settings. Of course, old shorewall does not
use them
so was fine :(
So check that if you compile your own custom kernels (gentoo ...)
Thanks for the suggestions various people made - it helped.
BillK
On 3/11/26 09:50, William Kenworthy wrote:
> Yep, did that which is why its installed - but it wont run and the
> error message is too vague to point to a direct cause. I am
missing
> some kernel settings so its rebuilding at the moment which is the
> probable cause - however my questions stand as until I get it
working
> :) there is nothing online about shorewall-nft and arm32 online
that I
> can find - only arm64. So I am hoping someone is running it on
arm32
> and its not a lost cause :)
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users