Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

roon-server: 1.8-850 -> 1.8-880 #152251

Merged
merged 2 commits into from
Dec 27, 2021

Conversation

lovesegfault
Copy link
Member

Motivation for this change

Closes: #152104

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:
  • 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
Copy link
Member Author

@anttisoikkeli This PR needs to be tested, I'm currently away from home and cannot test this in my Roon server.

@Steell
Copy link
Contributor

Steell commented Dec 27, 2021

Tested and confirmed operating as expected on my NixOS machine.

@github-actions
Copy link
Contributor

Successfully created backport PR #152360 for release-21.11.

@lovesegfault lovesegfault deleted the roon-server-1.8-880 branch January 3, 2022 16:03
@anttisoikkeli
Copy link

@Steell did you actually test to connect to it? Mine is running as well, but my Roon Remote fails to connect to it.

Tested on Android (Note 10 Plus) and iPad (2019 model) and both have latest version of Roon Remote. Android gives Connecting/Connection failed -loop and iPad can't even find it. Systemctl tells me that it's running on 1.8-880. Nothing has changed in the system lately.

I'm 98% certain that this relates to the new version of roon-server somehow. I'm guessing that adding libtasn1 isn't enough after all and some missing library is now failing silently or then the new version needs some new open ports.

Ping @lovesegfault as well.

Sorry for reacting this late, but I haven't been able to play with this before now.

@lovesegfault
Copy link
Member Author

It's going to take me a hot minute to be able to test or debug this.

My Roon server is in storage and I'm in another continent for another few weeks, and then I need to find a house before I can reassemble everything.

My recommendation is that we either revert this for now or that someone debug the issue without my help.

@anttisoikkeli
Copy link

I can try to debug this as well. Personally at least, I'm not in a hurry.

Note that reverting is not really an option. New versions of Roon Remotes (that get updated automatically in mobile devices) are not backwards compatible with the old roon-server and those can't be downgraded. We would have a broken system anyway, even if we reverted all the changes. That's why I created the issue in the first place.

I would say that let's just accept that it's broken and debug/fix this when we have time. Reverting creates just extra work without any benefits.

@anttisoikkeli
Copy link

It's firewall! sudo systemctl stop firewall and Roon Remote can connect.

@lovesegfault
Copy link
Member Author

It's firewall! sudo systemctl stop firewall and Roon Remote can connect.

Ah, interesting :)

Can you try stealing my firewall rules and seeing if it fixes it?

https://github.com/lovesegfault/nix-config/blob/09602aa096cac83ab92aa770889c925bd44836be/hosts/bohr/default.nix#L63

@anttisoikkeli
Copy link

Those are already identical to: https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/services/audio/roon-server.nix

There is something else. I also tried to allow all TCP and UDP ports with this and no success:

    networking.firewall.allowedTCPPortRanges = [ { from = 0; to = 65353; } ];
    networking.firewall.allowedUDPPortRanges = [ { from = 0; to = 65353; } ];

@anttisoikkeli
Copy link

anttisoikkeli commented Jan 6, 2022

Found it, this fixes the problem:

sudo iptables -I INPUT 1 -p tcp --dport 9330:9332 -j ACCEPT

Source: https://community.roonlabs.com/t/connection-failed-and-chromecast-issues-roon-using-new-additional-network-ports-since-880/181528

Now I just need to find out why the lines from my previous comment didn't fix anything, but that's not related to this ticket :)

EDIT: Ports above 9332 not needed.

lovesegfault added a commit to lovesegfault/nixpkgs that referenced this pull request Jan 9, 2022
During the bump to 1.8-880 these became necessary, debugging took place
in the [relevant PR][1].

[1]: NixOS#152251
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

roon-server: 1.8-850 -> 1.8-880
3 participants