BlessJah has quit [Ping timeout: 245 seconds]
BlessJah has joined #nixos-on-your-router
disasm has quit [Quit: WeeChat 1.9.1]
disasm has joined #nixos-on-your-router
<BlessJah> disasm: maybe you'd know: I'm trying to get firewall-like rules where I could decide which subnets are allowed to access which ports
<BlessJah> more generic than networking.firewall.allowedTCPPorts
<BlessJah> nftables may be the way to go, but so far I've never used the tool
<disasm> BlessJah: use the `-s 10.40.33.20/24` parameter to the rule. There's no built-in nix way to do it, would require some special hacking.
<BlessJah> the rule? like when adding one manually or modifying one that nix created?
<cransom> if you are allowing, you' dhave to remove the nix rule and add your own
[0x4A6F] has joined #nixos-on-your-router
* BlessJah is missing some context here
<cransom> if you are looking to be more specific than allowing all traffic to a port, there's no piece of the firewall module you can really use other than adding in iptables for the specific port and sources you want and removing them from allowedXXXPorts.
<BlessJah> or doing it with nftables?
<cransom> or nftables. there's nothing built in to the modules for any of nftables though.
<BlessJah> there is, enable and string with rulesets
<BlessJah> project claims that syntax is friendlier
<cransom> yes, you'd end up writing all of the rule set. which may be fine, it just doesn't cooperate with anything that thinks iptables exists.
<BlessJah> yep, including docker and libvirt
* BlessJah is thinking about laptop for now
<cransom> and fail2ban/et al. i'd like to check out nftables but haven't had the time nor project for it.
[0x4A6F] has quit [Ping timeout: 276 seconds]