<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div apple-content-edited="true" class=""><span><font size="2" class=""><span style="color: rgb(0, 0, 0); font-family: Menlo; font-size: small; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><br class=""></span></font></span></div><div apple-content-edited="true" class=""><div style="orphans: auto; widows: auto;" class=""><span style="orphans: 2; text-align: -webkit-auto; widows: 2;" class="">This is all sounding _very_ familiar! We do quite similar things using RPis here too, right down to the reverse SSH tunnels. Incredibly useful for remote diagnosis, visibility and proactive response. Our sample size isn't huge, only just over 3X what you've mentioned, but thus-far we've had zero hardware fails and some of them have been deployed and active for over 3 years.</span></div><div style="orphans: auto; widows: auto;" class=""><br class=""></div><div style="orphans: auto; widows: auto;" class="">We also designed and 3D-print our own rack-mount (or wall-mount) cases which expose only the ethernet and power ports, with the power port right there at the front of the rack so they customer can easily pull it out and plug it back in again if needed.</div><div style="orphans: auto; widows: auto;" class=""><br class=""></div><div style="orphans: auto; widows: auto;" class="">Pete</div><div style="orphans: auto; widows: auto;" class=""><span class="Apple-tab-span" style="orphans: 2; widows: 2; text-align: -webkit-auto; white-space: pre; font-size: small;"> </span></div></div><font size="2" class="">
</font><br class=""><div><blockquote type="cite" class=""><div class="">On 12/02/2016, at 1:38 pm, Graham Freeman <<a href="mailto:graham@nerdventures.com" class="">graham@nerdventures.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Yep, with my managed network customers. I have a small number of customers, each of which is meaningfully profitable, so a $100/year deployment of a Pi with a fancier USB wifi interface is well worth it. I set up reverse SSH sessions (originating from the Pi) to distinct per-customer bastion hosts on my management networks, so that the customer's firewall and/or dynamic-IP issues are non-issues. I use Chef, git, and some shell scripts for config management.<div class=""><br class=""></div><div class="">I've had 1 Pi fail out of 20. So, reliable enough, though of course not a huge sample size.</div><div class=""><br class=""></div><div class="">It's great to be able to say "Hey, customer, I noticed a routing issue impacting your web-based accounting software on your ISP A, so I automatically promoted ISP B to primary for that route. Monitoring (graph screenshot attached) indicates that this was an effective workaround. I'll restore normal routing or promote ISP B to primary off-hours tonight, depending on the outcome of the trouble ticket I've already opened about the issue." before the first tech support call comes in. Similar customer success story when I call them immediately after getting an alert from the Pi-connected UPS informing me of a power outage. This kind of thing makes the next 2-year renewal negotiation an easy one. :)</div></div></div></blockquote></div></body></html>