From owner-freebsd-bluetooth@FreeBSD.ORG Tue Dec 27 01:53:02 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45D4616A41F; Tue, 27 Dec 2005 01:53:02 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from mta11.adelphia.net (mta11.adelphia.net [68.168.78.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DD0343D5A; Tue, 27 Dec 2005 01:53:01 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [192.168.1.254] (really [70.32.199.60]) by mta11.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051227015300.SUQB5278.mta11.adelphia.net@[192.168.1.254]>; Mon, 26 Dec 2005 20:53:00 -0500 Message-ID: <43B09E71.9010400@savvis.net> Date: Mon, 26 Dec 2005 17:52:49 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dima Dorfman References: <20051224121651.GB1001@trit.org> In-Reply-To: <20051224121651.GB1001@trit.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: SPP server 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: Tue, 27 Dec 2005 01:53:02 -0000 Dima, > Does there exist an SPP server program? not yet. > rfcomm_sppd can act as a client, but it doesn't look like it can act > as a server. that is correct. rfcomm_sppd(1) can only act in client mode > The documentation doesn't say what it connects to, but I presume it's > some embedded device that would normally have a serial port. rfcomm_sppd(1) can be used with any bluetooth device that implements serial port (sp) profile. the scenario covered by sp profile deals with legacy applications using bluetooth as a cable replacement, through a virtual serial port abstraction. > I'm interested in using Bluetooth as a terminal connector. Instead of > running serial cables to all servers in a cluster, we can connect to > them over Bluetooth. It can't be used as a real console, but it can > probably be brought up early enough in the boot sequence to be usable > as a rescue mechanism. Is this already possible? If not, is there any > reason it can't work? Unless I'm missing some conceptual problem, it > doesn't seem like it would be very hard to write an rfcomm terminal > server using the SPP. it should be trivial to extend rfcomm_sppd(1) to do what you want. right now rfcomm_sppd(1) uses pty(4) as virtual serial port abstraction. it is assumed that another application will be using /dev/ttypX (slave pty) as serial port. in theory, you could teach rfcomm_sppd(1) to run login(1) or something like that. thanks, max