anyremote(1) [debian man page]

anyRemote(1)						      General Commands Manual						      anyRemote(1)

NAME

       anyremote - control PC with Bluetooth/Wi-Fi cell phone .br

SYNOPSIS

       anyremote [-f file] [-s connect string] [-log] [-a]

		 [-fe port] [-http] [-u username] [-name SDP service name] [-password]

       anyremote -h|-v .br

DESCRIPTION

       The overall goal of this project is to provide remote control service on Linux through Bluetooth, Wi-Fi or just TCP/IP connection.

       anyRemote supports wide range of modern cell phones like Nokia, HTC, SonyEricsson, Motorola and others.

       It was developed as thin "communication" layer between Bluetooth (IR, Wi-Fi)-capabled phone and Linux, and in theory could be configured to
       manage almost any software.

       anyRemote is console application, but in addition there are GUI front-ends for Gnome and KDE.

OPTIONS

   -h
       print short help and exit

   -v
       print version number and exit

   -f /path/to/configuration/file
       By default anyremote will try to find and use $HOME/.anyremote.cfg, then ./.anyremote.cfg. It is possible  to  specify  configuration  file
       directly with -f option.

   -s connect string
       where connect string can be one of:

	    bluetooth:_channel_ (Server mode - bluetooth connection)

	    socket:_port_      (Server mode - TCP/IP connection)

	    web:_port_	       (Server mode - Web interface)

	    local:/dev/ircommX	(Server mode - IR connection)

	    rfcomm:XX:XX:XX:XX:XX:XX:CC  (AT  mode  -  bluetooth connection, where XX:XX:XX:XX:XX:XX is bluetooth device address and CC is channel
       number - integer from 1 to 32)

	    /dev/ttyACM#       (AT mode - cable connection)

	    /dev/ircomm#       (AT mode - IR connection)

	    ilirc:_AF_LOCAL socket file_ (use with inputlircd)

	    stdin

   -log
       print verbose logging information to $HOME/.anyRemote/anyremote.log

   -a
       reconnect automatically in case of connection failure, used only in AT-mode

   -fe _port_
       Work as backend for GUI frontend. Use specified port to connect to frontend.

   -name SDP_service_name
       if bluetooth connection is used, allows one to specify SDP service name.

       Default value for SDP service name is "anyRemote"

   -password
       If this option is specified, then anyRemote will ask the client for the password.

       Password phrase should be stored in $HOME/.anyRemote/password file in plain text.

   -u|--user _username_
       if started from root, allows one to set effective user ID to specified user

	     .br

AUTHORS

       Mikhail Fedotov anyremote@mail.ru

       http://anyremote.sf.net	 .br

BUGS

       If you find any bugs, please report to anyremote@mail.ru .br

LICENCE

       This   is  free	software.  You	 may   redistribute   copies   of   it	 under	 the   terms   of   the   GNU	General   Public   License
       http://www.gnu.org/licenses/gpl.html. There is NO WARRANTY, to the extent permitted by law.

								   May 11, 2012 						      anyRemote(1)

RFCOMM_SPPD(1)						    BSD General Commands Manual 					    RFCOMM_SPPD(1)

NAME

     rfcomm_sppd -- RFCOMM Serial Port Profile daemon

SYNOPSIS

     rfcomm_sppd [-bhtS] -a address -c channel

DESCRIPTION

     The rfcomm_sppd utility is a Serial Port Profile daemon.  It can operate in two modes: client and server.

     In client mode, rfcomm_sppd opens RFCOMM connection to the specified address server and channel.  Once connection is established, the
     rfcomm_sppd utility provides access to the server's remote serial port via stdin/stdout or via pts(4) interface if -t option was specified.

     If the -S option is specified, rfcomm_sppd will operate in server mode and act as RFCOMM server, listening on ANY address and advertising a
     virtual serial port via the sdpd(8) daemon.  If -t options was specified, the server side of the virtual serial port is attached to a pseudo-
     terminal.	Otherwise the virtual serial port is attached to the stdin/stdout.  rfcomm_sppd should be run as root in order to communicate with
     sdpd(8) in this case.

     The rfcomm_sppd utility opens both master and slave pseudo terminals.  This is done to ensure that RFCOMM connection stays open until
     rfcomm_sppd is terminated.  The data received from the master pseudo terminal are sent over the RFCOMM connection.  The data received from
     the RFCOMM connection are written into master pseudo terminal.  The application in its turn opens the slave pseudo terminal and operates on
     it just like it would operate over the standard serial port.

     The options are as follows:

     -a address
	     In client mode, this required option specifies the address of the remote RFCOMM server.  If this option is specified in server mode,
	     rfcomm_sppd will only accept connections from the Bluetooth device with address address.  The address can be specified as BD_ADDR or
	     name.  If name was specified then rfcomm_sppd utility will attempt to resolve the name via bt_gethostbyname(3).

     -b      Detach from the controlling terminal, i.e., run in background.

     -c channel
	     In both client and server mode, this option specifies the RFCOMM channel to connect to or listen on.  In server mode, the channel
	     should be a number between 1 and 30.  If not specified, rfcomm_sppd will try to bind to ``wildcard'' RFCOMM channel number.  The
	     actual RFCOMM channel will be obtained via getsockname(2) call and will be used to register Serial Port service with sdpd(8).  In
	     client mode, the channel could either be a number between 1 and 30 or a service name.  Supported service names are: DUN (for DialUp
	     Networking service), FAX (for Fax service), LAN (for LAN Access Using PPP service) and SP (for Serial Port service).  If channel was
	     not specified then rfcomm_sppd utility will try to obtain RFCOMM channel for Serial Port service via Service Discovery Protocol from
	     the server.

     -h      Display usage message and exit.

     -S      Server mode; see DESCRIPTION.

     -t      Use slave pseudo tty.  If not set stdin/stdout will be used.  This option is required if -b option was specified.

FILES

     /dev/pts/[num]  slave pseudo terminals

EXIT STATUS

     The rfcomm_sppd utility exits 0 on success, and >0 if an error occurs.

EXAMPLES

	   rfcomm_sppd -a 00:01:02:03:04:05 -c 1 -t

     Will start the rfcomm_sppd utility and open RFCOMM connection to the server at 00:01:02:03:04:05 and channel 1.  Once the connection has been
     established, a pts(4) can be used to talk to the remote serial port on the server.  rfcomm_sppd prints the name of the pts(4) to use on std-
     out.

SEE ALSO

     bluetooth(3), ng_btsocket(4), pts(4), rfcomm_pppd(8), sdpd(8)

AUTHORS

     Maksim Yevmenkin <m_evmenkin@yahoo.com>

BUGS

     Please report if found.

BSD
								  April 21, 2008							       BSD