request for help with networking sorcery (a bit long) 

let's see if i can explain this in a way that makes sense and doesn't make me sound silly

i want to set up network file access for my home's local network, so i can access files from various devices without having to manually copy them over. every potential client i have is perfectly fine with SMB 3.0... except for one (a playstation 2 with some homebrew software), which only accepts SMB 1.0 for whatever reason. i don't want to enable a deprecated file sharing protocol for the entire network, so i'd like to limit it to as close to the troublesome client as i can.

is it possible to set up some kind of "relay," like in the diagram, that presents a network share or a subset of it to the ps2 via SMB 1.0 while the rest of the network can use newer protocols?

re: request for help with networking sorcery (a bit long) 

@typhlosion if you're using samba, you could run a second smbd instance on a different port that has SMB1 enabled and has very restricted access controls.

otherwise, I have no idea if a transparent SMB relay exists, but you could always just have a different machine mount the PS2 share with e.g. Linux's CIFS support, and then run its own smbd that exports that as a share :p

re: request for help with networking sorcery (a bit long) 

@typhlosion btw, if it would help, I have an smb.conf I set up for my PS2 that ought to still work correctly, and I can share some relevant config settings

Follow

re: request for help with networking sorcery (a bit long) 

@Skirmisher that would help, thank you!

re: request for help with networking sorcery (a bit long) 

@typhlosion here's what I came up with

[global]
# default/irrelevant entries omitted

# enable SMB1
server min protocol = NT1

# enable NTv1 encrypted password support
ntlm auth = ntlmv1-permitted

# restrict clients - can be set global and/or per-share
# accepts several forms of host specs, see smb.conf(5)
hosts allow = 192.168.

[PS2]
path = /home/skirmisher/stuff/PS2
comment = Open PS2 Loader
# arbitrary user, use smbpasswd(8) to create & set pass
valid users = opl
# never try to set owner or ACLs
inherit owner = Yes
inherit acls = Yes
# unfortunately necessary last I checked
writeable = Yes
# client assumes role of (UNIX) owner of files, to simplify permission checks
# might make "inherit owner" redundant, but eh
force user = skirmisher
Sign in to participate in the conversation
Awoo Space

Awoo.space is a Mastodon instance where members can rely on a team of moderators to help resolve conflict, and limits federation with other instances using a specific access list to minimize abuse.

While mature content is allowed here, we strongly believe in being able to choose to engage with content on your own terms, so please make sure to put mature and potentially sensitive content behind the CW feature with enough description that people know what it's about.

Before signing up, please read our community guidelines. While it's a very broad swath of topics it covers, please do your best! We believe that as long as you're putting forth genuine effort to limit harm you might cause – even if you haven't read the document – you'll be okay!