In Bluetooth section:

- Reflect availability of hcidump as a port
- Update obexapp usage example to match obexapp-1.4.1

Approved by:	trhodes, josef
This commit is contained in:
Pav Lucistnik 2004-12-12 16:56:46 +00:00
parent 0634652181
commit d2ff0850aa
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=23187

View file

@ -1679,13 +1679,9 @@ Bluetooth Profile Descriptor List:
into the phone's directory.</para>
<screen>&prompt.user; <userinput>obexapp -a 00:80:37:29:19:a4 -C IrMC</userinput>
obex&gt; get
get: remote file&gt; telecom/devinfo.txt
get: local file&gt; devinfo-t39.txt
obex&gt; get telecom/devinfo.txt devinfo-t39.txt
Success, response: OK, Success (0x20)
obex&gt; put
put: local file&gt; new.vcf
put: remote file&gt; new.vcf
obex&gt; put new.vcf
Success, response: OK, Success (0x20)
obex&gt; di
Success, response: OK, Success (0x20)</screen>
@ -1745,9 +1741,9 @@ rfcomm_sppd[94692]: Starting on /dev/ttyp6...</screen>
<sect3>
<title>Something is going wrong, can I see what exactly is happening?</title>
<para>Yes, you can. Use the <application>hcidump-1.5</application>
third-party package that can be downloaded from
<ulink url="http://www.geocities.com/m_evmenkin/"></ulink>.
<para>Yes, you can. Use the third-party package
<application>hcidump</application>, which is available as
<filename role="package">comms/hcidump</filename> port.
The <application>hcidump</application> utility is similar to
&man.tcpdump.1;. It can be used to display the content of the Bluetooth
packets on the terminal and to dump the Bluetooth packets to a