[the heatkiller]

Hi
a few days ago my SMB server stopped working.
I can't figure out what's wrong.

I've tried downgrading the firmware from build 58362 to build 48886 without any success

I've searched and searched the forum but haven't found anything that helps. Is my router broken?

Right now I'm running build 58362 and I've set up the SAMBA server through the GUI. Is there a way to do it from SSH? Because I think the SAMBA server isn't getting the right name that I gave it.

[the heatkiller]

It must be said that I cannot access from android, windows or linux or google TV where I normally use it

[egc]

Have you restarted the router?

Is the USB formatted as ext4? If you are using ntfs then the volume may have become dirty and you have to run chkdsk

[the heatkiller]

yes I have tried resetting it but it didn't help.

My drive is a USB pen which is formatted NFTS.
Now I have connected my old Linksys 1900ACS V2 and here everything works with build 48646.

but can it matter if it is NTFS or ext4?

[the heatkiller]

here are my USB settings

[egc]

NTFS is problematic use ext4 or ext2

[the heatkiller]

Now I have formatted my drives to ext4
I have set my WRT1900ASCV2 to run NAS server. and everything works both android, linux and windows 11.

Right now my WRT3200acm is running as a slave to my ISP provider router.

I have found out that as soon as I set my WRT3200ACM to run as a main router and set Vlan to 101 then my SMB stops working on the network

So I think it is the Vlan settings that are causing problems.
I run this command to get Vlan to work on the router

swconfig dev switch0 set enable_vlan 1
swconfig dev switch0 vlan 1 set ports "6 0 1 2 3"
swconfig dev switch0 vlan 2 set ports "5 4t"
swconfig dev switch0 vlan 2 set vid 101
swconfig dev switch0 set apply

Is it Vlan 1 that I need to change something on?

[egc]

VLAN guides are stickies in the Advanced networking forum

[kernel-panic69]

And VLANs as well as interface names on the switch have changed on Marvell in current releases without any updates to configuration practices that I'm aware of.

[ho1Aetoo]

The old Marvell switch driver only supported 64 VLANs so BS has ported the new DSA driver.

Therefore it was not possible to create a VLAN101 via GUI (sticky).

I personally don't own a Marvell router (WRT serie) and without remote access I can't create any documentation.

(not that I want to as I have already created 3)

and the DSA driver is only used from build ~r59887

[kernel-panic69]

Well, I am now behind CGNAT due to an internal changeover with mine and other local ISPs, otherwise, it would be "a flip of the switch" to grant access. This is for the 3200 at residence and otherwise that I know of, so far. If any of the inventory connected to previous ISP are not behind CGNAT, I'll see what I can do. AFAIK, the VLAN Tagging on the Setup -> Networking tab should work in current releases.

EDIT: Correct, max VLANs on Marvell was always 64 prior to recent changes (but somehow was able to be worked around via swconfig, etc.?):

https://svn.dd-wrt.com/browser/src/linux/universal/linux-4.9/drivers/net/phy/mvsw61xx.h?rev=31574
https://svn.dd-wrt.com/browser/src/linux/universal/linux-4.9/drivers/net/phy/mvsw61xx.h
https://svn.dd-wrt.com/changeset/59852

[ho1Aetoo]

https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=334342&start=5

should now work, instead of “eth0” use the WAN interface which is now called “wan” I think.

for the older builds this should work with eth0 as described in the sticky.