Using VirtualBox 4.2.18 r88780 on OSX I encountered this error in a Win8 Guest after upgrading from my host OS from Lion to Mavericks. Further testing revealed that it affects all guests, Windows and Linux. Changing my adapter mode from Bridged to NAT fixed the issue but I could not run in Bridged mode.
Using the uninstall application and removing VirtualBox then reinstalling it fixed the issue.
Monday, October 28, 2013
Tuesday, October 15, 2013
pfSense is an excellent router/gateway/proxy/content filter. It's not so hot at proactively alerting you if there is a problem. Nobody has time to stand over their pfSense Webmin Interface and monitor gateway statuses, but it is important to know if a member is down. An online uptime monitor can solve the problem.
The pfSense is capable of emailing you with notifications of a failed WAN connection, but that presents a chicken and egg problem - how is it supposed to notify you with email if the Internet connection has failed? The solution that I am currently trying is using uptimerobot.com to ping the public IP of each WAN interface and send me an email if it is down and another once the service is reestablished.
Here are my settings if you want to try it:
- Create an account at http://www.uptimerobot.com and set up your notification options.
- Log into your pfSense and create a pass rule for each WAN (or Internet-facing Opt) interface for protocol ICMP, source any, destination "WAN IP Address" / "OPT1-IP-Adress" then apply those changes. See the image that accompanies this post for more details.
- Using an Internet-connected remote host ping each of your public IP's and verify that they are visible to the outside world.
- Add your public IP's to uptimerobot.com using the +Add Monitor dialog
If anybody knows of a better way I'm all ears - this is a feature that has been requested repeatedly but hasn't ever been implemented. The hot setup would be an audible alarm upon link failure as well as internal Growl notifications of gateway up/gateway down.