@scottalanmiller said:

Oh, if on CentOS 5 you are out of luck. Pertino has always been known to not support libraries that far back and because it is so old they have no intention of making it work on a system so old. Sorry, that's just how that works. We have one database server that can't upgrade from CentOS 5 right now and it is left without Pertino 😞

Ah ok. Yeah, they're still using CentOS 5, and I have the latest Unitrends. Dang it...

@scottalanmiller said in Show Some Vendor Love:

@Grey said in Show Some Vendor Love:

@scottalanmiller said in Show Some Vendor Love:

LOL, it's true. Vendors that gave up or screwed the pooch. Pertino did fine they just... left I guess.

They got bought by Cloudflare. I still use their services for the 'three free' and it works well enough.

When did that happen? they were with Cradlepoint for the longest time.

That's right. I misremembered. Too many companies with cloudthis and whatever.

Installing the update manually

@Dashrender said:

I'm a bit lost.

You have two NASs at home mounted to a Linux box, that you are then sharing to CIFS so you can mount them on a Windows box?

Is the Windows box not on the local LAN? If not I guess that's why you have Pertino as part of this, because you are Pertino'ing from a non local Windows box to the Linux box which is offering a pass-through to the NASs?

If your Windows box is local to NASs, why bother going through the Linux box?

The Windows box and the Linux box are both on the same LAN as the NASes. This is more so I can access the NASes easily remotely on my Pertino network.

@Josh said:

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

Congratulations!

And the exact problem I am having is that the Dynamics NAV SQL Server and the RDS server when both put on Pertino were routing all traffic over Pertino instead of locally. I took the SQL server out of the network (made its own network) and everything started working again.

What Pertino is waiting on me for is some packet captures that I have not had time to create.

Because I seen odd behavior of LAN devices without Pertino also having problems access SQL. Those devices have the NAV client locally installed.

"Insanity is repeating the same mistakes and expecting different results." -- Narcotics Anonymous

@art_of_shred said:

What's wrong with a too-tight shirt that says "cheap. fast. easy. just the way you like it."? That should be the only way to wear it!

@Dominica said:

Mine is tight in just the right spot to make the slogan especially appropriate, lol.

Maybe not wrong on @Dominica, but not on me!

Well in a hosted system you don't have analogue lines so that isn't a factor for us.

that is cool!

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

Here is the additional log info:

#systemctl status pgateway.service pgateway.service - SYSV: The Pertino Client provides access to the Pertino Network. Loaded: loaded (/etc/init.d/pgateway) Active: failed (Result: exit-code) since Tue 2014-09-02 23:33:27 EDT; 3min 48s ago Process: 21792 ExecStart=/etc/init.d/pgateway start (code=exited, status=127) Sep 02 23:33:27 to-lnx-oc1 pgateway[21792]: /etc/init.d/pgateway: line 9: /etc/init.d/functions: No such file or directory Sep 02 23:33:27 to-lnx-oc1 pgateway[21792]: /etc/init.d/pgateway: line 12: .: /etc/sysconfig/network: is a directory Sep 02 23:33:27 to-lnx-oc1 pgateway[21792]: Starting pGateway: /etc/init.d/pgateway: line 25: daemon: command not found Sep 02 23:33:27 to-lnx-oc1 systemd[1]: pgateway.service: control process exited, code=exited status=127 Sep 02 23:33:27 to-lnx-oc1 systemd[1]: Failed to start SYSV: The Pertino Client provides access to the Pertino Network.. Sep 02 23:33:27 to-lnx-oc1 systemd[1]: Unit pgateway.service entered failed state.

Very impressive, sir! Kudos to you.

@Josh said:

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

Lol

@ajstringham said:

They are almost identical in how we are standing! LOL

No real surprise. You're basically SAM Mark II aren't you? The younger, newer model. I expect you to eventually overtake him on Spiceworks points and blog posts.

That works for the web interface, we were hoping for the SSH interface.

For site to site I prefer IPSec. OpenVPN is good but for static links I like IPSec better.

Pertino is a full mesh so you want every single device on the mesh. Very different approach.

How many devices do you have?

@scottalanmiller said:

@david.wiese said:

A.J. I'm not trying to be mean but why are you constantly plugging your website here instead of just posting your review on ML. It kind of defeats the purpose of the review section. I fully understand that your site is new but can you find a different way of plugging your site? To me its unprofessional to go on a site and say hey go to mine, i have all of these reviews and so on.

Plugging his writing is fine. There is even a self promotion category just for that. A review in the water closet isn't the best taxonomy but I feel that that is all.

Thanks Scott.