Forkbeard
Table
of Contents:
- Forkbeard
- Introduction
- System Requirements
- Using the Tools
- BTScan
- SDPTool
- OPPTool
- RFComm
- License
- The Forkbeard development team
Downloads
btscan.exe
sdptool.exe
rfcomm.exe
opptool.exe
forkbeard_source_0607.zip
Documentation
Back to Project
Summary
Introduction
Forkbeard is Bluetooth command line tools for Windows.
The tools allow the user to discover remote devices, the services and
channels
provided by those devices and transfer files to and from the devices.
The tools consists of four executable files, named BTScan.exe,
SDPTool.exe,
OPPTool.exe and RFCOMM.exe. These should be placed in the working
directory or
in a directory in your path.
It is assumed the user knows how to use the command line.
Back
System
Requirements
Windows XP SP2 or Windows Vista
A Bluetooth chip/dongle that supports the MS Bluetooth stack
Back
Using
the Tools
BTScan
Scans all Bluetooth devices on area and return the needed information.
Syntax:
btscan [--verbose] [--help] [--xml]
Parameters:
--verbose
Print extra details, including class of device.
--help
Print help.
--xml
Print results in XML format.
Back
SDPTool
Returns SDP services advertised by a given device. If no device
specified,
return services advertised by all found devices.
Syntax:
sdptool [dev] [--help] [--xml] [--pin]
Parameters:
dev
Bluetooth address of remote device.
--help
Print help text.
--xml
Print results in XML format.
--pin
<pin>
Authenticate device using this pin.
Back
OPPTool
Sends and retrieves files to or from a remote Bluetooth device.
Syntax :
opptool <dev> --push
[--files <filelist>] [--help] [--pin <num>]
[--channel <chan>] [--ftp] [--sync] [--force]
[--in-dir <dir>]
opptool <dev> --pull
[--files <filelist>] [--help] [--pin <num>]
[--channel <chan>] [--ftp] [--sync] [--force]
[--out-dir <dir>]
opptool <dev>
--pull-std-files [--help] [--pin <num>] [--channel
<chan>]
[--ftp] [--sync] [--force] [--out-dir <dir>]
opptool <dev> --pull-all
[--help] [--pin <num>] [--channel <chan>]
[--ftp]
[--sync] [--force] [--out-dir <dir>]
Options :
dev
Bluetooth address of remote
device
--push
Push files to remote device. If no files specified,
push all files from current folder to remote device.
--pull
Pull files from remote device. If no files specified,
does a standard OPP Business Card pull.
--pull-all
Pull all available files from remote device.
--pull-std-files Pull available
standard files (the telecom directory)
from remote device.
--help
Print help text.
--pin
[value]
Set PIN value used for authentication.
--force
Force connection to the remote device.
--out-dir
[value] Set the local output folder. Used
with pull.
--in-dir
[value] Push given folder to
remote device. Used with push.
--ftp
Use File Transfer Profile.
--sync
Use Synchronisation Service.
--channel
[value] Use given RFCOMM channel in the
connection.
--files
[value] List of files
to pull/push. Syntax:
"localfile1#remotefile1;localfile2#remotefile2"
Back
RFComm
Connects to a given device and sends data either from stdin or from a
specified file. Also can scan all possible channels of a
given device and
display if the channel is open or closed, what protocol it
uses and what
pin was used to connect to the channel.
Syntax :
rfcomm <dev> [[--scan] | [ --channel
<chan>]] [--file <file>] [--help] [--pin
<num>]
Parameters :
dev
Specifies the hw-address of a remote Bluetooth device to
which the user wants to connect.
--scan
Scans all possible 30 channels of a remote device.
--channel
<chan> Specifies the channel of a
remote Bluetooth
device to which the user wants to connect.
--file
<file>
Specifies the file from which the sent data is read.
--help
Displays this help text.
--pin
<num>
Use this PIN to authenticate devices. Otherwise try some
default PINs to authenticate ( no pin, 0000, 1111, 2222,
3333, 4444, 5555, 6666, 7777, 8888, 9999, 1234 ).
Back
License
Copyright (c) 2007, Forkbeard team
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
* Redistributions of source code must retain the above copyright notice
and notice to this lisence information and include this license
information with the source files.
* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
* Neither the name of the Forkbeard team nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Back
The
Forkbeard development team
Antti Määttä
Olli-Pekka Puolitaival
Pekka Saastamoinen
Tuomas Seppälä
Tuomo Untinen
Back