Enthusiast I

SMB2 (or SMB3) support must be supported NOW!

Forum|Forum|7 years ago
June 14, 2019
281 replies
30263 views

We are writing summer 2019 and still Sonos only supports SMB version 1 for the Music Library share.

This is not acceptable.

A file share running SMB1 is extremely vulnerable to all the variants of cryptolocker virus that exists today. File share servers (NAS, Windows, Apple OS) can only support one version of SMB - so you cannot from the same box have one file share (for Sonos) using SMB1 and the other file shares using SMB2 or SMB3. This way Sonos puts each and every file share at serious risc - just because they don’t update their file share protocol to comply with this century.

And for the record - the “solution” through PLEX is not a solution. Unstable at best.

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

Show previous replies

K

Keithmac

Virtuoso

I bought my NAS solely to supply my own music to Sonos.

Even with Deezer etc there are songs that aren't available to stream.

We don't have computers running 24/7 so it would be a pain if Sonos stopped supporting NAS drives.

N

norwester

Lyricist III

I dread the day Sonos e-mails me to tell me to add my Zone Players and Play 5 Gen 1 systems to the junk pile with my CR-100s. I may have to go back and follow the example of folks that disabled Sonos updates to keep their CR-100s alive at that point.

And here we are…

I came here to look for solutions for streaming from my Synology w/o SMB1 enabled. I can't believe there's no SMB2 support. IMHO, this is the pitfall of forcing all devices to run the same software and not making a central control/distribution device that could be upgraded periodically and allow legacy satelite speakers to remain relevant.

Airgetlam

There’s a belief amongst some users that the reason for this was due to the Linux kernel being restricted to the 32 Meg memory on the older devices. We have hope that now that Sonos has indicated the 32 Meg devices are being moved to a “legacy” status, there’s some hope that one of the new features coming up in May will be a new kernel, that while not fitting on a 32 Meg device, will include an update to the SMB protocol for the ‘modern’ devices.

Bruce

Stanley_4

Grand Maestro

I’m hoping to see Sonos on a newer Linux kernel too, it will bring the latest SMB along with all the other features.

In the meanwhile the easy solution is a Raspberry Pi Zero W computer and a few minutes tweaking it to be an SMB v1 gateway for whatever file sharing you want to use on your NAS. I’ve tried it with whatever SMB Windows 10 uses, XFS, FAT and EXT 4 as source file systems.

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

There is also an SMB v1 server configuration there if you want the Pi to do the storage as well as providing the SMB v1 share. That is what I’m using now.

A

amun

I dread the day Sonos e-mails me to tell me to add my Zone Players and Play 5 Gen 1 systems to the junk pile with my CR-100s. I may have to go back and follow the example of folks that disabled Sonos updates to keep their CR-100s alive at that point.

And here we are…

I came here to look for solutions for streaming from my Synology w/o SMB1 enabled. I can't believe there's no SMB2 support. IMHO, this is the pitfall of forcing all devices to run the same software and not making a central control/distribution device that could be upgraded periodically and allow legacy satelite speakers to remain relevant.

Do you play a single stream, even if you then group speakers together? If so, you could run a music server (qhich doesn’t need SMB 1 enabled) on your Synology, using something like Hificast (free with ads, a feww UKP to remove ads) to cast directly to the Sonos speakers. This just treats the speaker as ‘dumb’, so I use a Chromecast audio to keep both options open.

A

amun

There’s a belief amongst some users that the reason for this was due to the Linux kernel being restricted to the 32 Meg memory on the older devices. We have hope that now that Sonos has indicated the 32 Meg devices are being moved to a “legacy” status, there’s some hope that one of the new features coming up in May will be a new kernel, that while not fitting on a 32 Meg device, will include an update to the SMB protocol for the ‘modern’ devices.

Or, if they’re creating a legacy build, then rather than just freezing the latest bloated build they could strip out all the ‘stuff’ that legacy can’t support anyway - e.g. voice - thereby leaving space for a larger kernel.

controlav

Lead Maestro

Zero bytes of the code on the legacy speakers are used for voice. All voice devices have at least 1GB of memory.

Apart from memory, the oldest devices run old versions of Linux on old CPU types. I know little about Linux, but I would not be surprised if modern Linux versions (that have modern SMB support) do not support the ancient CPUs and hardware in the legacy devices.

Author of the leading independent Sonos apps for Android, MacOS, iOS, Windows and Xbox.

A

amun

Zero bytes of the code on the legacy speakers are used for voice. All voice devices have at least 1GB of memory.

Unless you have access to the code base I don’t see how you can say this… So far, we’ve been told that all kit has to run the same version of software, and that the old kit can’t keep up with the latest requirements…. If they already have different kit working on different code bases, then there should be no problem at all making old and new work together seamlessly.

controlav

Lead Maestro

Unless you have access to the code base I don’t see how you can say this

I worked in the Sonos code base for several years, as the main contractor on the Phish project. I also have extensive experience in Alexa integration.

Author of the leading independent Sonos apps for Android, MacOS, iOS, Windows and Xbox.

Smilja

Zero bytes of the code on the legacy speakers are used for voice. All voice devices have at least 1GB of memory.

Unless you have access to the code base I don’t see how you can say this… So far, we’ve been told that all kit has to run the same version of software, and that the old kit can’t keep up with the latest requirements…. If they already have different kit working on different code bases, then there should be no problem at all making old and new work together seamlessly.

The firmware differs in aspects of functionality. E. g. the ONE would not be operational running firmware designed for the Beam.

»And the world is like an apple whirling silently in space, Like the circles that you find in the windmills of your mind.« (›Windmills Of Your Mind‹ [1967]. Music by Michel Legrand ; English lyrics written by Alan & Marilyn Bergman)

Show more replies

Sign up

Login to the community