Free bluetooth protocol software for linux

GNOME Bluetooth control remoto (AKA GBTcr) It is meant to be a fast and functional remote control for GNOME Desktop working between a Sony Ericssons phone mobile (maybe others) and computer box using Bluetooth comunication protocol.
Main features:
- Realtime control by plugins for:
- Music player. (beep-media-player, xmms)
- Video player. (mplayer, totem, xine)
- Slideshow software. (ooimpress, magic point)
- Image Viewer. (gthumb, gqview)
- Mouse and Keyboard events.
- Nice and HIGgy GNOME gui GTK+ based.
- Notification Area Support (Tray Icon)

GNOME Bluetooth are tools for controlling and communicating with Bluetooth devices.

GNOME Bluetooth includes a GNOME platform library and associated tools for interfacing with and managing Bluetooth devices. Includes OBEX file transfer utilities and a prototype device manager.

GNOME Bluetooth was originally developed by Edd Dumbill, and its primary maintainer is now Bastien Nocera.

The software is free, licensed under the GPL.

The software is still in beta development right now. This means that there are bugs. Be careful!

The HTTP Time Protocl (HTP) system is a set of utilities to set and maintain the system clock from the HTTP/1.1 (RFC 2616) "Date:" header. HTP requires Libconfig.
The purpose of HTP is provide a simple to use system that can be used on any system that is connected to the internet and can access atleast one web page (either directly or through a proxy) to be able to maintain an accurate clock.
HTTP Time Protocol uses basic statistical analysis to arrive at the most accurate time possible given enough servers. The more servers HTP is configured to use the more accurate the clock can be.
Enhancements:
- Cleanup/simplification of the code.
- A more robust implementation of the "-p" (precision) switch.

STUN Protocol Library provides the Simple Traversal of UDP through NATs Library.
STUN Protocol Library, Client and Server implements a simple STUN (Simple Traversal of UDP through NATs) server and client, using the included library.
The STUN protocol is described in the IETF RFC 3489, available from the IETF.
STUN is a lightweight protocol that allows applications to discover the presence and types of Network Address Translators (NATs) and firewalls between them and the public Internet.
It also provides the ability for applications to determine the public IP addresses allocated to them by the NAT.
STUN works with nearly all existing NATs, and does not require any special behavior from them.
As a result, it allows a wide variety of applications to work through existing NAT infrastructure.
The STUN protocol is very simple, being almost identical to echo.
Enhancements:
- Changed to new terminology.

ZRTP Protocol Library is an implementation of Phil Zimmermanns ZRTP protocol, created based on and interoperable with Zfone beta 2.

Using this package, together with GNU ccrtp (1.5.0 or later) provides a zrtp implimentation that can be directly embedded into client and server applications, rather than the overhead penalty of using an external proxy such as zphone. The first application to demonstrate this capability is the 0.8.2 release of the Twinkle softphone client.

Please note, this library is licensed under the GNU GPL, version 2 or later, and has been copyright assigned to the Free Software Foundation.

Very Simple Control Protocol Daemon is a daemon for home automation tasks.
VSCP protocol is a very simple and free protocol for SOHO automation tasks & friends. The protocol is so easy that everyone can grasp the idea behind it in a few minutes.
Therefore its also very easy to construct and use VSCP aware modules and components. Nodes just start up and then serve the control solution reliable and stable for ever and ever and ever.
The protocol is free and is not designed to conquer the world and every Small Office and HOme. Very Simple Control Protocol Daemon is constructed just because its fun to make tiny little things work together.
Enhancements:
- The port was changed from 1681 to the IANA registered 9598. Scripts for Digitemp support and the first version of the ODIN database were added.

Generic Protocol Framework aims to allow users to rapidly prototype different emerging communications protocols. Implementations can be easily "dropped in" and tested independant of a finished product. Testing on both the end product, and the protocol itself can be easily accomplished. The tool aims to provide the developer and end user with a robust solution which can track the size of messages, how rapidly they will be generated, and how many of each type can be seen.
Why the GPF:
There are many similar tools available. The problem with many of these tools is that they are 1) closed source, 2) not easily adaptable to a specific implementation (they use custom languages), 3) expensive. The advantages of the GPF are its open source nature, the ease of which it can be adapted, and the cost: free!
Basic Flow:
Modification of the GPF is fairly simple. Tool-opts.h contains the basic options that will be applied to the packet while it is being built. To transmit a packet, the system calls the tx_message() function, and passes the message ID as well as the option block. This is then passed to the custom function: tx_message_custom() in tx.c. From the message id, the system selects an appropriate tx_* function (to be implemented by the user) and passes an unsigned char **, where the buffer will be written, and the option block. In turn, that function will make heavy use of the add_buf_tu*() functions, which will allow the user to add a tubyte8, tuint16, or tuint32 number to the buffer.
In daemonize mode, the basic options are set, and the system then listens for incomming packets. When a packet arrives, the system calls basic_parse() on the packet. This function then calls basic_parse_custom(), found in parse.c. In turn, this can call any appropriate parsing helpers, including the get_tu*() functions, which allow the user to retrieve a tubyte8, tuint16, or tuint32 from the buffer. CAVEAT: if the first two bytes of the buffer are zerod, it will be treated as an END message. However, recovery is available. In the basic_parse_custom() message, you can set the end_signal_caught variable of the option_block to 0. In this case, it will not stop the daemon from running.
Enhancements:
- Currently, TCP support is somewhat experimental.
- Testing for that portion will be ongoing.
- No clear examples are provided.
- The examples/ directory contains the precursors to a MIP example.