Discussion Room - Pertino
-
Does the agent get pushed down from the Central console? Can security/access be configured at that point? Where does the network get added into the mix?
-
Doesn't MS have something like this... I can't recall the name of it now.
-
@Bob-Beatty said:
Does the agent get pushed down from the Central console? Can security/access be configured at that point? Where does the network get added into the mix?
No. It can't since there is no network until the agent is deployed.
The agent adds a TUN interface. That is what puts you on the network.
There is nothing to configure at the end point. You just put in the creds and let it join.
-
@Dashrender said:
Doesn't MS have something like this... I can't recall the name of it now.
Yes but requires enterprise licensing and a 100% Microsoft network and is IPv6 only and you would have to build out your own infrastructure for it. Would cost hundreds of thousands to duplicate that way.
-
The automatic connection piece is huge. Because it does this things like DNS and AD can work. Makes our lives so much easier.
-
I started using Pertino because I'm sick of RRAS and hate the costs of hardware VPN's. If I can keep a user always connected with minimal interaction, that's a huge plus and also makes them happy.
-
And you can go to the central web console and see what machines are connected and, if necessary, disconnect them.
-
Bob - thanks for setting this up! Much easier to stay on top of threads.
Security: Pertino is installed on each end point that you want connected to the network, so we are able to deploy 256-bit AES encryption end to end. The connection is an SSL connection. Data passes through our hosted "routers" to get to each destination. Each network is completely separate, and no data is stored or even cached. Device or user-based access to resources can be restricted with just two clicks.
-
@Josh said:
Bob - thanks for setting this up! Much easier to stay on top of threads.
Security: Pertino is installed on each end point that you want connected to the network, so we are able to deploy 256-bit AES encryption end to end. The connection is an SSL connection. Data passes through our hosted "routers" to get to each destination. Each network is completely separate, and no data is stored or even cached. Device or user-based access to resources can be restricted with just two clicks.
Now all we need is those [moderated] I went around and around with a while back who were saying you were gonna get hacked if you used Pertino.
I'm still trying to get the thing to work in a point to point fashion. Lots of folks have devices behind the firewall that won't be able to either use Pertino or they don't want to have the talk with users about installing it on their personal devices. If only you would release it in source I could compile the thing on something I can work with in that regards.
-
I think we missed mentioning file transfers and remote access over Pertino because they just seem so obvious. But they play big roles. RDP and SMB over Pertino are major use cases.
-
@PSX_Defector said:
@Josh said:
Bob - thanks for setting this up! Much easier to stay on top of threads.
Security: Pertino is installed on each end point that you want connected to the network, so we are able to deploy 256-bit AES encryption end to end. The connection is an SSL connection. Data passes through our hosted "routers" to get to each destination. Each network is completely separate, and no data is stored or even cached. Device or user-based access to resources can be restricted with just two clicks.
Now all we need is those [moderated] I went around and around with a while back who were saying you were gonna get hacked if you used Pertino.
I'm still trying to get the thing to work in a point to point fashion. Lots of folks have devices behind the firewall that won't be able to either use Pertino or they don't want to have the talk with users about installing it on their personal devices. If only you would release it in source I could compile the thing on something I can work with in that regards.
@psx_defector - We use outbound port 443 SSL to make the connection, so your users should be able to connect despite being behind the firewall. You can literally close all inbound ports and still connect to your Pertino resources.
Are you looking at getting it on your Linux boxes? We've got a Debian package available and an RPM in private beta.
No plans for true point-to-point connection at this point. We're still doing all the routing via localized hosted routers.
-
RPM is working great. Best of all the packages I think. We use Windows, Mac, DEB and RPM.
-
I might be able to do something with the RPM. I'm just not big on Debian distros. My initial messing around with a psudeo point to point in Windows failed miserably. It wouldn't do much without performing a bunch of crazy local routes.
Of course, compiling from source would make my life easier.
-
I'm not a DEB fan either but GroveSocial is on Ubuntu so we've been working with it recently.
-
@scottalanmiller said:
I'm not a DEB fan either but GroveSocial is on Ubuntu so we've been working with it recently.
Isn't it generally considered that debian based systems are for consumers and rpm based systems for business? That's what I always tend to see. Anything applied to business practices always uses RPMs. FWIW
-
Am I correct in my understanding that for every person who wants to connect to their work PC either directly or through RDS will require at least two licenses of Pertino? one for office computer and one for the home computer? If the user wants to use their phone as well, that would be a third, and a second computer from home, that would be a fourth Pertino license?
wow.. these licenses per user can add up fast.
-
I just watched Scott's YouTube video on Pertino, not bad.
But unlike a traditional VPN solution - you need to setup each endpoint specifically in the Pertino cloud, right? This can get costly pretty fast considering the shear number of end points. Once a VPN solution is in place it's pretty much done. Granted there's a lot of upfront setup and that takes time and money sure, but I'm guessing the pay back for a small business would be under a year compared to the on going expenses of a subscription solution.
What am I missing?
-
@Dashrender said:
Am I correct in my understanding that for every person who wants to connect to their work PC either directly or through RDS will require at least two licenses of Pertino? one for office computer and one for the home computer? If the user wants to use their phone as well, that would be a third, and a second computer from home, that would be a fourth Pertino license?
wow.. these licenses per user can add up fast.
If you are working it that way, yes. The billing is done on a per device basis which was a change from their per person billing. Per device makes much more sense in my opinion.
-
@ajstringham said:
Per device makes much more sense in my opinion.
Why?
-
@Dashrender said:
I just watched Scott's YouTube video on Pertino, not bad.
But unlike a traditional VPN solution - you need to setup each endpoint specifically in the Pertino cloud, right? This can get costly pretty fast considering the shear number of end points. Once a VPN solution is in place it's pretty much done. Granted there's a lot of upfront setup and that takes time and money sure, but I'm guessing the pay back for a small business would be under a year compared to the on going expenses of a subscription solution.
What am I missing?
No. You setup users and then when Pertino is installed they authenticate with those credentials and they're on. If you have 20 users with 60 devices total you don't have to setup for 60 devices, just 20 users. Also, a feature they added (FINALLY!) was being able to do batch adds. Used to be one at a time which was very limiting.
