nixos/roon-server: open TCP ports 9330-9332 in firewall

[lovesegfault]

Motivation for this change

During the bump to 1.8-880 these became necessary, debugging took place
in the relevant PR.

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 22.05 Release Notes (or backporting 21.11 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
  • (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
• Fits CONTRIBUTING.md.

[lovesegfault]

@anttisoikkeli is this sufficient to fix 1.8-880?

[anttisoikkeli]

@lovesegfault sorry for the late reply. At least for me $ sudo iptables -I INPUT 1 -p tcp --dport 9330:9332 -j ACCEPT fixed the problem, but I haven't been able to fix it by changing the configuration. Will try again with reboot. There maybe something I don't know about how it all plays out (like, does NixOS edit iptables on reboot or something). Will get back during today if I get it working by just editing the config, without running manual iptables commands.

[anttisoikkeli]

And confirmed, this fixes the problem.

The reason I didn't get it working earlier from config:

I was using:

nixpkgs.config.networking.firewall.allowedTCPPortRanges

While I should had been using:

networking.firewall.allowedTCPPortRanges

[lovesegfault]

Thanks for confirming, glad it's all working again :)