From owner-freebsd-bluetooth@FreeBSD.ORG Fri Mar 23 22:12:45 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BE25916A401 for ; Fri, 23 Mar 2007 22:12:45 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.249]) by mx1.freebsd.org (Postfix) with ESMTP id 7C7ED13C457 for ; Fri, 23 Mar 2007 22:12:45 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so1416451ana for ; Fri, 23 Mar 2007 15:12:45 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Q6zJ9K37CtA+DFVxKKd6NQoKg8XaI7AUCWQLUCJuJDetoXrQKK7jBlImyNOq9EocCBGSTbQfAC1LlDHV0/w0+52YAgA/P6ZWuZWyJXpZ0jiP9UOGr9EYrtUVOEmJc+1WcRTt3vB38BchCO/xEBKdSpTgEuYC5KQfufLb+Rxx/hc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=stdsvTOWHc2svowjbnpTrwUM5N4fWAGS40hTtNU3jiY84LDrzZimPyGTEX6DrwgqPYjAES81C1/JSY1umBmKj2jUVr0wzK0nTNeF/83oaUPOlO6sC+9uL8YZppZLcNcL/d9tRtTUEgRD6VR71u7TrhzarklUBGiHRKk5K6rj4IQ= Received: by 10.100.167.7 with SMTP id p7mr3035587ane.1174687964764; Fri, 23 Mar 2007 15:12:44 -0700 (PDT) Received: by 10.100.168.6 with HTTP; Fri, 23 Mar 2007 15:12:44 -0700 (PDT) Message-ID: Date: Fri, 23 Mar 2007 15:12:44 -0700 From: "Maksim Yevmenkin" To: ml-vic In-Reply-To: <200703232156.10736.ml-vic@de-martino.it> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4603f621.1a4.33b3.1705538524@webmailh3.aruba.it> <200703232156.10736.ml-vic@de-martino.it> Cc: freebsd-bluetooth@freebsd.org Subject: Re: L2CAP doesn't seem to be up X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2007 22:12:45 -0000 On 3/23/07, ml-vic wrote: > Maksim, > > Sorry for annoying you but actually I'm absolutely new to bluetooth with which > I'm somewhat in deep waters. > > I read everything I found in freebsd docs and pieces of info and email but > must admit not that much in man pages. This because an absolute beginner like > me is frankly disorientated by, e.g., this extracted from "man sdpd" : > .................................................................................................... > The sdpd daemon keeps track of the Bluetooth services registered on the > host and responds to Service Discovery inquiries from the remote Blue- > tooth devices. > In order to use any service remote Bluetooth device need to send Service > Search and Service Attribute or Service Search Attribute request over > Bluetooth L2CAP connection on SDP PSM (0x0001). Etc..... > ................................................................................ > ????? from the handbook 28.4.7 Service Discovery Protocol (SDP) The Service Discovery Protocol (SDP) provides the means for client applications to discover the existence of services provided by server applications as well as the attributes of those services. The attributes of a service include the type or class of service offered and the mechanism or protocol information needed to utilize the service. SDP involves communication between a SDP server and a SDP client. The server maintains a list of service records that describe the characteristics of services associated with the server. Each service record contains information about a single service. A client may retrieve information from a service record maintained by the SDP server by issuing a SDP request. If the client, or an application associated with the client, decides to use a service, it must open a separate connection to the service provider in order to utilize the service. SDP provides a mechanism for discovering services and their attributes, but it does not provide a mechanism for utilizing those services. Normally, a SDP client searches for services based on some desired characteristics of the services. However, there are times when it is desirable to discover which types of services are described by an SDP server's service records without any a priori information about the services. This process of looking for any offered services is called browsing. === specifically in your case, your nokia phone runs one or more bluetooth server applications and provides bluetooth services. your pc is a bluetooth client, who wishes to discover and possibly use one of the provided services. sdpd is only required if you want to run bluetooth services on your pc. this way bluetooth service application (running on your pc) will register itself with sdpd (running on your pc) so remote clients can actually know that your pc is providing bluetooth services. without doing anything at all, you should be able to discover bluetooth services on your nokia phone, by simply % sdpcontrol -a e61 browse or % sdpcontrol -a e16 search thanks, max