[pula123]

Hi.
I'm using the latest Firmware: DD-WRT v3.0-r43886 std (07/21/20)

My problem is Mac computers and Apple TV not discovering/reading the SMB-share.

When i am using Linksys firmware MacOs reads the drive, but with some connection problems from time to time, thats why i switched to DDWRT in the first place, thinking things will be better. I have spent countless days and hours trying to configure both Macs and DDwrt and reading online without any success.

A friend of mine with a windows PC could connect and find the share without any problem, so its clearly a problem on Apple devices. Is this driver related and can it be fixed? Any other suggestions to what i can do or should i just get a new router?

THANKS

[SurprisedItWorks]

I'm guessing you're way ahead of me on this one, but just in case...

My own issues with SMB in a recent (April) release turned out to be that I had not set the "Minimum Protocol Version" and "Maximum Protocol Version" in the GUI>Services>NAS Samba Server section. The default values, at least in my case, were to only use a very old version of the protocol. Setting them for minimum 3.0 and maximum 3.11 fixed everything.

I gather that Samba issues in recent builds is due to a move a small number of months ago to Samba code embedded in the linux kernel. It's taken a while to get the kinks out. Maybe some are still in there.

[kernel-panic69]

I think Macs require the use of Avahi by way of Entware or something. This is why I don't use a router as a file server (except for FTP)

[pula123]

[pula123]

[whaleyland]

I am having the same exact problem and it has only been happening for about six weeks, although it also happened last year for a few months until I found some solution online (which I can't find now but shouldn't have changed since). When everything is working, I successfully NAS share two 3TB USB drives (one using a USB2.0 port) from my FlashRouter/Linksys WRT3200ACM which I bought back in August last year.

In short, my hard drives appear to time out once my Mac goes into sleep mode for a few minutes. It happens every day in the morning and night, and sometimes twice at night if I am not using the computer continuously. What's worse though is that the Apple TV is basically unusable if the drives aren't responding because most of what I watch is played through Infuse Pro directly from my hard drives, including my entire movie collection from the US and many of my TV shows. The only solution to this problem that I have found is to restart the router, but then this often causes the 5 GHz/802.11ac band to remain off on restart, leading me to restart the router again (and again occasionally) until the higher band network is broadcasting again. It is super frustrating and my partner can't watch her shows if she is at home while I'm at work unless she first restarts the router from behind (again, sometimes multiple times).

I have also just tried turning the Samba off, Apply Settings, then on, Apply Settings, but then the internet stops responding, although the drives do load paradoxically. Other than that, I haven't changed a single setting or updated the router/DD-WRT firmware since I bought the router, so nothing should have changed. The system is still currently running DD-WRT v3.0-r40260 std (07/09/19) since I don't want to mess up the preconfig settings and, until recently, it was working just fine as is. As with pula123, is there any workaround for this? I am wasting a lot of time throughout the day stressing about this and restarting the router, which probably isn't that good for it either.

[ad19]

Unless you are looking for something fixed in the latest versions, I would suggest going back to r35681 or r40009. Very stable and no problems with Mac using SMB or Bonjour.

[kernel-panic69]

Mac needs to fix their SMB / network discovery implementation. Or people need to adapt. I don't think BrainSlayer is going to muck with adding anything else that will cause flash size constraint issues.

[pula123]

[pula123]

[blkt]

Mr. ad19 gives great build advice for Marvell 3200 series (also SurprisedItWorks for 1900 series).

One of the last builds before the introduction of CIFSD in-kernel Samba is r41813 (Dec 2019).

If you want to read more, below is a discussion (thanks Mile-Lile).

https://github.com/namjaejeon/cifsd/issues/349

[SurprisedItWorks]

I agree with a poster above that 40009 was a really trouble-free build. It is a shame though to go back that far (over a year) and lose all the improvements and security patches that have appeared since. I can't imagine going all the way back to a 35*** build.

Also, my mac seems to map my router's large USB/Samba ext2 flash drive without problem. I'm on build 42926 (in the download pages as 42925). I also use it from Windows 10 and Fedora linux.

The new-build threads seem OK on Samba matters through 43099. Since then, however, there are Samba-trouble posts for every build.

Rather than use Apply on the NAS page to wake up a stuck Samba system, you can do

stopservice samba3
startservice samba3

either in the CLI or in Startup code. I needed this in several builds back in the winter. I do not need it in 42926.

[kernel-panic69]

[pula123]

[SurprisedItWorks]

I'm not very knowledgeable about Samba and various filesystem types, but my limited sense of it is that Samba hides the native filesystem type of a share and instead presents a sort of uniform "Samba type" to the network. So a share on the network looks the same no matter whether the underlying filesystem is formatted as ext4, NTFS, or whatever. I have no idea how well dd-wrt Samba handles HFS+ as an underlying fs type. I keep my drives formatted as either ext4 (if journaling is desired) or ext2 (if not), because those are native linux types and dd-wrt is a linux system.

I have noticed also that the Samba presentation of owner/permissions seems to contain less information than I am used to in linux. The "group" of a file doesn't appear to exist, for example.

But I am ignorantly rambling here. Let's let someone with an actual clue speak up.