Sunday, December 31, 2017

GOPRO Karma drone can't download updates on google wifi

This is an off topic (from vitrualization) post - but hope to save some folks some time who might have the same issue:

TL;DR (at the top - why don't we put the TL;DR at the top?):

KNOWN ISSUE (google wifi + karma does not work) ref: - someone called GOPRO support and commented support knows this does not currently work 

Wasted some time on this (had the GOPRO support # on standby) before
DISCONNECTING the controller from google wifi and using a combination of Sprint wifi hotspot (so slow!) and xfinitywifi (shared,faster - thanks neighbour!) -

Issue #1: Karma controller could not download the required updates
(actually 4 software updates should be checked - all listed in devices menu):
#1 - v1.6 Camera (Hero6 in our case) REQUIRES
#2 - the Karma drone software to be v2.0,
#3 - controller to be v2.0,
#4  - gimble/gyro assembly even has its own software

Issue #2 - once the controller updated,  the software menu item says v2.0 (no updates needed)  - WRONG! -

what about the other  3 components?  To access the other 3 update components the (non-obvious to a new karma setup person) is accessed on the home screen - click on the upper right tiny icon (looks like a down arrow pointing down into a tray) - then and only then did we get all 4 updates done and the blessed green light appeared on the controller :)

Later, we had much fun on our first test flight

PS: looks like Sonos and google wifi also may be problematic:

Friday, January 29, 2016


If you are looking for a centralized IDS logging solution with real time elastic search capabilities and security event classification, trending I'd highly recommend Wazuh based on Elasticsearch, Logstash and Kibana (ELK) stack and its own fork of OSSEC.  Customizable, importable visualizations and loadbalanced scalability make this opensource project robust and valuable.

When following the implementation guide, make sure to use the OSSEC 2.9 fork

Friday, February 6, 2015

Quantifying TPS Savings now that its disabled - how much are you losing?

The most recent ESXi updates will incorporate a change in TPS.  Due to security (KB 2080735) considerations, TPS will be disabled by default.
As a vmadmin, your next question would be how much am I losing with TPS gone ?
Thankfully there is a tool to quantify exactly how much TPS is going on - credit @vmMarkA and @vBrianGraf.
As it turns out, our main clusters are only seeing 2-5% TPS savings (mostly zero pages) so this change will have no real impact.  I can imagine VDI type workloads could be the most impacted by this change - what are the max TPS numbers folks are seeing ?

vExpert 2015

Congratulations to the vExpert class of 2015, new and alumni alike, its an honor to be counted in your company!

Friday, April 18, 2014

Windows 2003 IPSec error blocks all traffic

This happened to one of our windows 2003 VMs this week - it was patched and rebooted and came up with no network traffic being passed.

The team first looked to revert to the previous known good state - the central storage snapshots.
But as it turns out these restored snapshots also came up with no network being passed.

I removed the old VM network adapter (AMD) and replaced it with the newer Intel, updated the vmwaretools, several reboots in between, all to no effect (the adapter was up and "connected") but not passing any traffic - could not ping the default gateway.

Finally found a post leading us to check the System Event logs

And finding a VMware KB article confirming the resolution:

Disable the Windows 2003 IPSec service and reboot - voila, traffic now unblocked!

Hope this saves other folks some time to resolution!