Netgate 2100 blocking? Spotify issue
-
I can't specifically speak to EasyList and how ofter it changes. However ADs_Basic, changes often more than once a week. (Of course you can choose when to check it)
However, unbound will only restart (assuming pfBlocker is configured properly) when one of the DNSBL lists has a changed. Not just because it checked. I check ADs_Basic daily (and other lists). As I said before, unbound can still go days between needing a restart.
my unbound restarted because of a list change on Sept 1 at midnight, and again on Sept 5 (this morning) in the days between it just kept running.
The entire restart of unbound takes a couple of seconds, you would never know in most cases.
In fact the only way I know is by the dashboard (if I'm running it) and graylog (which is always running) Your last dashboard image, didn't even show any lists. Does it now? and what is the time stamp of the list reload.my dashboard shows the update time (this morning)
so they all reloaded this morning... looks fine to me (compare this to the previous screen shot and they all said Sep 1) nothing changed in-between, nothing restarted unbound.
The graylog shows me the pid changed (different colour) but it also never skipped.
orange is pid before, different pid after the reload is blue.
Notice the time slot (5 minutes) bands where there is both blue and orange. that's when it restarted.here is the same data on a 2 second time slice, unbound restarting at the colour transition, you should never even notice, nor should any device on your network.
-
@jrey said in Netgate 2100 blocking? Spotify issue:
here is the same data on a 2 second time slice, unbound restarting at the colour transition, you should never even notice, nor should any device on your network.
One caveat I would offer --
Be careful of time comparison examples (such as the 2 seconds in your post). This will be very dependent on the underlying hardware a particular user is running on. Another obvious variable is the size of the chosen list or lists. So long as the comparison is apples-to-apples (meaning same exact hardware and same exact DNSBL lists), then time comparisons are pertinent.I've just sometimes seen posters assume that everyone should see the same performance with some feature as they do. That is not the case unless the parameters are very closely matched.
-
@jrey said in Netgate 2100 blocking? Spotify issue:
I can't specifically speak to EasyList and how ofter it changes. However ADs_Basic, changes often more than once a week. (Of course you can choose when to check it)
However, unbound will only restart (assuming pfBlocker is configured properly) when one of the DNSBL lists has a changed. Not just because it checked. I check ADs_Basic daily (and other lists). As I said before, unbound can still go days between needing a restart.
10/10 ! Nice. You've done your home work. -
@bmeeks said in Netgate 2100 blocking? Spotify issue:
Be careful of time comparison examples (such as the 2 seconds in your post).
sure, but I'm running a 2100 same as the OP. 2 second reload of unbound is "normal" here.
Edit: and the op has never answered the questions about the list size of list as seen in the pfblockerng.log (or other questions unless I missed those answers) so yes there still could be other "variables" as well.
-
-
@stephenw10 @Gertjan @jrey @bmeeks @SteveITS Hi all, so you know the fixes you provided have worked perfectly. Spotify has been behaving itself extremely well for a few days now, and is much more responsive too. I can't thank you all enough
I did realise afterwards that I also had pfBlockerNG misconfigured too (several people mentioned I might have done this) as it started aggressively blocking everything all of a sudden. So that's been reset back to factory except from being told to only update at night once a day.
Thanks again everybody, I'm very grateful 🫡
-
@jrey @stephenw10 @Gertjan @SteveITS @bmeeks I just thought I'd let you all know and post here just in case anybody else has the same problems I've had with Spotify.
A few days after my last post the issue with Spotify not seeing speakers and dropping connections returned. I did some hunting around online and eventually did find some other people who had the same problem, one of whom had a solution.
So if anybody else is finding pfBlocker is blocking Spotify and your speakers, add the domain byspotify.com to your DNSBL whitelist and restart pfBlocker in the Services panel, that fixed it
-
Ooo, good tip.
-
What is byspotify.com?
I am having intermittent Spotify disconnects all day long but I think my issue might just be librespot implementation in my device.
-
@bitperfect said in Netgate 2100 blocking? Spotify issue:
What is byspotify.com?
something they want their devices to check into periodically in order to function (and collect information) - SONOS has much the same "msmetrics.ws.sonos.com"
it is on some block lists and if you don't white list it their "new" app just crashes.
The cost of using their platform.whois
-
@jrey Thank you very much!
I found byspotify.com in my DNSBL block log so I have whitelisted it. Now the wait begins to see if it makes a positive difference.
I also found the Sonos domain but left that alone as I have no issues with my Sonos speaker.
-
@bitperfect I also found the domain rnwspotify.com in my block log, and Spotify works much better now I've unblocked that too
-
@MikeHalsey, thanks for the update.
I eventually determined the issue to be with my Spotify Connect endpoint and not the pfBlocker system. I have since demoted my audio system to using Airplay and it has been fine. Now I just need Airplay 3 to be released so it can be a bit perfect audio stream but that is another issue for another forum
-
Upnp thing??
-
No, it is because my streamer is not from an official Spotify Connect authorized vendor. Instead, they use the open-source Librespot client library, which can be flakey depending on its implementation.
