SMB2 (or SMB3) support must be supported NOW!

I don’t think, @PudgyChicken, that you understand what has been discussed. There is no additional memory space in which they could store a backported version of the kernel. The current kernel appears to have taken all available memory. 

And there just isn’t any spare space on the devices at all, inside or external to the kernel, without removing features. 

Now, if you’re talking S2 devices, that’s a whole different beast, and I could agree with what you’re saying. Which, if you read the thread, we’re all hoping at some point they’ll do. But, as @controlav  and others have pointed out, the amount of folks that want this, while vocal,  is relatively small. It may not be financially intelligent to do that work, which is likely both extensive and costly. It may behoove them to put their limited resources elsewhere, as there are already several solutions, as described in this thread. 

This doesn’t sound like a plausible reason for not supporting SMB v2/v3. 

IF Sonos needs to have SMB v2/v3 support at the kernel level, there is probably a way to backport the patches that add support into the kernel they’re currently using. Crazier things have happened. 

However, not everything must be implemented at the kernel level. There’s absolutely no reason that they could not use an SMB client implementation that runs in userland. Many programming languages have third party (or even first party) SMB client library implementations. I have no doubt that Sonos could swap out their current SMB integration with one of these. 

This issue reeks of either incompetence or indifference, neither of which is acceptable when it comes to a company selling hardware this expensive.

That might work if you assume that Sonos hasn’t made the change out of spite, rather than a forced  business decision.

If you read the thread, it’s relatively certain that the issue has more to do with available memory on the devices to contain a Linux kernel that’s been updated to use higher versions of SMB. Not some sneaky desire to repress people like me who play from their NAS almost exclusively. 

Maybe a all should complain by email to the Sonos CEO: ceo@sonos.com

That’s his/her email address according to:
https://support.sonos.com/s/contact?language=nl_NL

I’ve already send an email, wo is going to follow?

For Systems running S1, I doubt if there will ever be and SMB upgrade.  The memory constraints of those speaker restrict what can be done.

For S2 it may be possible, but probably requires a significant development commitment, and given the bulk of new customers tend to use streaming services (and that there is a workaround), I can’t see this being high on the list for Sonos.

I run a dedicated Pi based NAS running SMB1 ,for my Sonos music only, that is sacrificial.

Compared to the power that a Sonos device uses in sleep mode, roughly 3 to 8 Watts depending on the device, the 1 Watt that a Pi Zero draws isn’t much.

https://support.sonos.com/s/article/256?language=en_US

Such a shame that the “solution” requires yet another box burning electricity when we should be trying to reduce energy consumption.

If you’ve read the full thread you’ll know there is no official answer. 

I read the full thread but all I see is speculation.  Is there an official answer on why SMB2/3 isn’t supported?

Does anyone know why Sonos doesn’t support SMB2 or SMB3?

Ah, understood. My apologies if my response also sounded terse, the reasons around this have, as you’ve seen, been discussed over and over in this thread. As has the fact that Sonos doesn’t tell us what is on, or when we should see anything from the roadmap. 

As you’ve seen from controlav’s posts, there are some hopeful signs. However, certainly I was hoping for forward movement long before this date, but having been in these sorts of software update processes before, am not surprised it hass taken this long. The real question is still whether or not Sonos considers this an important enough issue (probably decided by number of users, which has been previously conjectured to be in the single digit percentages) for them to dedicate coding resources to. 

As has been stated before, we just don’t know, and we won’t know, until or even if Sonos releases it. 

Being a user of local files myself, I certainly have hopes that it will come to pass. But I’m also not holding my breath. 

Michel,

May I recommend that you read the thread in which you’ve posted? 

There are signs that an updated SMB stack is on its way, for S2 devices. The recent regression with non ascii characters on the Sonos SL implies that changes are afoot, so there are faint signs of hope.