We are getting closer!
shorewall:
1. Macro forwardUPnP is not supported. (Legacy shorewall:
/usr/share/shorewall/action.forwardUPnP ). I would assume that its
relatives action.allowinUPnP and macro.DropUPnP & macro.A_DropUPnP would
do the same.
(Yeah, I know I shouldn't be using it. I have a bittorrent server behind).
2. tproxy doesn't work. I don't need it to; I just realized it was a
holdover from when squid was a thing.
3. ERROR: unsupported address or interface in an address column: cable
Offending lines:
/etc/shorewall/interfaces:
#ZONE INTERFACE BROADCAST OPTIONS
net cable detect
dhcp,tcpflags,rpfilter,logmartians=1,optional,wait=5,upnp
/etc/shorewall/providers:
#NAME NUMBER MARK DUPLICATE INTERFACE GATEWAY
OPTIONS COPY
rogers 3 3 - cable detect track,primary -
shorewall6:
1.. PYTHONPATH=src python3 -m shorewall_nft check /etc/shorewall6
/tmp/tmpmlobeofy.nft:105:18-54: Error: Could not resolve hostname:
Address family for hostname not supported
ip daddr 2607:fea8:be20:7fc:21c:23ff:fedd:1e22 tcp dport 80
accept comment "rules:40"
This is an expansion of the following rule:
Web(ACCEPT) net eloc:$FLAMEN_IP
("eloc" is the name of the internet zone)
and a params definition:
params:FLAMEN_IP=2607:fea8:be20:7fc:21c:23ff:fedd:1e22
On 2026-07-23 04:17, Dave Kempe wrote:
Hi Winston,
thanks for trying it out! Let me know if this release fixes your problems:
https://github.com/sol1/shorewall-nft/releases/tag/v0.2.4
Dave
On Thu, 23 Jul 2026 at 12:05, Winston Sorfleet <[email protected]> wrote:
Also, is this supposed to work in shorewall6?
_______________________________________________
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
