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 I don't know (I haven't touched SMB in like two decades) but I think it's a very interesting question!
if read-only access is enough you might be able to run two separate Samba servers with different configurations but serving the same directories on the same machine. you'd need them to either listen on different ports or different IP addresses, but in a home network it's not too hard to assign as many addresses as you want to the same network interface. then you can apply different firewall or ACL rules to each.
also have you already checked whether Samba has config options for allowing different protocol versions on different listening sockets? some server software supports that kind of thing but as I say I haven't looked at Samba in a long time. if that's an option then I'd expect even read-write access ought to work fine.
finally there's the somewhat brute-force approach of faking a "proxy" like you want by mounting the SMB share on another machine and running a separate copy of Samba there. I'm skeptical whether that's any better than running two copies on the same machine though.
