|
A VPN (Virtual Private Network) would be one way to connect the two sites together to form a secure, private communications channel. Note this is a different form of VPN than that is being touted as "secure Internet" and "geo locking evasion" sold by VPN service providers.
Ideally, I'd have the VPN tunnel endpoints vested on the routers in each location, but not all routers offer such functionality and there's other ways to do it (for example, your NAS may have a VPN server app.) Usually, there's credentials involved in establishing (and if it goes down re-establishing) a VPN link, but it's often automatable - set it up once and forget about it.
That will provide you with the communications channel, then it's up to your software as to how it interacts - but you should be able to map an (old fashioned) drive handle or UNC path over such a channel.
We can get into the details if you are interested - for example you might need to ensure both sites use different IP subnets if you create a router-to-router VPN tunnel, maybe not if you use a VPN Server on your NAS. You may also need to sign up to a Dynamic DNS (DDNS) service and register a couple of (DNS) domain names so your and your friend can "find" each other on the Internet. Both will cost a bit of money, (annually,) but not much.
All streaming (indeed, all data networking,) involves a degree of "lag" (called "latency" in proper data networking speak) as all packet switching networks introduce latency at every "hop" along the pathway between source and sink devices - it's fundamental to how such technology works, it simply cannot be eliminated entirely. The goal is to design/manage latency to an acceptable level. When using a heterogeneous network that you don't own or control (ie the Internet) there's very little you can do about it unless you want to spend huge amounts of money with service providers for guaranteed minimum performance levels. Most people prefer to "just live with it" in a quid pro quo for cheap Internet service. |
|