@danno Can we take a step back and (for my benefit) do a sanity check as I may have misunderstood your problem.
Can you explain what exactly you're doing that doesn't work (when connected via VPN). What do you see? Are there any error messages, etc.
Ok, another pass at this. The reason I am going through this "exercise" is to apply a VPN to our home network. We have several ipcams and I am no longer willing to port forward devices or enable router remote administration. I also want to remove our R6400 Netgear which does not support OpenVPN etc.. Besides, it is slow. I also like the idea of defeating Geofencing while we can.
Our Eero's are supplied by the ISP and have no USB ports. I want to take advantage of USB storage while away from home and get rid of the R6400.
While on the home LAN with the VPN off, I can use Windows to MAP the USB drive attached to the EBG15. The Samba server shows up under the Windows "File Explorer" "Network" tab/twisty/carat. So the router(server) is discovered and windows will allow me to access the drive folders so I can work with the files. I can use FileZilla FTP (TLS) to access the drive as well.
Regardless of my being remote or on the home lan, as soon as I connect to the VPN, the router(server) is removed from the "File Explorer" network list. I do not have to refresh it. It is gone. No error messages, nothing. Just gone. However FileZilla will still allow a TLS connection to work with the files on the EBG15 USB drive. If I attempt to MAP the USB drive using Windows File Explorer since I know the IP address or server name I get this;
If I try from my phone with the VPN active, Cx File Explorer cannot connect to the IP address it cannot connect to the user at the ip address.
These results are the same as long as I connect to the VPN on the client regardless of being on the lan or remote.
With the VPN up, I can however, review all of the ipcams, and the USB drive hung off our old R6400 which is running as an AP with the wireless off since we have the Eero's performing that function.
Hope this helps.
At this point it, to the uninitiated naive novice I am, it looks as though the only course of action is to change the SMB configuration, unless there is a way to route the tunnel to the LAN subnet without causing loops or other issues. At least that is what OpenVPN is recommending as a solution as I posted above.
Post #5 above tries to illustrate the topology.