README.md - rfcommd - RFCOMM daemon to run filters on clients.
 (HTM) git clone git://bitreich.org/rfcommd/ git://enlrupgkhuxnvlhsf6lc3fziv5h2hhfrinws65d7roiv6bfj7d652fid.onion/rfcommd/
 (DIR) Log
 (DIR) Files
 (DIR) Refs
 (DIR) Tags
 (DIR) README
 (DIR) LICENSE
       ---
       README.md (1628B)
       ---
            1 # RFCOMMd, a rfcomm daemon.
            2 
            3 ## RFCOMM
            4 
            5 RFCOMM is a sub standard of bluetooth, allowing serial communication via
            6 some bluetooth channel.
            7 
            8 ## What is this?
            9 
           10 The rfcomm daemon will offer some rfcomm service for any device and based
           11 on the id of the device, users can run different scripts, daemons or
           12 filters for serial link output.
           13 
           14 This can be used in the most simple case to emulate some bluetooth
           15 printer, bluetooth-capable printing clients connect to, where the piped
           16 format is simply outputted to lpr(1). See the spirofilter script for how
           17 this can be done.
           18 
           19 ## Installation
           20 
           21         $ make
           22         $ make PREFIX=/usr install
           23         # Copy over init scripts from etc/* for your needs.
           24         # Copy over sample filters from filters/* for your needs.
           25 
           26 ## Filters
           27 
           28 A filter is a simple script, where the first argument is the rfcomm
           29 device, like /dev/rfcomm0. The script can then do whatever it likes on
           30 this pseudo tty. See the example filters for how to properly configure
           31 the device to your needs using stty.
           32 
           33 Using this logic, you can use whatever daemon allowing serial
           34 communication as a filter script.
           35 
           36 ## Types of Connection
           37 
           38 Depending on how crappy someone implemented bluetooth, I observed
           39 following device behaviours:
           40 
           41 1.) The device will connect, output content and then disconnect.
           42 
           43 2.) The device connects and stays connected.
           44 
           45 Since rfcommd does no child process management, which would be too much
           46 for it, you need to consider this for anything restarting rfcommd. Maybe
           47 in the future a better logic can be implemented.
           48 
           49 ## Bugs / Patches
           50 
           51 Send bugs / patches to:
           52 
           53         Christoph Lohmann <20h@r-36.net>
           54 
           55 ## Have fun!
           56 
           57 Have fun using this!
           58