I typically use Amazon’s AWS EC2 cloud services which include Route53 for DNS however I have certain clients that prefer RackSpace and therefore require RackSpace Cloud DNS services. One of the primary reasons for not just using an external DNS service such as Amazon’s Route53 DNS service is because when you setup large cloud deployments you typically are going to need internal DNS entries for communication between cloud instances and DNS services such as Route53 will not respond externally to RFC1918 or private IP space for those DNS entries. Anyhow one thing that is well documented or easy to accomplish on Route53 is creating A records with multiple IP’s for round robin DNS which provides a cheap easy to configure load balancing of sorts for different services such as MySQL. I could not find any documentation or mention of round robin DNS setup on RackSpace Cloud DNS so I wanted to explain how I was able to accomplish this.
I recently wrote an article about how to fix btscanner in Backtrack Linux and realized after the article was completed that some people may prefer to launch btscanner via the menu in Backtrack Linux instead of the command terminal by typing btscanner. This article specifically explains how to add btscanner back to the menu in Backtrack Linux under Backtrack > Information Gathering > Wireless Analysis > BlueTooth Analysis > btscanner. The information could however apply to any tools you wanted to manually add to the Backtrack menu by modifying each variable accordingly.
I have been playing around with some of the bluetooth tools within Backtrack recently and btscanner is one of the main tools I have bene using. The btscanner application in Backtrack Linux provides two bluetooth scanning functions it calls inquiry scanning and brute force scanning. Unfortunately the package installed with Backtrack 5 release 3 will crash when attempting to use it for brute force scanning however I was able to create a fix that isn’t too messy to accomplish. Below we describe the btscanner crash in more detail and provide a way to get btscanner bluetooth brute forcing operating properly.
While doing some testing this evening I ran into all sorts of errors when attempting to compile a new version of btscanner on Backtrack Linux 5 R3. Luckily it is super easy to resolve the error complaining about an unrecognized command named -Wimplicit-function-dec. This error will display when attempting to run “make” against an already configured (./configure) btscanner source. Below we output the error in more detail, explain how to resolve the error by editing the make file, and then display the compilation process moving past the error.
While doing some testing this evening on Backtrack Linux 5 R3 I had issues with apt or aptitude complaining about some dependencies for packages I had compiled from source. One of the packages I first ran into issues with was bluez which is installed by default on Backtrack. I wanted to apply a patch to the source code and then reinstall bluez which I was able to accomplish. The issue started after that when apt started complaining that bluez was not installed any longer. Below I describe how I modified the apt dependencies tracker file which fixed my unmet dependencies errors.