Date: Fri, 12 Mar 2004 13:14:35 -0800 (PST) From: Maksim Yevmenkin <m_evmenkin@yahoo.com> To: imp@freebsd.org, ru@freebsd.org Cc: freebsd-doc@freebsd.org Subject: [PATCH] Handbook Bluetooth chapter Message-ID: <20040312211435.8266.qmail@web40308.mail.yahoo.com>
next in thread | raw e-mail | index | archive | help
--0-323712099-1079126075=:7013 Content-Type: text/plain; charset=us-ascii Content-Id: Content-Disposition: inline Hello, i'd like to update Bluetooth chapter in the FreeBSD Handbook (see attached patch). basically it is to document that users should use stock sdpd(8) instead of GNU sdpd (port from Linux BlueZ). thanks, max __________________________________ Do you Yahoo!? Yahoo! Search - Find what you’re looking for faster http://search.yahoo.com --0-323712099-1079126075=:7013 Content-Type: text/plain; name="handbook.bluetooth.chapter.diff.txt" Content-Description: handbook.bluetooth.chapter.diff.txt Content-Disposition: inline; filename="handbook.bluetooth.chapter.diff.txt" Index: en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml =================================================================== RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v retrieving revision 1.282 diff -u -r1.282 chapter.sgml --- en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml 12 Mar 2004 19:55:13 -0000 1.282 +++ en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml 12 Mar 2004 21:10:38 -0000 @@ -1428,35 +1428,32 @@ services. This process of looking for any offered services is called <emphasis>browsing</emphasis>.</para> - <para>Currently Bluetooth SDP server and client are implemented in a - third-party package <application>sdp-1.5</application> that can be - downloaded from - <ulink url="http://www.geocities.com/m_evmenkin/">here</ulink>. The - <application>sdptool</application> is a command line SDP client. + <para>The Bluetooth SDP server &man.sdpd.8; and command line client + &man.sdpcontrol.8; are included in the standard &os; installation. The following example shows how to perform a SDP browse query.</para> - <screen>&prompt.root; <userinput>sdptool browse 00:80:37:29:19:a4</userinput> -Browsing 00:80:37:29:19:A4 ... -Service Name: Dial-up Networking + <screen>&prompt.user; <userinput>sdpcontrol -a 00:01:03:fc:6e:ec browse</userinput> +Record Handle: 00000000 +Service Class ID List: + Service Discovery Server (0x1000) Protocol Descriptor List: - "L2CAP" (0x0100) - "RFCOMM" (0x0003) - Channel: 1 + L2CAP (0x0100) + Protocol specific parameter #1: u/int/uuid16 1 + Protocol specific parameter #2: u/int/uuid16 1 -Service Name: Fax -Protocol Descriptor List: - "L2CAP" (0x0100) - "RFCOMM" (0x0003) - Channel: 2 +Record Handle: 0x00000001 +Service Class ID List: + Browse Group Descriptor (0x1001) -Service Name: Voice gateway +Record Handle: 0x00000002 Service Class ID List: - "Headset Audio Gateway" (0x1112) - "Generic Audio" (0x1203) + LAN Access Using PPP (0x1102) Protocol Descriptor List: - "L2CAP" (0x0100) - "RFCOMM" (0x0003) - Channel: 3 + L2CAP (0x0100) + RFCOMM (0x0003) + Protocol specific parameter #1: u/int8/bool 1 +Bluetooth Profile Descriptor List: + LAN Access Using PPP (0x1102) ver. 1.0 </screen> <para>... and so on. Note that each service has a list of attributes @@ -1466,24 +1463,22 @@ it is possible to search for the specific service. The example below shows how to search for the OBEX Object Push (OPUSH) service.</para> - <screen>&prompt.root; <userinput>sdptool search --bdaddr 00:07:e0:00:0b:ca OPUSH</userinput></screen> + <screen>&prompt.user; <userinput>sdpcontrol -a 00:01:03:fc:6e:ec search OPUSH</userinput></screen> <para>Offering services on &os; to Bluetooth clients is done with the - <application>sdpd</application> server.</para> + &man.sdpd.8; server.</para> <screen>&prompt.root; <userinput>sdpd</userinput></screen> - <para>The <application>sdptool</application> is also used to register - a service with the local SDP server. The example below shows how to - register the Network Access with PPP (LAN) service. Note that some - services require attributes (RFCOMM channel for example).</para> - - <screen>&prompt.root; <userinput>sdptool add --channel=7 LAN</userinput></screen> - - <para>The list of services registered with local SDP server can be - obtained by issuing SDP browse query to a <quote>special</quote> - BD_ADDR.</para> + <para>The local server application that wants to provide Bluetooth + service to the remote clients will register service with the local + SDP daemon. The example of such application is &man.rfcomm.pppd.8;. + Once started it will register Bluetooth LAN service with the local + SDP daemon.</para> + + <para>The list of services registered with the local SDP server can be + obtained by issuing SDP browse query via local control channel.</para> - <screen>&prompt.root; <userinput>sdptool browse ff:ff:ff:00:00:00</userinput></screen> + <screen>&prompt.root; <userinput>sdpcontrol -l browse</userinput></screen> </sect2> @@ -1521,7 +1516,7 @@ <para>In &os; both profiles are implemented with &man.ppp.8; and &man.rfcomm.pppd.8; - a wrapper that converts RFCOMM Bluetooth connection into something PPP can operate with. Before any profile - can be used, a new PPP label in <filename>/etc/ppp/ppp.conf</filename> + can be used, a new PPP label in the <filename>/etc/ppp/ppp.conf</filename> must be created. Consult &man.rfcomm.pppd.8; manual page for examples. </para> @@ -1530,20 +1525,18 @@ DUN RFCOMM channel. The actual RFCOMM channel number will be obtained from the remote device via SDP. It is possible to specify RFCOMM channel by hand, and in this case &man.rfcomm.pppd.8; will not perform SDP - query. Use <application>sdptool</application> to find out RFCOMM + query. Use &man.sdpcontrol.8; to find out RFCOMM channel on the remote device.</para> <screen>&prompt.root; <userinput>rfcomm_pppd -a 00:80:37:29:19:a4 -c -C dun -l rfcomm-dialup</userinput></screen> - <para>In order to provide Network Access with PPP (LAN) service - <application>sdpd</application> server must be running. It is also - required to register LAN service with the local SDP server. Note that - LAN service requires RFCOMM channel attribute. A new entry for LAN - clients must be created in <filename>/etc/ppp/ppp.conf</filename> file. - Consult &man.rfcomm.pppd.8; manual page for examples. Finally, RFCOMM - PPP server must be running and listening on the same RFCOMM channel - as registered with the local SDP server. The example below shows how - to start RFCOMM PPP server.</para> + <para>In order to provide Network Access with PPP (LAN) service the + &man.sdpd.8; server must be running. A new entry for LAN clients must + be created in the <filename>/etc/ppp/ppp.conf</filename> file. Consult + &man.rfcomm.pppd.8; manual page for examples. Finally, start RFCOMM PPP + server on valid RFCOMM channel number. The RFCOMM PPP server will + automatically register Bluetooth LAN service with the local SDP daemon. + The example below shows how to start RFCOMM PPP server.</para> <screen>&prompt.root; <userinput>rfcomm_pppd -s -C 7 -l rfcomm-server</userinput></screen> @@ -1559,7 +1552,7 @@ phones and other devices with PIM applications.</para> <para>The OBEX server and client are implemented as a third-party package - <application>obexapp-1.0</application> that can be downloaded from + <application>obexapp-1.1</application> that can be downloaded from <ulink url="http://www.geocities.com/m_evmenkin/">here</ulink>. The package requires the <application>openobex</application> library (included) and the <filename role="package">devel/glib12</filename> @@ -1589,14 +1582,12 @@ Success, response: OK, Success (0x20)</screen> <para>In order to provide OBEX Push service, - <application>sdpd</application> server must be running. It is also - required to register OPUSH service with the local SDP server. Note that - OPUSH service requires RFCOMM channel attribute. A root folder, where - all incoming objects will be stored, must be created. The default path - to the root folder is <filename>/var/spool/obex</filename>. Finally, - OBEX server must be running and listening on the same RFCOMM channel - as registered with the local SDP server. The example below shows how - to start OBEX server.</para> + &man.sdpd.8; server must be running. A root folder, where all incoming + objects will be stored, must be created. The default path to the root + folder is <filename>/var/spool/obex</filename>. Finally, start OBEX + server on valid RFCOMM channel number. The OBEX server will + automatically register required service with the local SDP daemon. + The example below shows how to start OBEX server.</para> <screen>&prompt.root; <userinput>obexapp -s -C 10</userinput></screen> </sect2> --0-323712099-1079126075=:7013--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040312211435.8266.qmail>