4 ms·
> The issue with remote access is you need a service in the middle to provide that remote access, and provide it securely. This is a pain, but solvable by punc
by jjav 6y ago
> The issue with remote access is you need a service in the middle to provide that remote access, and provide it securely.
This is a pain, but solvable by punching holes in all the NAT pair combinations. At a previous startup we all communication peer to peer (phones, custom home devices, laptops), no data traversed our servers ("the cloud"). It worked beautifully.
- shaftway 6y ago> keep in mind the total addressable market is mostly people who don't want to deal with these problems. > This is a pain, but solvable by punching holes in all the NAT pair combinations. https://www.youtube.com/watch?v=i3RqDp7i308 https://www.youtube.com/watch?v=i3RqDp7i308
- jjav 6y agoI think I wasn't clear in the first post. The customer did not have to do anything (i.e. no need to configure any NAT passthroughs on their router etc), this was entirely transparent to the user.