Hey guys and gals - What are we calling Mango Lassis these days anyway?

I have a proposition for you. We are introducing our first visibility app called Bandwidth Monitor.

Here's the synopsis:

Bandwidth Monitor is an application that provides bandwidth usage visibility across the entire network and at a fine-grained device or user level. With this app, you can identify insights such as the top bandwidth consumers, peak usage times & servers/resources that are being taxed the most. All this information helps in cost control, compliance, operational planning and productivity enforcement.

Here's my ask:

I need 10 volunteers to dive into the app with our VP of Product via approximately a one hour web "experience". Our goal is to recruit a range of user backgrounds (ie MSPs/IT consultants, IT Pros @ companies 100-500, and IT Pros @ smaller offices up to 100).

Requirements:
You have remote users or multiple offices
You are a current Pertino customer or are at a minimum, familiar with Pertino
You realize that a bandwidth monitor is not an actual monitor that you plug in
You are a member of the Mango Lassi community

If this is of interest to you, please email [email protected] and I'll get you on the list. Again, we're looking at the first 10 that fit those profiles.

Thanks Lassis!

@scottalanmiller

Hey guys. Josh from Pertino here. Scott is correct. Install Pertino on the Vcenter and it will feel as if you are directly connected.

iOS is definitely on the roadmap...

@IRJ Sorry, I've been disconnected with a new addition to the family. Have you emailed [email protected]? I've also never gone through the install with a Linux GUI...

Just a quick update. I'm sure anyone impacted has been following the status page, but we've been all clear for a few hours now and are closely monitoring all services.

Just trying to help out a customer find some good full-time IT support working for the county. Do you all know anyone in Lubbock/Amarillo area?

@JaredBusch I actually think we do still have some of those Beta shirts in a closet somewhere. I got a text from one of the SpiceHeads that took one of our shirts. He said that his wife was looking for a comfy shirt to wear and just happened to grab ours without reading it first. She walked in the room and he just started busting up laughing...makes it all worthwhile!

Well I'm glad I didn't come in too soon! SAM hit the nail on the head. We provide the connectivity. You provide the services and permissions.

I haven't heard a ton of great things about Windows syncing capabilities, but Pertino can provide the connections depending on OSes involved. You could also look at OwnCloud, Sher.ly, etc. Much cheaper alternative to cloud storage, just be prepared for versioning issues with any cloud storage solution where you are enabling local copies.

Adam - welcome to the community and overlay networking!

Not trying to hijack the thread as this appears to be a ZT feature request topic, but since Pertino has come up a number of times, here are the answers:

DNS: PITA. We solved it by using customer internal DNS in AD environments. This is a solution for many customers, but not the end all. Without some type of local integration, overlay networks can never really be used for an internal company network because protocols will not translate.

Free plans: all trials revert to a free network for up to 3 devices; existing free plans with more devices are still live - thanks beta testers! Take the class-action suit to LMI

Chef/Puppet: you can automate Pertino installs with your orchestration tools. We even have a Docker compatible client for cloud-bursting, cross-DC networking

LDAP integration/custom UI: We've got some APIs already available, some in the works. Plan is to make it so if you don't want to, you never have to enter the Pertino console.

Best,
Josh

Jumping in a bit late, but we do have a solution for optimal local routing. It is called SmartZones and is available with free and paid subscriptions. To set it up, look under the network tile in the app.pertino.com console. The short of it is that it allows you to identify a subnet and when devices enter that subnet, they choose the local route over Pertino. Here's the blog from when it was introduced.

Now the longer answer.

In a standard deployment, Pertino uses local name resolution and traffic can be routed locally instead of across the Pertino interface. The reason I say "can be" is because it is really tied to race conditions in the protocol (ie LLMNR in Windows). When you add AD Connect to enable your internal DNS to propagate across Pertino, all traffic ends up being forced across the Pertino interface. Smartzones solves this.

Hope that helps!

I have a buddy in the UK that has a few performances cars (ie Porsche, Lambo, Range Rover), and his daily driver is the Abarth! That was pretty surprising to me...

Side note: It must be nice to have "company cars"

@scottalanmiller @steve

That is too cool. I'm thinking we've got a case study in the making.

I'm glad I got on here early. I'll be able to sell my "Josh" handle for some serious bucks one day!

@Carnival-Boy a little secret...iOS beta will be announced for October.
@JaredBusch Your explanation is perfect. Pricing is fine for small business today and your customers aren't using the apps so you don't want to pay for them. That's exactly what we're doing. Increasing pricing for businesses that consume apps.

When we launched the original pricing we were solving entirely different challenges than we are today. Anything "more advanced" required some creative minds (like SAM with the original AD integration). Now we're providing those for businesses that need them.

Hope that helps and looking forward to seeing you guys next week!

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.

@Bob-Beatty said:

Wow - this is a plethora of information. I've read all of the posts and now have learned more than expected - I was looking for Scott's video, can you throw that link in here? I didn't see it. Thanks for all of the input, this is a great resource - now, can we take this post and file it as a "whitepaper" of sorts, or just leave it as it is for users to search for?

We also host weekly demos on Thursdays at 2 PM EST. Here's the latest registration link.

@dashrender In regards to the site to site configuration, that is an ongoing discussion over here. For your use case of 5 devices at each location, then it's less than $300/year and those devices are no longer location-dependent. It's a compelling story for many scenarios. Once you get a greater number of devices on the local network then there are more factors that play into the ROI.

Where Pertino really changes the game is in enabling you to instantly and securely connect seemingly disparate devices, whether physical or virtual, located behind firewalls that you don't control. Then there's the "always on" connectivity for replication, eliminating annoying timeouts, user error, yada yada yada...

And like the guys have said, today it's all about being able to easily deploy and manage networks and making it easier for your users to access the resources they need.

@ajstringham Hey AJ...good question and one we get frequently. We call this feature "grouping". It's essentially like creating a VLAN; one resource that can be accessible via multiple neworks, without exposing said networks to each other. This is a roadmapped item that is becoming increasingly important for our MSPs (program to be launched this month) and to enterprise customers.

@josh owes all of you beers for not supporting CentOS 7 yet...

We test it with movies streaming off a Plex server. You should give it a go!

http://www.dell.com/learn/us/en/uscorp1/secure/2014-11-05-dell-simplify-transform-cloud-experience

A few of the Pertino guys just came back from Austin after demoing Pertino at Dell World. You're probably wondering, doesn't Dell already have networking equipment in their portfolio (Sonicwall), so why partner with Pertino?

Cool story: Dell acquires Enstratius (web-based management tool for hosted instances). They start to think, where do we fit in in this whole cloud movement? We make hardware. They realize, hosting is a race to the bottom, and you have to continuously invest to differentiate yourself, so let's just make it easier for end users to transition. Thus we still sell hardware (hopefully to end users and data centers) and now we inject ourselves into the movement. Announcing: Dell Cloud Marketplace

The premise is simple. They create a platform that is somewhat like the Priceline (shop your provider) of hosting providers that abstracts all the intricacies of deploying (proprietary configurations, terminology). Let's make it super simple to manage and deploy, and give you one throat to choke. Makes a lot of sense.

Initial technology partners for the announcement: Docker (software dev and deployment), Delphix (data migration), and Pertino (secure networking)

The idea is this will take the fear out of deploying in hosted environments by removing the unknown, vendor lock-in, and distributed management and billing.

Do you think Dell will succeed in becoming relevant in the cloud conversation with this type of offering?

@JaredBusch

That is the one issue in today's version of AD Connect. There can be suboptimal routing when your Pertino-enabled devices are local to the resources they are accessing (unless you disconnect Pertino on those laptops when they hit the LAN).

A near-term release has additional filtering that detects connectivity based on SSID/network and determines routing.

@thanksajdotcom Client updates are automatic, however they do not necessarily get pushed at the same time as releases. The Windows update should go out very soon. In the past, we required manual updates.