Cloudflare have been pounding the security drum for years and I have always looked for financially viable solutions that help me stay safer than the next guy. After recently listening to the Security Now (https://twit.tv/shows/security-now) and Troy Hunt (https://www.troyhunt.com/my-weekly-updates-are-now-available-as-an-audio-podcast/) podcasts, I was intrigued about what Cloudflare could offer me on the go and there it was, 184.108.40.206 which has been a DNS offering to rival Google’s 220.127.116.11 for a short while now but Cloudflare have rolled it into an app that performs similarly to a VPN (I appreciate this is an over simplification). Using the offering on an iPhone gives me an on demand DNS directory over https or tls (depending on your preferences) which is faster than any other DNS provider. For further reading, see here for full details https://18.104.22.168/
OSSIM has limited or no connectivity: Make sure your network connection is active and try again
In the event that you receive this message “Limited or no connectivity: Make sure your network connection is active and try again.” while trying to link OSSIM to the Open Threat Exchange (OTX) it may be that your DNS entries need adjusting. Simply SSH to the OSSIM environment and in the menu go to System Preferences, then Configure Network and Name Server (DNS) where you can change the entry to your required DNS settings.
Ensure you go back to the main menu and select Apply all Changes, this should then update the configuration file and solve the issue. You may however find that this does not help, in which case, go to Jailbreak System and using the usual Linux navigation edit the file /etc/network/interfaces check your details and if needed, change the DNS entry. Once complete, save and type exit, you will be returned to the main menu.
At this point you might wish to reboot the device.
Unable to open kernel device “.\Global\vmx86”:The system cannot find the file specified. Did you reboot after installing VMware Workstation?
This recently occurred on my system and although the cause is not yet know, the fix was pretty simple.
Open command prompt (Win+R) but ensure it is run as admin, try net start vmx86, it will probably fail but at least you’re not doing unnecessary steps. Now (still in cmd prompt) change directory into the Workstation install location and type vnetlib — uninstall vmx86 and reboot your physical host machine.
Open command prompt again and type vnetlib — install vmx86 then reboot again, this time the issue should be gone and you can run the VM’s as normal.
If you still have no luck then try reinstalling workstation.