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"

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!

Post-mortem: http://status.pertino.com/incidents/nk4btw5cdbnb

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.

@hubtechagain said:

hey @Josh i'm not sure if your 100% correct about devices that were connected. on one of my networks i've got 14 of 47 devices connected, 15 or so of my offline devices are devices that were connected earlier in the day and haven't been rebooted. i've noticed pertino has been acting a little funky since this weekend. Can we get a little more info as to what's happening?

That's what I've got from engineering and seems consistent from other customers, but more details will follow and I'd expect a post-mortem.

I'd expect all devices to auto-reconnect upon resolution, but I'll post here as soon as we're in the clear.

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

Hey guys,

I was on a demo but here's the scoop. It looks like any connected devices should be fine, but we're experiencing latency for devices that were previously disconnected and coming online. We've got it up on the http://status.pertino.com/ page.

@JaredBusch Correct. This has been the one downside for AD Connect if you have users that frequent the office. Traffic is forced across the Pertino interface. 430 will allow you to designate "zones" where devices use local routes instead.

@thanksajdotcom In regards to 370, we didn't push auto updates to all clients for subsequent releases. 420 is the first that everyone is getting.

@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.