Anyone with Bluetooth want to test a program I am working on?
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Anyone with Bluetooth want to test a scanner/logger I am working on?
I have recently gotten a pet project of mine to the level where I think it works well enough that other people can give it a shot, and I'm looking for some help in making sure it works as expected.
Basically, it is a Bluetooth scanner that is designed to do just one thing, scan for discoverable devices in range and record their MAC, name, and the time/date they were found to a log file. There are only a few options, it is pretty much a set it and forget it sort of thing.
The only requirements are BlueZ (3.x or 4.x), and that your computer has a Bluetooth device that is supported by Linux. Obviously you will also need at least one device to scan for, and the more the better. If you want to take a walk through your mall while running it and seeing what you found, I would be ecstatic.
A word of warning, I am not a very good C programmer and I have no doubt that there are mistakes in the code and improvements that could be made. To that end, if you have any suggestions, please let me know.
It seems to work nicely on my rig (Slackware64 13.1). The only thing I had to do was set the march option in the makefile to x86-64 to get it to compile. It picked up my Android phone without a problem.
I have reached a new stable (probably) release of Bluelog, and thought I would bump this up a little bit for those who didn't see it. I have added a lot of options and fixed a lot of things since I posted last, but the main addition has been "Bluelog Live", a web front-end for Bluelog that could be used in a public area to raise awareness of Bluetooth security risks, much like the "Wall of Sheep" seen at DEFCON.
The interface can be skinned with CSS, and I have included two different versions, one based on my website's layout and another for BackTrack (which Bluelog will hopefully be included in someday):
I understand the testing setup is kind of difficult for most people, since you need not only a Linux box with Bluetooth hardware but at least a few devices to scan, but I would appreciate anyone who could give the new version a try and see how it works out on different distributions/setups. Even if you can only scan one device with it, it is enough to show it works.
Well, it is good to know it is building properly on other architectures now. The first versions used a makefile that was basically just for testing, now I am using a proper (well, better) makefile that should work right on all systems and has install/uninstall targets (which I needed for Live anyway).