Sure, PM me and I’ll give you the details. Requirement: A NAS platform that can run .NET Core and knowledge of C#.

I was under the impression that this was for old unpatched versions of Windows... 

Are you saying that my Samba server runing under Linux is vulnerable to this family of exploits when allowing SMB1? 

I’m not an expert on that but I think running SMB v1 on anything does have security issues. Too lazy to dig into the details as they likely vary by Linux distribution.

Avoiding the issue, I went with a dedicated SMB v1 NAS based on a Raspberry PI here and set up a friend with a NFS to SMB v1 gateway on a Pi Zero W.

This has been an open issue for so long expecting a change isn’t realistic. Not saying it won’t come, but don’t hold your breath. Instead pick a safe work-around and move on.

The .Net Core option sounds interesting but my problem is solved.

I am so puzzled at the lack of support for NAS users. 
Am I the only one with old, weird music that is impossible to find elsewhere?
And if Sonos does not want to support NAS, could they not support OneDrive instead? 

Oh well, since I do not know what I am doing it took me forever to figure out the SMB1 solution.
But now it is done. Until the next hiccup.

Bose, here I come!

Curious as to whether you’ve read the thread before posting to it?

I have read your posts elsewhere on using a raspberry pi as a Gateway.  For a dozen years I was running a dlink 323 only for Sonos and leaving it on SMB1.  That box has died and my main NAS which I won’t allow the unsecured smb1 to run on could certainly hold my ~20,000 tracks and the gateway idea seems to make sense.  I am far more proficient at networking than I am at coding…. and I’ve never used a pi but I love the idea of what you present and the cost is lower which is great.  The comments that you make about how to set that up seem generally simple to follow but I was curious if that is a complete instruction set or if that is a small portion of a much larger assumption that someone would have complete understanding of setting up the pi?  Also is there a general security issue with having any device running version one even the pi as a Gateway? That would not itself cause the issues that we are trying to avoid?

You are correct. These security issue are not software bugs tied to a specific implementation of SMBv1 (say a particular version of Linux vs Mac OS vs Windows). There are fundamental security design flaws in older versions of SMB that can only be fixed by changing the protocol itself - thus SMBv2, v3, etc.

The ridiculous part of this thread is conflating old devices, backward compatibility, and a seemingly very reasonable request for Sonos to keep a feature they still support working at “industry standard” level on NEW hardware.

As others have said; if old devices cannot handle an SMBv2/v3 client library due to their firmware - leave them with SMBv1 support - they’re old and that’s what they started with. But limiting new devices to an insecure protocol that is not supported by many modern SMB “servers” is crazy. OTOH; new devices probably should keep allowing SMBv1 (if a user configures that) as the opposite problem exists; ancient NASes that don’t support new versions of SMB.

But workarounds telling people there are many ways to still run SMBv1 don’t address the main two issues: (1) Sonos support for SMB is decreasing in quality if that doesn’t mean “any common, modern SMB compatible server” and (2) no one should want to run ANYTHING with SMBv1 as the protocol; that’s why all the distros and commercial OSes are dropping support. Workaround are fine to help each other; but they don’t execute lack of a real product commitment response from Sonos.

Since you already have a NAS the Raspberry Pi gateway will be your cheapest option. Pick up a minimal Raspberry Pi Zero-W kit. Follow the instructions here and it should be working with no issues.

https://stan-miller.livejournal.com/357.html

If you want a wired Ethernet instead of WiFi connection then one of the Pis with wired Ethernet would be the way to go. A used Pi 3b, 3b+ would be less but a 4 2GB would work as well.

-----

Without a NAS the SMB v1 file server setup is the better option.

https://stan-miller.livejournal.com/650.html

If you have a problem PM me so we don’t clutter up the forum with non-sonos troubleshooting posts.

There has been much discussion of why Sonos does not support SMB v2 or 3, rather than rehash it again after so many past times I’l leave you to dig up the old topics if you care.

If you can address the issues seen there I’m sure the Sonos folks would be more than happy to forward your solutions to their tech folks who are stumped by the issue.

I’m fascinated by your assumption that their tech folks are stumped by the issue.

I’ve got some questions, if you’d be so kind:

• How many engineers does Sonos have?
• How large of a team would it require, if our assumption of the fact that the previous kernel would need to be replaced, would it take?
• Are you familiar enough with the Sonos code base to have an educated opinion as to how much time and effort is involved?
• Have you done scheduling for Sonos engineers, and are familiar with their velocity, and the challenges in dealing with the issue?
• Given that they’ve written a new system (S2], and integrated a couple of new features (HD radio and LPCM for the Arc), and had to work through the issues raised by the pandemic, and done a bit of bug fixing, how are you arriving at the fact that they’ve had time, much less are stumped by the issue?
• Are you familiar with their backlog, and management requests for feature prioritization?

Unfortunately, I don’t have answers to any of those questions. I’m unwilling to cast aspersions, unless someone can show that the Sonos staff is willfully sitting on their behinds, and ignoring the issue. I’d like to think not, but I don’t know. 

Re-reading that rant don’t you feel a bit embarrassed?

Wouldn't it have been easier to just ask “Why do you think they are stumped?”

If you ask me to stuff an elephant into a phone booth and I can’t do it, how is pointing that out insulting to me? The Sonos folks are in exactly the same situation trying to stuff a modern kernel and Samba into the limited legacy Sonos hardware.

In any case, I based that ‘stumped’ on seeing some discussion between the Sonos folks and the Samba developers on getting the current Samba to work on the latest Sonos kernel. I was not party to the details but as nothing came of it I’m going with stumped.

I guess some of you are already aware, just to state here that Synology new OS (DSM 7.0) currently does not support anymore SMB1, and it seems it’s not planned to do so.

Such an issue for NAS users!

Would you be so kind as to provide a link to this information? I’ve just spent five minutes on Google, looking for this data, and haven’t been successful in finding it. 

Hi,

yeah I am following this thread in the Synology forum here 

ciao

mk

Thank you most kindly!

Edit… looks like Zappiti has a similar issue as does Sonos...not enough space to update their kernel. 

Do they (Sonos) really have no space to update the kernel?

In general, many of us believe that is the case in S1 legacy devices. The amount of memory on those devices is extraordinarily limited. The common belief is at some point, hopefully in the near future, the extra memory in newer S2 devices will allow Sonos to replace the old kernel with a newer version in the S2 firmware, that is capable of including a newer version of Samba. 

There has been no confirmation from Sonos, one way or another. So essentially we’re making a guess here, but it seems logical, and fits the facts as we know them. 

I was under the impression that S2 devices have lots of space so confused by the “… as does Sonos ...not enough space to update their kernel” but I’m not totally up on all the details and acknowledged I may not be comprehending the nuance of what you are saying.

Anyway Sonos needs to fix this yesterday! (If there is space etc)

I can say that it seems with Synology DSM 7.0 beta Sonos libraries won’t work anymore, even with SMB 1 selected.

https://community.synology.com/enu/forum/20/post/139200

Sonos has been maintaining an antique Linux kernel, they had to as the changes made to Linux took them past the memory limits on their earlier hardware. Trying to port all the changes they made to the old kernel to a modern kernel is not something that can be quickly done, once done a LOT of testing needs to follow before releasing it to the user base.

My suggestions are:

Use a NAS to SMB v1 gateway device, a Pi for example will support any common NAS file share on the input and SMB v1 on the output. 

Use a SMB v1 capable NAS just for your Sonos music. Most of the tiny computers like Pis will support this with the addition of a storage medium, thumb drive, USB hard drive or the like.

I don’t have a warm fuzzy feeling about SMB v1 on a NAS containing important data and I wouldn’t do that.

The issue of them using SMB surely still exists under Pi, they create an insure network?

In the end they did a big fancy update recently to the Sonos OS, so surely they can update SMB.

There is another option as well, remove the 5 Sonos devices I have and replace them with something else.

I’ve currently got it going via Plex, which adds another layer which really shouldn’t be needed.

Hi Sonos team

as Synology does not support anymore SMB1 in their NAS from DSM 7.0 beta and probably from official releases of the upcoming official DSM 7 F/W, Sonos equipments cannot connect anymore to the music.

SONOS must now port SMB2 or SMB3 Otherwise many peoples will buy products from competition

regards

Using a Pi as a gateway to offer Sonos SMB v1 isn’t secure but since it has no access to your real NAS and data, the worst case scenario is you get compromised and have to swap out the boot SD card and reboot.

Using one as a v1 server you might have to re-copy your music too if that got corrupted. You can minimize that risk by mounting the music in read-only mode if you wish.

Yes Sonos should fix this but I can’t see a way to do that for S1 and while possible for S2 it is not a simple or fast project.

Sonos talk up S2 as a new operating system so it is BS that they don’t fix it. This is a very old flaw and shame on them that they have not fixed it yet. 
 

Yes there are work arounds but we shouldn’t require this on new hardware and an OS that was released in 2020. 
 

They lack the will to do it and frankly I hope people keep coming at them here and on social media until they fix this. 

Hi,

This post just to inform that there are 3 solutions for fixing that sad issues ( sad for Synology and Sonos)

- Use a cheap Raspeberry PI 0 that will make the link between the Synology/SMB2 or 3 and the Sonos/SMB1. I did not experiment that solution as it would require additional hardware and a good minimal Linux skill.

- Use the Plex solution . I am currently experimenting that solution. I would say that it did not start at the beginning but finally it did without clear reasons. Therefore I have some doubts about its reliability. The big advantage of this solution is that you have the  jackets of the albums just beside each album name that you don't have with the usual method.

- use an additional Docker Samba interface between the SMB>1 Synology and the SMB1 Sonos. I am currently experimenting as well that solution that is working well.

So currently I have both methods running between my Sonos equipments and the DSM 7.0 beta.

My wife is happy !

But let's be honest : I hope both Synology and Sonos will find TOGETHER a solution for music lovers.

Regards (from France )

Philippe