Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

sdpquery(1) [netbsd man page]

SDPQUERY(1)						    BSD General Commands Manual 					       SDPQUERY(1)

sdpquery -- Service Discovery Protocol query utility SYNOPSIS
sdpquery [-NRX] [-d device] -a address command [parameters ...] sdpquery [-NRX] [-c path] -l command [parameters ...] DESCRIPTION
The sdpquery utility attempts to query the specified Service Discovery Protocol (SDP) server. Remote SDP servers are identified by their address. Connection to the local SDP server is made via the control socket. The sdpquery utility retrieves complete Service Records as directed and prints each record's attribute ID/value list to standard output and error messages to standard error. The options are as follows: -a address Connect to the remote device with the specified address. The address can be specified as BD_ADDR or a name. If a name was spec- ified, the sdpquery utility attempts to resolve the name via bt_gethostbyname(3). If no remote address is given, sdpquery attempts to contact a local SDP server via the control socket. -c path Specify path to the control socket. The default path is /var/run/sdp. -d device Connect from the local device with the specified address. The device can be specified by BD_ADDR or device name. See btconfig(8) for a list of devices available. If no device is specified, the sdpquery utility will use the best available. -l Query the local SDP server via the control socket. -N Additionally display numerical values. -R Display service attributes in raw (uninterpreted) format. -X Display service attribute values in hex. The currently supported commands in sdpquery are: Browse [group] Browse for services. The group parameter is the UUID of the group to browse. If omitted, the "Public Browse Group" is used. Record handle [handle...] Retrieve the Service Record with the given handle. Multiple handles can be given. Search uuid [uuid...] Search for records matching the list of UUIDs which can be given in numerical form, or the following aliases are known: A2DP Advanced Audio Distribution Profile BNEP Bluetooth Network Encapsulation Protocol CIP Common ISDN Access Service CTP Cordless Telephony Service DUN Dialup Networking Service FAX Fax Service FTRN File Transfer Service GN Group ad-hoc Network Service HID Human Interface Device Service HF Handsfree Service HSET Headset Service L2CAP Logical Link Control and Adaptation Protocol LAN LAN Access Using PPP Service NAP Network Access Point Service OBEX Object Exchange Protocol OPUSH Object Push Service PANU Personal Area Networking User Service PNP Plug'n'Play Information Service RFCOMM RFCOMM Protocol SDP Service Discovery Protocol SP Serial Port Service SYNC IrMC Sync Client Service Note that in order for a record to match, it must contain all the UUIDs in the ServiceSearchPattern and the maximum number is 12. EXIT STATUS
The sdpquery utility exits 0 on success, and >0 if an error occurs. SEE ALSO
bluetooth(3), sdp(3), btconfig(8), sdpd(8) HISTORY
The sdpquery command first appeared in FreeBSD 5.3 as sdpcontrol. It was ported to NetBSD 4.0 under its present name by Iain Hibbert under the sponsorship of Itronix, Inc. AUTHORS
Maksim Yevmenkin <> Iain Hibbert for Itronix, Inc. BSD
October 6, 2009 BSD

Check Out this Related Man Page

BTPAND(8)						    BSD System Manager's Manual 						 BTPAND(8)

btpand -- Bluetooth PAN daemon SYNOPSIS
btpand [-i ifname] [-m mode] -a addr -d device {-s service | -S service [-p psm]} btpand [-c path] [-i ifname] [-l limit] [-m mode] [-p psm] -d device {-s service | -S service} DESCRIPTION
The btpand daemon handles Bluetooth Personal Area Networking services in the system. It can operate in client mode as a Personal Area Net- working User (PANU) or in server mode as Network Access Point (NAP), Group ad-hoc Network (GN) or PANU host. btpand connects to the system via a tap(4) virtual Ethernet device and forwards Ethernet packets to remote Bluetooth devices using the Bluetooth Network Encapsulation Pro- tocol (BNEP). The PANU client is the device that uses either the NAP or GN service, or can talk directly to a PANU host in a crossover cable fashion. A GN host forwards Ethernet packets to each of the connected PAN users as needed but does not provide access to any additional networks. The NAP service provides some of the features of an Ethernet bridge, with the NAP host forwarding Ethernet packets between each of the con- nected PAN users, and a different network media. Note, the only differences between NAP and GN services as implemented by btpand are in the SDP service record. The bridging of packets by the NAP must be configured separately with brconfig(8). The options are as follows: -a address In client mode, address of remote server. May be given as BDADDR or name, in which case btpand will attempt to resolve the address via the bt_gethostbyname(3) call. -c path In server mode, specify path to the sdpd(8) control socket. The default path is /var/run/sdp. -d device Restrict connections to the local device. May be given as BDADDR or name, in which case btpand will attempt to resolve the address via the bt_devaddr(3) call. btpand will set the tap(4) interface physical address to the BDADDR of the Bluetooth radio. -i ifname btpand uses the tap(4) driver to create a new network interface for use. Use this option to select a specific tap(4) device interface which must already be created. -l limit In server mode, limit the number of simultaneous connections. The default limit is 7 for NAP and GN servers, and 1 for a PANU server. -m mode Set L2CAP connection link mode. Supported modes are: auth require devices to be paired. encrypt auth, plus enable encryption. secure encryption, plus change of link key. -p psm Use an alternative L2CAP Protocol/Service Multiplexer (PSM) for server mode or client mode (when not using Service Discovery). The default PSM for BNEP is 15 (0x000f). -s service Name of service to provide or connect to, the following services are recognised: GN Group ad-hoc Network. NAP Network Access Point. PANU Personal Area Networking User. -S service As per -s except that btpand will not use SDP services for connection setup. When providing networking services, the Bluetooth PAN profile says that the 'Class of Device' property of the bluetooth controller SHALL include Networking capability (set bit 0x020000). See btconfig(8) for details. After btpand has set up the client or server connection and opened the tap(4) interface, it will create a pid file and detach. FILES
/dev/tap /etc/bluetooth/hosts /var/run/sdp /var/run/ EXIT STATUS
The btpand utility exits 0 on success, and >0 if an error occurs. EXAMPLES
ifconfig tap1 create btpand -a host -d ubt0 -s NAP -m encrypt -i tap1 dhclient -q -o -w -nw tap1 Will create an encrypted connection to the NAP on host, and link that to the tap1 interface. btpand -d ubt0 -s GN -m auth Will create a Group Network requiring authentication to join and register the GN service with the local SDP server. SEE ALSO
bluetooth(3), bluetooth(4), bridge(4), tap(4), brconfig(8), btconfig(8), dhclient(8), dhcpd(8), ifconfig(8), sdpd(8) The "Personal Area Networking Profile" and "Bluetooth Network Encapsulation Protocol" specifications are available at AUTHORS
Iain Hibbert BUGS
There is no way to supply alternative values for the SDP record. There is no way to set net type or multicast address filters. btpand does not do any address routing except to directly connected unicast addresses. All other packets are multicast. As btpand uses the BDADDR of the Bluetooth radio as the physical address of the tap, only one instance can be run per radio. btpand can only provide a single service. BSD
August 17, 2008 BSD
Man Page