Does per-incident support make sense in the cloud?

Although I haven’t looked at this deeply I know that AWS, and it appears Azure as well, only offer subscription-based support models.  On-premises Microsoft offers both subscription-based models and per-incident support.  So does per-incident support make sense in the cloud?  I really want to hear from customers across cloud platforms, although my musings are clearly AWS-focused.

AWS does not currently offer a per-incident support option, and spending a lot of time in the Amazon RDS Forum one sees the potential for them to offer one. Keep in mind that the forums are targeted at community discussions and not individualized technical support from AWS. If you check the comparison of AWS Support plans you see that Basic Support, the free option, does not include Technical Support. So customers post technical support requests in the forum and, most of the time, no one from AWS responds.  On top of that, whereas there is a strong culture of community participation in (both company and third-party) forums on Microsoft offerings, that culture is not as well developed around AWS.

AWS does offer an inexpensive support plan for Developers, though it can be used to obtain support for production systems as long as you can live within its limits (e.g., only email, respond only during business hours, 12 hour response time on impaired systems). What you can do if you have that once/year kind of need for technical support is sign up for developer support, open a case via email, then cancel support before the next billing cycle. If your monthly spend with AWS is under $1000/month ($966 actually) then you effectively have a per-incident support price of $29. If you are spending over $1000 your effective per-incident price is 3% of your total AWS bill for the month using this “subscribe only for a month” technique.

For more critical support incidents you could sign up for AWS’ Business support for a month then cancel that.  If you do this for a single incident it effectively costs you $100/incident if your spend is under $1000 a month, but escalates rather quickly as it is 10% of the monthly bill.  Actually the 10% applies to the first $10K, with higher spend levels getting volume discounts, but we will ignore that for this discussion.  Using the current Business support subscription pricing in the “subscribe only for a month” technique to obtain per-incident support only makes sense for smaller customers.

Figuring out if “subscribe only for a month” pricing is an adequate substitute for a true per-incident offering could use a benchmark, and we have one.  Microsoft charges $499 per incident for its on-premises (non-consumer) products.  If AWS were to price per incident support comparably you would need to be spending over $16,700/month for that to be cheaper than just signing up for Developer Support for a month then cancelling.  The Microsoft per-incident offering is closer to AWS’ Business Support, but even there the “subscribe only for a month” technique is cheaper as long as your monthly bill is under $5000.

To put this further in perspective, how many organizations are spending more than $200K/year (the breakeven point for our per-incident benchmark vs one month of Developer Support) on a cloud provider?  Or $60K/year (the breakeven for Business Support)?  I’m going to speculate that for 99.9% of customers the “subscribe only for a month” technique is a better option than per-incident, based on the chosen benchmark.  So if this is true in the cloud, why isn’t it also true on-premises?  On-premises support subscriptions are generally annual (or longer) contracts, so you can’t subscribe for a month then cancel.

Is Microsoft’s $499 benchmark the right comparison?  On the surface it seems expensive, but that is because it is one size fits all.  From things that can wait a day and then resolve with 15 minutes of effort to production system down situations that need fast response to complex issues that take person-days or weeks of effort across multiple expertise domains. That’s also why support subscriptions are priced as a % of total spend, because the more complex the environment the more the requests about product/service X turn into debugging a problem across product/service X, Y, Z, and the customer’s app that requires multiple engineers to be engaged.   Services pricing reflects the overall cost structure of delivering services, not the cost of your (potentially really simple) request.

Vendors really hate the idea of unbundling support because it can create tremendous customer dissatisfaction.  You take your dog in to have its teeth cleaned for a simple published price.  Then they tell you it is highly recommended that for a dog of its age they do bloodwork and an EKG before administering anesthesia.  You choke on the price, but you’d hate for your dog to die just because its teeth needed cleaning, so you say ok.  Then they find something in the bloodwork that indicates there could be a problem with the liver.  You are already paying for the anesthesia, so do you want them to x-ray the liver as well.  There in the x-ray is a growth, should they biopsy it?  Etc.   Your $100 teeth cleaning is turning into a multi-thousand $ bill.   The veterinarian you love has just given you the choice of your kids hating you because you didn’t try to save their dog, or being unable to afford their college education.  You can’t blame the veterinarian for the cancer, but you love them less because of the process they put you through.  So it is really hard for a vendor to say something like we will sell you support for your database server, even if you don’t want support for everything else, because they don’t want to come back to you in the heat of a situation and say the problem spills over to the application server and you don’t have support for that.  It will cost you $X for us to continue the effort over there.  Yeah, right.

Low cost vs. reality of support vs. customer satisfaction is a conundrum.

So is there a per-incident model that would work for customers and fit in what I called the “reality of support”?  One rational per-incident offering to explore would look something like current monthly business support pricing with a cap. So it would be greater of $100 or 10% of total spend up to a maximum of some amount. Using Microsoft’s per incident price as a proxy for not having AWS Support cost data to work from, let’s say that cap is $500/incident. Is that the kind of per-incident support that would be attractive to AWS customers?  How about customers of other cloud providers?

Advertisements
Posted in Amazon, Cloud, Computer and Internet, Microsoft | Tagged , | 2 Comments

A newfangled buggy whip is still a buggy whip

One of the downsides of falling in love with a technology is that you miss it, really really miss it, at times when it isn’t available to you. Take your smartphone. I wonder how many people have popped a Xanax after being in a no Cell or WiFi signal area for an extended period. Well I’m starting to have that problem with Amazon Alexa. I don’t like being somewhere I can’t say “Alexa, time” or “Alexa, turn on the outside lights”, or “Alexa, ask CNBC the price of Amazon stock” rather than drop the Ming vase to get the phone out of my pocket. As Paul Marcarelli used to say, can you hear me now? So when Garmin launched the Garmin Speak with Amazon Alexa a couple of weeks ago I didn’t wait for reviews, and I didn’t think about it for even a second, I just went to smile.amazon.com and ordered one.

Ok I lied. I read the announcement of the Garmin Speak and thought, “hey I’m going on a trip and wouldn’t it be neat to take Alexa along?” Oh, and “it might be nice to have a dedicated navigation device in the rental car”. Then I shut off my brain and ordered. I forgot how many times my old standalone GPS devices had taken me on a bad (even dead end) route. I didn’t think about how much better navigation has been since I switched to Waze a few years ago. Or how helpful little touches, like Apple Maps picking up the destination address of the restaurant from the Yelp app, can be. Or, “you realize you are going to spend $149.99 for a subset of the $49.99 Echo Dot’s capabilities?” I just ordered.

Let me get the easy part out of the way, I loved having Alexa along for the ride. I can’t wait for it to appear as a native capability in car infotainment systems. Or for Amazon to find a way to expose it through the infotainment systems via Apple CarPlay and Android Auto. Or for a true Echo Dot Auto device to be introduced by Amazon, or one of its partners. I don’t even regret that I had to pay 3x what it costs to put an Echo Dot in my house to have one in the car. And as long as you are think about the Garmin Speak as no more than an expensive Echo Dot you’ll probably be happy. One caveat, do keep in mind that not all Alexa functionality is available yet on the Garmin Speak. Indeed all the third-party devices are missing true 100% Echo compatibility, so if you are expecting specific functionality (e.g., Alexa Voice Calling and Messaging) on the device then you’ll need to do some research before buying.

Now for the hard part, I found myself as disappointed with the navigation capabilities of the Garmin Speak as with all the earlier Garmin’s I’ve owned. It was kind of magical to say “Alexa, ask Garmin to take me to the u-haul moving center in Smithtown” and have it start giving voice instructions and displaying the next turn on its small but easy to read display. When it decided to route me on a small tertiary road through a neighborhood I had a bit of deja vu. Back in the 90s I would sometimes take Route 522 over the top of Lake Washington on my way from Woodinville to Seattle. As you would approach the entrance to I5, my original Garmin would have you turn into a neighborhood apparently calculating there was a shortcut. It would then route you in a circle through the neighborhood and back on to 522. I almost crashed the car my wife and I were laughing so hard. But you only laugh the first time. Twenty years later the Garmin Speak didn’t take me in a circle, but when it got to the intersection of the tertiary road and the Main Street my destination was on it told me I’d arrived. I looked around and couldn’t see the U-Haul dealer. Following the street numbers myself I located it a half mile north of where the Garmin Speak had taken me. First time use, big fail.

I wish I could say that my initial failure navigating with the Garmin Speak was an isolated case, but it wasn’t. Although I turned off the option to avoid u-turns, the Garmin Speak still insisted on taking me on a wild goose chase to get to the house I was staying in rather than do a simple u-turn that took me right to the neighborhood entrance. Waze doesn’t have this issue. Up until a year or two ago that intersection didn’t allow u-turns, so this suggests to me Garmin isn’t processing map updates very quickly. It is almost as though Garmin still works on the old annual cycle for shipping map updates, while Waze and other cloud-born solutions pick up even entirely new neighborhoods within weeks or months. More broadly, over a week of use the Garmin Speak did ok but was an inferior experience to Waze, Google Maps, or Apple Maps.

One other issue I had with the Garmin Speak was its mount. Don’t get me wrong, the magnetic mount works great and sticks to the windshield all too well. The problem with the mounting system is that it isn’t suitable for rental car use. Garmin’s design center, and they say this in their documentation, is for permanent installations. The magnetic disk glues solidly to your windshield and is very hard to remove. The wiring is intended to be routed under your car’s headliner, so the USB cable goes upward rather than down with an awkward bend if you want a straight connection to the power outlet. When you use it in a rental, where a suction cup mount would be more appropriate, you’ll be disposing of one of the two magnetic disks Garmin gives you. And I haven’t found where they sell replacements. You also may be buying tools for removing the disk from the rental car. Note that if you are not going to use the Garmin Speak for navigation, you can forget the mount entirely and just throw it in a cup holder for Alexa access. That’s how I’ll be using mine in the future.

Garmin fans may think I’m nuts and have all kinds of counter-examples of Garmin doing a better job of navigation than Waze et al. I believe those users would have been better served by integrating Alexa into a traditional Garmin GPS form-factor than the Speak’s attempt to hew to the Amazon Echo design language. For example, the Garmin Speak’s display very clearly shows you the next turn and distance to it, but it doesn’t show you the name of the street that you’ll be turning on. Or a map or turn list for those who like to think ahead. Those are just too much for a watch face sized display being viewed from a couple of feet away.

Overall the Garmin Speak is a new fangled buggy whip. I’ll leave the rest of the analogy to the reader.

Posted in Computer and Internet, Mobile | Tagged , , ,

Amazon Key: Bad idea or evolutionary pressure tactic?

Like most people, or at least much of the Twitterverse, I am a bit freaked out by the idea of having a stranger open my front door to put a package inside. If you want to get freaked out a little more than the idea of a stranger unlocking your front door while no one is home, imagine it happening while you or a family member are home. When I hear someone fiddling with my front door I very quickly go to DEFCON 1. My brother once showed up when I wasn’t expecting him, and by the time I got to the door he had assumed I wasn’t home and was fiddling with opening the door with his key. I arrived at the door to hear someone apparently trying to break in, and was fully prepared to open a can of whoopass. I wonder how many couriers making deliveries for Amazon are going to end up at the wrong end of a can of whoopass, or how many criminals will take advantage of us getting used to strangers opening our front door and figure out how to subvert it deliver some whoopass of their own? Sorry, it’s the New Yorker in me.

Of course, what Amazon Key promises to allow is for someone known to Amazon to unlock your door and place a package inside with the entire event being caught on video. And I believe, or can invoke WSOD, that Amazon has the technology to make this safe. Or sort of safe. Video helps in bringing a criminal to justice, it doesn’t stop a crime in progress. And while, like an alarm system, it may cause a criminal to focus on softer targets (like your neighbor who has no security systems) it also enables the criminal equivalent of a spear phishing attack. It actually becomes a tool they could subvert in a complex burglary scheme. If you think all criminals are dumb, listen to a crime prevention officer describe how burglars figured out a gap in a high-end security system so they could break into a house and steal an expensive piece of art.

Lest you think I am completely down on Amazon Key let me dissuade you. There are circumstances where it makes sense. For example, we have a house in the city. The neighborhood is very safe, except there is a fair amount of low-level property crime. Packages are regularly taken from porches, if you leave your car unlocked the items inside will be given new homes, and occasionally if you leave a door unlocked or a ground floor window open someone may enjoy your hospitality. If we need a package delivered we use an Amazon Locker a few blocks away. Sometimes that isn’t an option, or the most convenient option, and I would love to use Amazon Key. But they aren’t getting in my house. There is a detached garage, and I would happily install Amazon Key on it and let them leave packages inside. It is a different risk/reward calculation.

I wonder how big the Amazon Key opportunity is, particularly for the next decade. How many people have a secure area that doesn’t expose their entire house, like my detached garage? Or if they are willing to consider allowing someone to access their home directly, have to turn off their alarm system or at least bypass some of their sensors? In the long run Amazon Key could disable certain sensors just for the duration of the delivery (and you may be able to do it now if all the pieces, including IFTTT, come together), but I bet we are at sub-1% penetration of that capability. And what about family pets? At a minimum you need to make sure your escape artist doesn’t take advantage of the front door being opened. And a lot of the most loving and gentle dogs draw the line at a perceived home invasion. Talk about opening a can of whoopass!

I’ve been going back and forth, and mostly negative, on Amazon Key for fun. It is a disruptive idea, though not particularly far fetched. A recent projection is that online sales will exceed brick and mortar sales for the first time this holiday season. In a world in which most of our goods are delivered to us we can, and should, expect that our homes will change to accommodate that lifestyle. My city house also has a mud room. The mud room has both an outside door and a door into the house. We don’t ever close the inner door, and it has no lock on it. But we could install a lock and alarm the inner door as well, and allow delivery access into the mud room while keeping the house (and pets) secure. A lot of houses built in the last 30 years have mud rooms, and they could (some easily, some with significant work) evolve to be package delivery rooms. The same could be said for the entrance rooms/halls of houses and apartments. When we renovated a Seattle-area condo we could easily have turned the entrance hallway into an area that was securable in a way that allowed for direct package delivery without giving easy access to the rest of the unit. Homes used to be built with doors that allowed the milkman to deliver dairy products directly into a box inside the house and slots for the postman to securely deliver the mail. A decade (or two) from now we are all going to have a way to securely receive a large variety of packages at home. In that context, Amazon Key is just one of the forcing functions that will cause homes to evolve.

Posted in Amazon, Retail | Tagged , | 4 Comments

Amazon HQ2 – The Uber Test

Let me start off by saying I have no non-public information about Amazon’s search for a second headquarters, aka HQ2.  And I have no idea how Amazon’s senior leaders will ‘score’ proposals and make a decision.  But I have a couple of observations I’d like to make based on how Amazonians think.

Yesterday’s big news on the HQ2 front was how Newark was offering $7B in incentives if Amazon chose it for HQ2.  The $7B was composed of $5B over 10 years from the State of New Jersey and $2B over 20 years from the city.  Nice.  But cities that think Amazon will make its decision based on short term, and 10 years is short term, incentives are sadly mistaken.  Incentives are going to be a tie-breaker, not the primary driver of a decision.  Amazon thinks long-term, so senior leadership is going to be thinking about picking a location that they believe will be the right one for 2030, 2040, and 2050.  Incentives that mostly run out in the 2020s won’t mean much if it means having 50,000 people in the wrong place in 2035.  So they will narrow things down based on other criteria, get to a few finalists, then start weighing the value of the incentives.  At least IMHO.  I’ll get back to Newark later.

On Facebook a friend, who grew up in Memphis, suggested that city for Amazon HQ2.  This was in response to the New York Times’ analysis saying HQ2 would go to Denver.  Memphis isn’t an obvious choice, and I don’t know how it lines up with the official criteria.  So how can one quickly weigh if Memphis, or any other location, would be a good choice for Amazon?  Amazon is a company where it is always Day 1.  Amongst other things that means it tends to pursue disruptive ideas, such as using drones for deliveries.  Amazon would want HQ2 to be in a location that is supportive of a Day 1 company, if not outright still in Day 1 itself.  What I needed was a simple test for Day 1 type disruptions, and the last decade presented us with a perfect one.  Ride Sharing, and more specifically Uber.  Another interesting test would be AirBnB, but I haven’t pursued that one.

Uber has been disruptive in applying technology to an urban transportation system (taxis)  that hasn’t changed significantly in almost a century, and has deeply entrenched interests.  Moreover, that system had become highly regulated with substantial public bureaucracies and government revenue streams linked to them.  So wherever Uber (or Lyft or…) went it was going against “the system” and friction was to be expected.  What you could measure, very quickly thanks to Google and Bing, was just how much friction (or support) Uber ran into with local government.

So I did a search on Memphis and Uber and discovered that in 2013 the city of Memphis has sent its police force to arrest Uber drivers.  That seemed like a pretty extreme case of being unfriendly to Day 1 type disruptions, and played that back to my friend.  He pointed out that was 2013, so I did a search on Denver and Uber and discovered that in 2013 the Colorado Legislature became the first in the country to explicitly legalize ride-sharing.  What Colorado Governor John Hickenlooper said at the time was “Colorado is once again in the vanguard in promoting innovation and competition while protecting consumers and public safety.”  And when there was some friction in the city of Denver after that, the Police Chief acted quickly to resolve it.  Which makes more sense to locate the HQ of a Day 1 company in, a place that sent the police to arrest Uber drivers or one that acted quickly to accept and encourage the disruption?

So let’s get back to Newark.  There are many reasons I could think of for picking Newark as HQ2.  In particular the close proximity to New York City and all its benefits, with much better housing costs.  Making the reverse commute from Manhattan to nearby New Jersey cities has even become reasonably common in the last 20 years.  The incentives being offered are nice, but again they are a short-term benefit in a long-term play.  So I applied the Uber test to Newark, and it failed miserably.  Newark was still trying to force Uber into their Taxi regulatory scheme as recently as 2016, banning them from Newark Airport and train station in February and planning to enact further regulation in April.  Uber was planning to abandon the city when a last minute deal was reached.  Compare what Newark Mayor Ras Baraka said about Uber, “Just because they have a great idea, doesn’t mean they have an exemption from rules and regulations that have been in existence for decades” with the earlier quote from Colorado Governor Hickenlooper.  I was particularly caught by the “rules and regulations that have been in existence for decades” part.  That doesn’t read like a Day 1 supportive location to me.  It is quite possible that those words will come back to haunt Mayor Baraka when Amazon is evaluating the HQ2 proposals.

The Uber test isn’t perfect for a couple of reasons.  One is that pretty much no locality that regulates Taxis and Limousines won’t try to put some regulatory regime around ride sharing.  The other is that Uber itself has valued confrontation with local governments and agencies over reaching an accommodation, and that in some cases has raised the heat significantly.  For example, I know of airports where Lyft was able to pick up months before Uber, because they negotiated a deal while Uber was still trying to fight the local airport authority.  But in most cases Uber fights the regulatory fight, and gets painted as the bad guy, then Lyft and other competitors benefit.  So the Uber test isn’t black and white, it is varying shades of grey.  But compare the light grey of Denver to the very dark grey of Newark and it, at the very least, gives an indication of which city would be more accommodating to a company where it is always Day 1.

 

 

 

Posted in Amazon | Tagged , , , | 7 Comments

Sonos and Alexa, now for Niles…

It seems like I’m on a continuous journey of how to play music at home.  It all started when we built our ranch back in 2003-2004 and I had the bright idea of doing a whole-house A/V system.  Our timing couldn’t have been worse.  Components were not network aware.  IR, Coax, and RS-232 were the technologies of the day.  There were no smartphones or wireless controllers, let alone something like an Amazon Echo, to control the system.  It was so primitive!  And expensive.  Better options started to appear almost before we moved in, but it was too late.

Over the years I’ve ripped most of the old system and wiring out.  Gone are the Escient Fireball music server, the Sony CD Jukebox, the video distribution system so you could control the Escient remotely (basically IR repeaters would send the commands to the Escient, but you needed to display its UI on a TV).  What remains is the Niles built-in speakers, wall panels, and a Niles ZR-4630 Multi-Zone Receiver.  Years ago I hooked a Sonos Bridge (now called the Connect) to the ZR-4630, so we could play all that Sonos goodness throughout the house.  Of course, controlling this is still a bit of a pain.  You have to use an old Niles panel to select the Sonos to play in that zone, then control the Sonos with your smartphone.  And you may have to play with the Niles volume controls as well as those on the Sonos.  So not quite that simple, but better than the previous setup by a mile.

Today I linked my Sonos account with Alexa.  The Alexa app discovered the Bridge and I said “Alexa, play the Bill Joel channel from Pandora on the Media Room” and lo-and-behold…nothing happened.  Well it did happen, but I had to jump up and press the button (still labeled CD for the old Fireball) to route the Sonos to my office.  And then beautiful music was coming through the ceiling speakers.

Like others, I found the announcement of Alexa support for Sonos very confusing.  The focus of the announcement was the new Sonos One, which is basically a Sonos Play:1 enhanced with far-field microphones and Alexa support.  It looks like a really nice device, and if I had a room calling for really music-focused “Echo” I would go for the Sonos One instead.  The confusion was that the announcement made it sound like you needed a Sonos One to use Alexa.  Either that Alexa only could control the Sonos One, or that one Sonos device in the house had to be a Sonos One to control the others.  Fortunately that isn’t true, you can control existing Sonos devices on your network with Alexa today.

Despite our whole-house system we have been using Echos as standalone music devices at the ranch.  My wife tired of the complexity of using the Niles panel (which in the kitchen/family room has some weird legacy dynamics) and the Sonos app.  She liked the simplicity of an Echo and put one in the kitchen.  Now she can just walk in and say “Alexa, play The Beatles” and she has music.  There is also a weird legacy dynamic in the exercise area because we’d run out of zones on the ZR-4630.  So there is a separate legacy amplifier that had two zones itself, and well….  I will spare you the details, but it is very hard to get music into the exercise area.  I finally just put an Echo in there too, and now I can tell Alexa what to play from the Elliptical.  As well as do all the other great things Alexa supports.

If only I could control the ZR-4630 with Alexa!  Ok, that’s not going to happen given it is a 14 year old device.  So I checked the Niles website and can’t find any indication they have an Alexa-compatible replacement.  The only Alexa-compatible multi-zone receiver I know of is the Denon Heos Drive, and it is only 4 zones.  I need at least 6, preferably 7.  Given the rapid adoption of Alexa I probably don’t have to wait too long for additional multi-zone options.  Either that or I finish ripping out the whole house system and go for an entirely wireless (Sonos or Denon, for the moment) system.

Talk about first world problems.

 

Posted in Amazon, Computer and Internet, Home Entertainment | Tagged , , , | 4 Comments

Finally a Brand New WINDOWS PHONE!

Ok, I lied.  There is no Windows Phone, this is about the Apple iPhone X.  It isn’t even about the iPhone X, it is about clairvoyance.  One of the signature features of the iPhone X is Windows Hello.  Oh, sorry, I mean “Face ID”.  And Qi-based wireless charging. I think I still have some Qi wireless charging plates lying around from a 4 year old Lumia 1020 Windows Phone. Ok, so the iPhone X is full of technology pioneered by Microsoft and its ecosystem years earlier.  The only reason to be snarky is because of a long tradition of Apple and its fanboys claiming Apple is innovative and Microsoft is not.  I should be excited that these technologies are now available in the phone ecosystem I use.  Very excited.  So why do I feel let down?

I think about the iPhone X and picture how it will change my life 6, 12, or 24 months from now and draw a blank.  The first 10 years of iPhone marked a profound change in how I live my life.  In how nearly all of us live our lives.  Even those without smartphones have experienced the change.  My mother experienced her first Uber ride a few months ago.  She didn’t have a smartphone, but my cousin did. And she is only marginally aware of how it contributed to the restaurants we’ve chosen, her healthcare, her travel, or dozens of other things we’ve done on her behalf using a smartphone.

The technological advancements in smartphones the last decade are breathtaking, even when we take them completely for granted.  Take a current dilemma for the military, the potential that they will be denied access to GPS signals during a conflict.  For 30+ years militaries, particularly those of the U.S.A., have used GPS at the core of navigation.  It allows them to feed an accurate current position into Inertial Navigation Systems.  But GPS signal access can be denied, or potentially spoofed, and DARPA (the guys who brought you everything from the Internet to Stealth) have a project to provide accurate positioning information in GPS-denied environments.  One element of that program is to triangulate on existing radio signals.  Well, how does “GPS” work in today’s smartphones?

To reduce battery drain smartphones run with their satellite GPS receivers turned off.  However they are always looking for, and connected to, a nearby cell tower with the strongest signal.  So they can see one or more cell towers and they know where they are located.  When an application asks for location, the smartphone very quickly gives it a location that is triangulated from the cell towers it already looking at.  That isn’t as accurate as GPS, but it is good enough for many uses. Then it looks at all the available WiFi signals.  It can access a database of known WiFi hotspot locations and triangulate on those.  Finally, if the app has asked for maximum location accuracy, the phone fires up its GPS receiver and tries (since GPS signals don’t penetrate buildings, or the “canyons” created by skyscrapers, well) a satellite-based location.  It fuses all this information to determine a very accurate location for your phone.  You can actually see this in action in many location-based applications.  You fire up Uber and watch as the pin moves from a location tens or hundreds of feet from where you are standing to almost exactly where you are.  Map apps may also show a blue circle around the location, indicating accuracy.  The circle shrinks as a more accurate location is determined.  Many applications go one step further by having a database of known points of interest, such as hotels, restaurants, popular office buildings, etc.  So when you ask for an Uber and the cell tower triangulation says you are 50 feet from an Italian Restaurant it assumes you are at the Italian Restaurant.  I can request an Uber from inside my condo.  Location services always starts with a location around the corner from my building entrance, but the Uber app is smart enough to know I’m likely requesting a car from the Home address I’ve saved.  As a result, if GPS satellites were to suddenly all stop working, most location-based apps would continue to work much as they do today.

The maturity of location services in smartphones, and of course the apps built on them, has changed our lives.  Does the iPhone X offer anything with similar potential?  I don’t think so.

What about Augmented Reality?  That isn’t something unique to the iPhone X, but indeed has long term potential.  I may not care much about it, except as a curiosity right now, as I’m not a gamer.  But denying ARs potential would be like claiming GPS was only useful for back country hikers a decade ago. Learning that the sleepsofa we bought couldn’t make it into a guest room no matter how the delivery guys twisted and turned it, before we bought it, would be a game changer.

So why would I part with $1000 for an iPhone X.  There are many times I’d like a screen the size of my iPhone 7s Plus in a smaller package.  I’m having trouble convincing myself that is worth $1000 when the 7s Plus is no new.  I would normally wait for the Xs to make a move.  And there is a potential reason not to buy an X, the lack of a fingerprint reader.

The only reason I really care about a fingerprint reader is that Windows Hello, I mean Face ID, seems really inconvienent for Apple Pay.  What’s the sequence?  I do the usual dance trying to find the right spot on the payment terminal for Apple Pay to launch, then I have to hold it up to see my face, then I have to do the dance again to find the right position to register the payment?  I’ve gotten good at the current sequence, where I find the right position while my thumb hovers over the start button then just give it a touch when Apple Pay launches.  Forcing me to use Face ID (or a pin) instead probably means its more convenient to go back to pulling out a credit card.  I could wait and see if the Xs introduces a screen-based finger print reader, which was something Apple reportedly dropped from the X because they were having trouble getting it to work in time for launch,

So I’m not too excited by the iPhone X, and emotionally lean towards waiting for an Xs.  But that isn’t the end of the story, since my interest may grow over time.  While I have often pre-ordered devices, that hasn’t been the case with iPhones. With iPhones I find my excitement builds over time and I tend to buy them a few months after introduction.  So if February comes around and I’m carrying an iPhone X, don’t be too surprised.

Meanwhile, I was talking to a friend about what would really get me excited about mobile phones again and I gave him a one-word answer: clairvoyance.  He thought I was joking. Fortunately we both believe in Clark’s Laws so be prepared for magic, I mean sufficiently advanced science.  Why do I have to use a finger print or Face ID at all when making a payment?  Or to access the phone at all?  Clairvoyance or bust.

Behavior approaching clairvoyance is already something we are familiar with.  Android and iOS already will figure out your home and work addresses based on behavior.  Waze knows I’m going to/from work and home based on time of day and location I start a journey.  That used to only happen with my pre-designated Home and Work.  But lately I’ve noticed that it handles going from my Colorado home to Colorado work location, even though what is programmed in are my Seattle home and work locations.  Figuring things out from information we provide (e.g., a calendar entry with a meeting location in it) is just good programming.  Deriving facts and projecting behaviors seemingly out of thin air?  Clairvoyance.

Of course clairvoyance is a marriage of sensor data, historical behaviors, and cloud-based AI models.  Mobile phones play a very small part, providing a portion (large today, smaller tomorrow) of the sensory input and serving as a human-network communications interface.  So it is entirely possible to deliver clairvoyance without requiring a new mobile phone.  But, like most things, having the right design center yields a superior experience.  A mobile phone with delivery of clairvoyant experiences as the design center?  That I could get excited about.  It ain’t the iPhone X.

 

 

 

Posted in Cloud, Computer and Internet, Linux and Android, Microsoft, Mobile, Windows Phone | 5 Comments

CUJO Firewall: Approach with Caution

In my previous post I did an introduction to whole-home Internet security.  For the last few months I’ve been trying to get one of the early devices in this category, the CUJO working.  I have now tried CUJO in two totally different networking setups, and failed to get it working properly in either. I had total failure in one and a partial failure in another.

What sets CUJO apart from other devices currently hitting the market is that it is a separate security firewall, not a new router or router feature.  That suggests you can upgrade, rather than replace, your existing network.  Given some may have unusual networking needs to address, the CUJO approach would seem to offer the flexibility that some of us need.  It also would seem to address the problem of how to add security to the modem/router/access point that your internet provider supplies.

I have three home network environments that I can use to try out new products.  The first is as simple as it gets, and likely represents the environment of most Americans.  It is a 2-bedroom condo with Comcast Xfinity as the Internet provider.  Since it is small, the Xfinity combination cable modem/router/access point is completely adequate and thus its base networking setup is extremely vanilla.  The second environment has Centurylink as its Internet provider.  It uses a Centurylink-supplied Zyxel modem/router/access point, except I turn off the AP in favor of using a Netgear Orbi for WiFi.  Though not purely an Internet Provider default environment, it doesn’t stray too far either.  The third environment is very complex due to the lack of any landline Internet provider.  As I didn’t try the CUJO there, I’ll leave out the details.  All three environments contain a number of IoT devices, which leads to complexity on the LAN side.  For example, there are definitely too many ZigBee/Zwave/BLE bridges because despite using standardized protocols many vendors requires a bridge of their own.  But again, that is another story.

My first attempt to get the CUJO working was in the condo, which I often use as a test bed because…my wife is infrequently there so she will never know how badly I mess things up!  There, I said it.  So I get my CUJO, watch the videos, read everything I can find, and get ready to set it up.  I discovered that with Xfinity you need a real hack to get CUJO to work.  I’m not above hacks, so I go ahead and follow the instructions to get it working.

Before we get into that let me summarize how I understand CUJO gains access to your network traffic.  You disable the DHCP server (the thing that hands out addresses to each device in your network, like 192.168.0.23) in your router and let CUJO serve up DHCP addresses instead.  Along with the DHCP address CUJO provides the LAN-side address of the Gateway that the device should talk to in order to send data out over the Internet.  CUJO tells every device to use it, rather than the router, as the gateway.  That way every network packet to and from the device goes through the CUJO.  CUJO can then sniff packets for malicious content, block accesses to bad URLs, and monitor for unusual communications patterns that might indicate a device has been compromised.  For those who really care, CUJO also sets itself up in a sort-of double-NAT environment.  It sets itself up as the gateway at 192.168.0.1, with DHCP handling out 192.168.0.x addresses, and changes your router to sit at 10.0.0.1.

The problem with Xfinity-supplied routers is that you can’t turn off their internal DHCP server.  So instead CUJO came up with the hack I linked to above.  I tried the hack on my router and could never get CUJO to work (it would always end up with its LEDs making the frowning face).  CUJO has easy access to support.  I talked to support, tried a few things, then let them connect into my router to try to get it configured.  We never did get it to work, and the technician suggested I try doing a factory reset of the router then install CUJO again.  At this point I’d spent most of a day on the problem, and decided I couldn’t face all the things that could go wrong with a factory reset.  So I managed to undo the CUJO hack and get my home network working properly again.

The CUJO sat in my cabinet for months, until I realized it was there and that Xfinity had since sent me a newer generation modem/router/AP.  By definition, it had been “reset”! Of course they didn’t make it possible to disable the DHCP server, so CUJO’s hack was still necessary.  Having a couple of hours before I needed to leave for the airport, I reset and again installed the CUJO. The results were no better, once set up according to CUJO’s instructions my home network became completely inaccessible. And without a functioning DHCP server, even after removing the CUJO I struggled to regain access to the Xfinity router and return it to its proper configuration. I had to delay my departure for the airport, and nearly missed the flight, to get my home network back working properly before leaving. I could have tried calling CUJO support again, but I’d already spent way too much time on this device and was running up against that deadline.

Instead I’ve concluded that if you have Comcast Xfinity, don’t go anywhere near the CUJO.  I’m not saying you can never get it to work, just that it is not worth the likely aggravation of trying.  Xfinity subverts the basic mechanism that CUJO uses, and the hack means you are caught in the middle.  You could also replace the Xfinity-supplied modem/router/AP with separate non-Comcast components, and add CUJO to that, but it isn’t a normal consumer thing to do.

With CUJO and Xfinity not playing together I decided to try the CUJO on my CenturyLink network. I knew the Zyxel modem/router/ap allowed you to turn off DHCP, so it should work the way that CUJO is designed for. I followed the instructions in the CUJO app, which automatically configured the Zyxel.  Over a few hours all the devices in my house were recognized by CUJO, and were working correctly. All except a couple of WiFi security cameras. I waited 24 hours for their TTLs to expire to be sure they reached out to DHCP for a new address, but that didn’t help.  They just wouldn’t join the network.

I looked at the instructions for my cameras and they mentioned a number of cases where they could lose WiFi connectivity (e.g., switching network gear). I took one of them and went through its process for connecting to a new network. To make along story short, it was unable to get an IP address from DHCP. I did a hardware reset on the camera and tried the reconnect, no luck. I tried unplugging and re-plugging in the Zyxel, CUJO, and Orbi.  Well first my entire network got screwed up.  Nothing could connect to WiFi for the longest time.  My wired Ethernet connected PC picked up completely bogus information that I couldn’t clear with any imaginable combination of IPCONFIG commands, or the network troubleshooter.  It appeared that it had gotten some information from the router’s DHCP and some from the CUJO’s DHCP, which would make sense later.  It took a reboot to regain a useful Internet configuration.  I then tried to connect the WiFi camera again, with the same result.  It couldn’t get a valid IP address.

At this point I’d wasted hours and was no closer to getting CUJO working correctly, so I decided to remove it from my network.  When I went in to turn back on the DHCP server in the Zyxel I was surprised to find it was already on.  I don’t know if the CUJO app had failed to turn it off, or if the Zyxel somehow turned its DHCP server back on.  I thought about just turning it off, and manually verifying the configuration was proper for the CUJO, but realized it would take days to be confident that the change would “stick” and be comfortable the CUJO was working properly.  So instead I changed the Zyxel back to sitting at the gateway address, removed the CUJO, and rebooted the Zyxel and Orbi.  My network came back with all devices working.  I had to finish the setup of the camera that I’d done a factory reset on, but this time it went smoothly.  Now I had failure with CUJO on both Xfinity and Centurylink.

So conclusion number two is that even though CUJO has tried to make setup consumer friendly, it just doesn’t work reliably enough.  I’m even more sure I could have gotten the Centurylink setup to work properly, if I wanted to spend another few hours between setup and testing, than I was with the Comcast Xfinity setup.  But I worry it is all too fragile.  Because of that, I just don’t think I’ll be giving the CUJO another shot.

 

Posted in Computer and Internet, Security