The translation is temporarily closed for contributions due to maintenance, please come back later.

Translation

(itstool) path: sect2/para
English
<literal>create_connection</literal> accepts <literal>BT_ADDR</literal> as well as host aliases in <filename>/etc/bluetooth/hosts</filename>.
170/1410 · 141
Context English Turkish (tr_TR) State
Once the driver is loaded, plug in the <acronym>USB</acronym> dongle. If the driver load was successful, output similar to the following should appear on the console and in <filename>/var/log/messages</filename>: Once the driver is loaded, plug in the <acronym>USB</acronym> dongle. If the driver load was successful, output similar to the following should appear on the console and in <filename>/var/log/messages</filename>:
ubt0: vendor 0x0a12 product 0x0001, rev 1.10/5.25, addr 2
ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3,
wMaxPacketSize=49, nframes=6, buffer size=294 		ubt0: vendor 0x0a12 product 0x0001, rev 1.10/5.25, addr 2
ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3,
wMaxPacketSize=49, nframes=6, buffer size=294
To start and stop the Bluetooth stack, use its startup script. It is a good idea to stop the stack before unplugging the device. Starting the bluetooth stack might require <citerefentry><refentrytitle>hcsecd</refentrytitle><manvolnum>8</manvolnum></citerefentry> to be started. When starting the stack, the output should be similar to the following: Bluetooth yığınını başlatmak ve durdurmak için başlangıç komut dosyasını kullanın. Cihazı fişten çekmeden önce yığını durdurmak iyi bir fikirdir. Bluetooth yığınını başlatmak, <citerefentry><refentrytitle>hcsecd</refentrytitle><manvolnum>8</manvolnum> </citerefentry> 'nin başlatılmasını gerektirebilir. Yığını başlatırken, çıktı aşağıdakine benzer olmalıdır:
<prompt>#</prompt> <userinput>service bluetooth start ubt0</userinput>
BD_ADDR: 00:02:72:00:d4:1a
Features: 0xff 0xff 0xf 00 00 00 00 00
&lt;3-Slot&gt; &lt;5-Slot&gt; &lt;Encryption&gt; &lt;Slot offset&gt;
&lt;Timing accuracy&gt; &lt;Switch&gt; &lt;Hold mode&gt; &lt;Sniff mode&gt;
&lt;Park mode&gt; &lt;RSSI&gt; &lt;Channel quality&gt; &lt;SCO link&gt;
&lt;HV2 packets&gt; &lt;HV3 packets&gt; &lt;u-law log&gt; &lt;A-law log&gt; &lt;CVSD&gt;
&lt;Paging scheme&gt; &lt;Power control&gt; &lt;Transparent SCO data&gt;
Max. ACL packet size: 192 bytes
Number of ACL packets: 8
Max. SCO packet size: 64 bytes
Number of SCO packets: 8 		<prompt>#</prompt> <userinput>service bluetooth start ubt0</userinput>
BD_ADDR: 00:02:72:00:d4:1a
Features: 0xff 0xff 0xf 00 00 00 00 00
&lt;3-Slot&gt; &lt;5-Slot&gt; &lt;Encryption&gt; &lt;Slot offset&gt;
&lt;Timing accuracy&gt; &lt;Switch&gt; &lt;Hold mode&gt; &lt;Sniff mode&gt;
&lt;Park mode&gt; &lt;RSSI&gt; &lt;Channel quality&gt; &lt;SCO link&gt;
&lt;HV2 packets&gt; &lt;HV3 packets&gt; &lt;u-law log&gt; &lt;A-law log&gt; &lt;CVSD&gt;
&lt;Paging scheme&gt; &lt;Power control&gt; &lt;Transparent SCO data&gt;
Max. ACL packet size: 192 bytes
Number of ACL packets: 8
Max. SCO packet size: 64 bytes
Number of SCO packets: 8
Finding Other Bluetooth Devices Diğer bluetooth cihazlarını bulma
<primary>HCI</primary> <primary>HCI</primary>
The Host Controller Interface (<acronym>HCI</acronym>) provides a uniform method for accessing Bluetooth baseband capabilities. In FreeBSD, a netgraph <acronym>HCI</acronym> node is created for each Bluetooth device. For more details, refer to <citerefentry><refentrytitle>ng_hci</refentrytitle><manvolnum>4</manvolnum></citerefentry>. Ana Bilgisayar Denetleyici Arabirimi (<acronym> HCI </acronym>), Bluetooth temel bant özelliklerine erişmek için tek tip bir yöntem sağlar. FreeBSD'de, her Bluetooth cihazı için bir netgram <acronym> HCI </acronym> düğümü oluşturulur. Daha fazla ayrıntı için bkz. <citerefentry><refentrytitle>ng_hci</refentrytitle><manvolnum>4</manvolnum> </citerefentry>.
One of the most common tasks is discovery of Bluetooth devices within <acronym>RF</acronym> proximity. This operation is called <emphasis>inquiry</emphasis>. Inquiry and other <acronym>HCI</acronym> related operations are done using <citerefentry><refentrytitle>hccontrol</refentrytitle><manvolnum>8</manvolnum></citerefentry>. The example below shows how to find out which Bluetooth devices are in range. The list of devices should be displayed in a few seconds. Note that a remote device will only answer the inquiry if it is set to <emphasis>discoverable</emphasis> mode. One of the most common tasks is discovery of Bluetooth devices within <acronym>RF</acronym> proximity. This operation is called <emphasis>inquiry</emphasis>. Inquiry and other <acronym>HCI</acronym> related operations are done using <citerefentry><refentrytitle>hccontrol</refentrytitle><manvolnum>8</manvolnum></citerefentry>. The example below shows how to find out which Bluetooth devices are in range. The list of devices should be displayed in a few seconds. Note that a remote device will only answer the inquiry if it is set to <emphasis>discoverable</emphasis> mode.
<prompt>%</prompt> <userinput>hccontrol -n ubt0hci inquiry</userinput>
Inquiry result, num_responses=1
Inquiry result #0
BD_ADDR: 00:80:37:29:19:a4
Page Scan Rep. Mode: 0x1
Page Scan Period Mode: 00
Page Scan Mode: 00
Class: 52:02:04
Clock offset: 0x78ef
Inquiry complete. Status: No error [00] 		<prompt>%</prompt> <userinput>hccontrol -n ubt0hci inquiry</userinput>
Inquiry result, num_responses=1
Inquiry result #0
BD_ADDR: 00:80:37:29:19:a4
Page Scan Rep. Mode: 0x1
Page Scan Period Mode: 00
Page Scan Mode: 00
Class: 52:02:04
Clock offset: 0x78ef
Inquiry complete. Status: No error [00]
The <literal>BD_ADDR</literal> is the unique address of a Bluetooth device, similar to the <acronym>MAC</acronym> address of a network card. This address is needed for further communication with a device and it is possible to assign a human readable name to a <literal>BD_ADDR</literal>. Information regarding the known Bluetooth hosts is contained in <filename>/etc/bluetooth/hosts</filename>. The following example shows how to obtain the human readable name that was assigned to the remote device: The <literal>BD_ADDR</literal> is the unique address of a Bluetooth device, similar to the <acronym>MAC</acronym> address of a network card. This address is needed for further communication with a device and it is possible to assign a human readable name to a <literal>BD_ADDR</literal>. Information regarding the known Bluetooth hosts is contained in <filename>/etc/bluetooth/hosts</filename>. The following example shows how to obtain the human readable name that was assigned to the remote device:
<prompt>%</prompt> <userinput>hccontrol -n ubt0hci remote_name_request 00:80:37:29:19:a4</userinput>
BD_ADDR: 00:80:37:29:19:a4
Name: Pav's T39 		<prompt>%</prompt> <userinput>hccontrol -n ubt0hci remote_name_request 00:80:37:29:19:a4</userinput>
BD_ADDR: 00:80:37:29:19:a4
Name: Pav's T39
If an inquiry is performed on a remote Bluetooth device, it will find the computer as <quote>your.host.name (ubt0)</quote>. The name assigned to the local device can be changed at any time. Uzak bir Bluetooth cihazında sorgulama yapılırsa, bilgisayarı <quote> your.host.name (ubt0) </quote> olarak bulur. Yerel aygıta atanan ad her zaman değiştirilebilir.
Remote devices can be assigned aliases in <filename>/etc/bluetooth/hosts</filename>. More information about <filename>/etc/bluetooth/hosts</filename> file might be found in <citerefentry><refentrytitle>bluetooth.hosts</refentrytitle><manvolnum>5</manvolnum></citerefentry>. Uzak cihazlara <filename> / etc / bluetooth / hosts </filename> içinde takma adlar atanabilir. <filename> / etc / bluetooth / hosts </filename> dosyası hakkında daha fazla bilgi <citerefentry><refentrytitle>bluetooth.hosts</refentrytitle><manvolnum>5</manvolnum> </citerefentry> 'de bulunabilir.
The Bluetooth system provides a point-to-point connection between two Bluetooth units, or a point-to-multipoint connection which is shared among several Bluetooth devices. The following example shows how to create a connection to a remote device: Bluetooth sistemi, iki Bluetooth ünitesi arasında bir noktadan noktaya bağlantı veya birkaç Bluetooth cihazı arasında paylaşılan bir noktadan çok noktaya bağlantı sağlar. Aşağıdaki örnekte, uzak bir aygıta nasıl bağlantı oluşturulacağı gösterilmektedir:
<prompt>%</prompt> <userinput>hccontrol -n ubt0hci create_connection <replaceable>BT_ADDR</replaceable></userinput> <prompt>%</prompt> <userinput>hccontrol -n ubt0hci create_connection <replaceable>BT_ADDR</replaceable></userinput>
<literal>create_connection</literal> accepts <literal>BT_ADDR</literal> as well as host aliases in <filename>/etc/bluetooth/hosts</filename>. <literal> create_connection </literal> <literal> BT_ADDR </literal> ve <filename> / etc / bluetooth / hosts </filename> içindeki ana bilgisayar takma adlarını kabul eder.
The following example shows how to obtain the list of active baseband connections for the local device: Aşağıdaki örnekte, yerel aygıt için etkin temel bant bağlantılarının nasıl alınacağı gösterilmektedir:
<prompt>%</prompt> <userinput>hccontrol -n ubt0hci read_connection_list</userinput>
Remote BD_ADDR Handle Type Mode Role Encrypt Pending Queue State
00:80:37:29:19:a4 41 ACL 0 MAST NONE 0 0 OPEN 		<prompt>%</prompt> <userinput>hccontrol -n ubt0hci read_connection_list</userinput>
Remote BD_ADDR Handle Type Mode Role Encrypt Pending Queue State
00:80:37:29:19:a4 41 ACL 0 MAST NONE 0 0 OPEN
A <emphasis>connection handle</emphasis> is useful when termination of the baseband connection is required, though it is normally not required to do this by hand. The stack will automatically terminate inactive baseband connections. Bir <emphasis> bağlantı tutamacı </emphasis>, taban bandı bağlantısının sonlandırılması gerektiğinde yararlıdır, ancak normalde bunu elle yapmak gerekmez. Yığın, etkin olmayan ana bant bağlantılarını otomatik olarak sonlandıracaktır.
<prompt>#</prompt> <userinput>hccontrol -n ubt0hci disconnect 41</userinput>
Connection handle: 41
Reason: Connection terminated by local host [0x16] 		<prompt>#</prompt> <userinput>hccontrol -n ubt0hci disconnect 41</userinput>
Connection handle: 41
Reason: Connection terminated by local host [0x16]
Type <command>hccontrol help</command> for a complete listing of available <acronym>HCI</acronym> commands. Most of the <acronym>HCI</acronym> commands do not require superuser privileges. Kullanılabilir <acronym> HCI </acronym> komutlarının tam listesi için <command> hccontrol help </command> yazın. <acronym> HCI </acronym> komutlarının çoğu süper kullanıcı ayrıcalıkları gerektirmez.
Device Pairing Aygıt eşleme
By default, Bluetooth communication is not authenticated, and any device can talk to any other device. A Bluetooth device, such as a cellular phone, may choose to require authentication to provide a particular service. Bluetooth authentication is normally done with a <emphasis><acronym>PIN</acronym> code</emphasis>, an ASCII string up to 16 characters in length. The user is required to enter the same <acronym>PIN</acronym> code on both devices. Once the user has entered the <acronym>PIN</acronym> code, both devices will generate a <emphasis>link key</emphasis>. After that, the link key can be stored either in the devices or in a persistent storage. Next time, both devices will use the previously generated link key. This procedure is called <emphasis>pairing</emphasis>. Note that if the link key is lost by either device, the pairing must be repeated. Varsayılan olarak, Bluetooth iletişiminin kimliği doğrulanmaz ve herhangi bir cihaz başka bir cihazla konuşabilir. Cep telefonu gibi bir Bluetooth cihazı, belirli bir hizmet sağlamak için kimlik doğrulaması gerektirebilir. Bluetooth kimlik doğrulaması normalde 16 karakter uzunluğunda bir ASCII dizesi olan bir <emphasis> <acronym> PIN </acronym> kodu </emphasis> ile yapılır. Kullanıcının her iki cihaza da aynı <acronym> PIN </acronym> kodunu girmesi gerekir. Kullanıcı <acronym> PIN </acronym> kodunu girdikten sonra, her iki cihaz da bir <emphasis> bağlantı anahtarı </emphasis> oluşturur. Bundan sonra, bağlantı anahtarı cihazlarda veya kalıcı bir depolamada saklanabilir. Bir dahaki sefere, her iki cihaz da önceden oluşturulan bağlantı anahtarını kullanır. Bu işleme <emphasis> eşleştirme </emphasis> adı verilir. Bağlantı anahtarı her iki cihaz tarafından da kaybedilirse eşleştirmenin tekrarlanması gerektiğini unutmayın.
The <citerefentry><refentrytitle>hcsecd</refentrytitle><manvolnum>8</manvolnum></citerefentry> daemon is responsible for handling Bluetooth authentication requests. The default configuration file is <filename>/etc/bluetooth/hcsecd.conf</filename>. An example section for a cellular phone with the <acronym>PIN</acronym> code set to <literal>1234</literal> is shown below: Bluetooth kimlik doğrulama isteklerini işlemekten <citerefentry><refentrytitle>hcsecd</refentrytitle><manvolnum>8</manvolnum> </citerefentry> daemon sorumludur. Varsayılan yapılandırma dosyası <filename> /etc/bluetooth/hcsecd.conf </filename> şeklindedir. <acronym> PIN </acronym> kodunu <literal> 1234 </literal> olarak ayarlanmış bir cep telefonu için örnek bir bölüm aşağıda gösterilmiştir:
device {
bdaddr 00:80:37:29:19:a4;
name "Pav's T39";
key nokey;
pin "1234";
} 		device {
bdaddr 00:80:37:29:19:a4;
name "Pav's T39";
key nokey;
pin "1234";
}
The only limitation on <acronym>PIN</acronym> codes is length. Some devices, such as Bluetooth headsets, may have a fixed <acronym>PIN</acronym> code built in. The <option>-d</option> switch forces <citerefentry><refentrytitle>hcsecd</refentrytitle><manvolnum>8</manvolnum></citerefentry> to stay in the foreground, so it is easy to see what is happening. Set the remote device to receive pairing and initiate the Bluetooth connection to the remote device. The remote device should indicate that pairing was accepted and request the <acronym>PIN</acronym> code. Enter the same <acronym>PIN</acronym> code listed in <filename>hcsecd.conf</filename>. Now the computer and the remote device are paired. Alternatively, pairing can be initiated on the remote device. <acronym> PIN </acronym> kodlarındaki tek sınırlama uzunluktur. Bluetooth kulaklıklar gibi bazı cihazlarda sabit bir <acronym> PIN </acronym> kodu bulunabilir. <option> -d </option> anahtarı <citerefentry><refentrytitle>hcsecd</refentrytitle> <manvolnum> 8 </manvolnum> </citerefentry> ön planda kalmak, böylece neler olduğunu görmek kolaydır. Uzak cihazı eşleştirilecek şekilde ayarlayın ve uzak cihazla Bluetooth bağlantısını başlatın. Uzak cihaz eşleştirmenin kabul edildiğini belirtmeli ve <acronym> PIN </acronym> kodunu istemelidir. <filename> hcsecd.conf </filename> 'de listelenen aynı <acronym> PIN </acronym> kodunu girin. Şimdi bilgisayar ve uzak cihaz eşleştirildi. Alternatif olarak, eşleştirme uzak cihazda başlatılabilir.
The following line can be added to <filename>/etc/rc.conf</filename> to configure <citerefentry><refentrytitle>hcsecd</refentrytitle><manvolnum>8</manvolnum></citerefentry> to start automatically on system start: <citerefentry><refentrytitle>hcsecd</refentrytitle><manvolnum>8</manvolnum> </citerefentry> 'i sistemde otomatik olarak başlayacak şekilde yapılandırmak için <filename> /etc/rc.conf </filename> öğesine aşağıdaki satır eklenebilir. Başlat:
hcsecd_enable="YES" hcsecd_enable="YES"
The following is a sample of the <citerefentry><refentrytitle>hcsecd</refentrytitle><manvolnum>8</manvolnum></citerefentry> daemon output: Aşağıda, <citerefentry><refentrytitle>hcsecd</refentrytitle><manvolnum>8</manvolnum> </citerefentry> arka plan programı çıktısının bir örneği verilmiştir:
hcsecd[16484]: Got Link_Key_Request event from 'ubt0hci', remote bdaddr 0:80:37:29:19:a4
hcsecd[16484]: Found matching entry, remote bdaddr 0:80:37:29:19:a4, name 'Pav's T39', link key doesn't exist
hcsecd[16484]: Sending Link_Key_Negative_Reply to 'ubt0hci' for remote bdaddr 0:80:37:29:19:a4
hcsecd[16484]: Got PIN_Code_Request event from 'ubt0hci', remote bdaddr 0:80:37:29:19:a4
hcsecd[16484]: Found matching entry, remote bdaddr 0:80:37:29:19:a4, name 'Pav's T39', PIN code exists
hcsecd[16484]: Sending PIN_Code_Reply to 'ubt0hci' for remote bdaddr 0:80:37:29:19:a4 		hcsecd[16484]: Got Link_Key_Request event from 'ubt0hci', remote bdaddr 0:80:37:29:19:a4
hcsecd[16484]: Found matching entry, remote bdaddr 0:80:37:29:19:a4, name 'Pav's T39', link key doesn't exist
hcsecd[16484]: Sending Link_Key_Negative_Reply to 'ubt0hci' for remote bdaddr 0:80:37:29:19:a4
hcsecd[16484]: Got PIN_Code_Request event from 'ubt0hci', remote bdaddr 0:80:37:29:19:a4
hcsecd[16484]: Found matching entry, remote bdaddr 0:80:37:29:19:a4, name 'Pav's T39', PIN code exists
hcsecd[16484]: Sending PIN_Code_Reply to 'ubt0hci' for remote bdaddr 0:80:37:29:19:a4
Network Access with <acronym>PPP</acronym> Profiles Ağ erişimi profilleri <acronym>PPP</acronym>

Loading…

User avatar browndie

New translation

FreeBSD Doc (Archived) / books_handbook — Turkish (tr_TR)

<literal>create_connection</literal> accepts <literal>BT_ADDR</literal> as well as host aliases in <filename>/etc/bluetooth/hosts</filename>.
<literal> create_connection </literal> <literal> BT_ADDR </literal> ve <filename> / etc / bluetooth / hosts </filename> içindeki ana bilgisayar takma adlarını kabul eder.
7 months ago
Browse all component changes

Glossary

English Turkish (tr_TR)
aliases diğer isimler FreeBSD Doc (Archived)
as tür FreeBSD Doc (Archived)
filename dosya adı FreeBSD Doc (Archived)
host ana bilgisayar FreeBSD Doc (Archived)

Source information

Source string comment
(itstool) path: sect2/para
Source string location
book.translate.xml:65535
String age
9 months ago
Source string age
a year ago
Translation file
books/tr_TR/handbook.po, string 10879