!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

399 Members
Next Infra call: 2024-07-11, 18:00 CEST (UTC+2) | Infra operational issues backlog: https://github.com/orgs/NixOS/projects/52 | See #infra-alerts:nixos.org for real time alerts from Prometheus.121 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
4 Aug 2025
@hexa:lossy.networkhexayeah, I'm temporarily blocking tor exits18:53:12
@hexa:lossy.networkhexathe requests stopped a minute after I sent the mail18:57:02
@hexa:lossy.networkhexaalso boo, we're still using iptables18:57:17
5 Aug 2025
@emma:rory.gay@emma:rory.gayor youre using the nftables wrapper lol02:59:30
@hexa:lossy.networkhexathe nixos default 🤷03:00:29
@hexa:lossy.networkhexaquite a bit of technical debt in there03:00:51
@emma:rory.gay@emma:rory.gayyeah, thats the nftables wraper03:02:10
@emma:rory.gay@emma:rory.gay iptables v1.8.11 (nf_tables) 03:02:18
@emma:rory.gay@emma:rory.gayglad that still exists because i have no clue how to manage nftables03:02:46
@hexa:lossy.networkhexa
  systemd.services.nft-update-tor-exits = {
    wantedBy = [ "nftables.service" ];
    after = [ "nftables.service" ];
    startAt = "hourly";
    script = ''
      curl -sSL "https://check.torproject.org/cgi-bin/TorBulkExitList.py?exit" | sed '/^#/d' | while read IP; do
        nft add element inet filter torexits { $IP } 
      done
    '';
    path = with pkgs; [
      curl
      nftables
    ];
  };
03:10:29
@hexa:lossy.networkhexa
        set torexits {
          type ipv4_addr;
          flags dynamic, timeout;
          timeout 6h;
        }
03:11:00
@hexa:lossy.networkhexabasically you can create a datatype, e.g. a set03:11:06
@hexa:lossy.networkhexaand add to it, and have entries timeout automatically03:11:14
@hexa:lossy.networkhexaand then match on that set03:11:31
@hexa:lossy.networkhexa
            ip saddr @torexits counter drop
03:11:38
@sinan:sinanmohd.comsinan changed their profile picture.03:58:54

Show newer messages


Back to Room ListRoom Version: 6