Multiple share paths for same folder

[stej]

My NAS has interfaces on a bunch of different subnets to facilitate access to the shares for clients in each one.

So the same network share is available under let's say 192.168.1.2\movies and 192.168.2.2\movies and 192.168.3.2\movies

And depending on which subnet each client lives in, they access their subnet's nas address to avoid overloading the router with smb traffic

My problem is that as far as I can tell Jellyfin only allows entering one network share path for each library folder.

I've tried a few different syntaxes to see if it would accept multiple listings, but couldn't make it work.

Is there a way to enter multiple network paths for libraries? And if not, where do I sign up for a feature request?!

[TheDreadPirate]

When adding folders to a library, isn't there a "+" to add additional lines? Several of my libraries have multiple folders, but those are local directories. Why would that same ability not extend to SMB paths?

[stej]

When adding folders to a library, isn't there a "+" to add additional lines?  Several of my libraries have multiple folders, but those are local directories.  Why would that same ability not extend to SMB paths?

Unfortunately, the "+" is only for additional folders under the same library. There isn't a + option for extra let's say aliases for a single folder.

For now I worked around the problem with dns redirections for the dhcp servers of each subnet, but it's far from ideal.

I don't like it, I don't trust it, it produces extra load for the router for no reason and the only way to enforce it to clients would be by dns hijacking which I don't wanna do.

So yea, it would be much better for Jellyfin to actually support multiple alternative network paths for clients to look up.

[TheDreadPirate]

Will each user always come from the same subnet? If so, you could create multiple libraries for each subnet and make only the appropriate library visible to the appropriate user.

[stej]

That sounds even messier than my current workaround and would require extra manual work for every user and hardcoding stuff that really shouldn't be hardcoded etc.

Anyways, appreciate the suggestions. My original query has been answered I suppose, there isn't some hidden way for Jellyfin to provide a list of alternative paths to a library folder for clients.

There's a few messy workarounds but ultimately can only be fixed by the devs adding it as a feature. Not holding my breath obviously, heh.