From owner-freebsd-bluetooth@FreeBSD.ORG Tue May 13 17:05:21 2008 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E818B1065672 for ; Tue, 13 May 2008 17:05:21 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by mx1.freebsd.org (Postfix) with ESMTP id 7A1638FC15 for ; Tue, 13 May 2008 17:05:21 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so4650349fgb.35 for ; Tue, 13 May 2008 10:05:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; bh=nyq5rf8MvRkQczbCRXoxNdUfN2yvsIFLeGTbhGo6osU=; b=d95pBsQU8K90+VOUxsCK4o407ox+7/aUIOYheqcii3DMvhCllplgvWOHUNMkJ08p/ji4ttfeumRTwhj+w1i7/NDSOa2t3PwgjdccbLWps8ReVc8fPHlk+j5RkevZ5EBA1yJ9+8Jvv2Km9uT/Qv6hL0KdbOOXr94UcgmhvwnhiIc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=Ej8ThjOg5Qoz1VC7VYBFhf6HgDD/rBFELcnjmcsGwXWBZUjVy3HIZFHPZGQCt4seg9BE143nibg1C3Bv4tBTPSn+S5IdSj69j+5/itVDi4sGbX9g2OdQWiqEerPJnPefWZVRUDitw0oIEcDPkBUCpOjMWpBwbCQ+EN9OhMkgqeo= Received: by 10.86.90.2 with SMTP id n2mr662200fgb.51.1210698320091; Tue, 13 May 2008 10:05:20 -0700 (PDT) Received: by 10.86.66.5 with HTTP; Tue, 13 May 2008 10:05:20 -0700 (PDT) Message-ID: Date: Tue, 13 May 2008 10:05:20 -0700 From: "Maksim Yevmenkin" To: "Helge Oldach" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: freebsd-bluetooth@freebsd.org Subject: Re: rfcomm_sppd -S as generic wrapper 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, 13 May 2008 17:05:22 -0000 [...] > BTW, Luigi's pipe application is interesting, but what about true > two-way communcation? For instance, I would like to have something like > > # rfcomm_sppd -S -c sp -a myPalm -x "coldsync -t serial -s -md" > > ...meaning: Upon receipt of a SP connection request from myPalm we would > fork coldsync to synchronize the Palm (just like USB or serial sync, but > now bluetooth). > > This could even go into /etc/ttys, forking a fresh rfcomm_sppd after the > request terminates. well, i thought about this, but not really sure how to do it cleanly. here is what i mean. with rfcomm_pppd(8) (lan service wrapper) we only need to start one server and register one lan service with local sdpd(8). as soon as client connects to rfcomm_pppd(8) it forks and starts separate ppp(8) instance that handles this particular client. this model works well (imo) here. i'm not sure what rfcomm_sppd(8) wrapper behavior should be. what you seems to be suggesting is that a single rfcomm_sppd(8) instance can only handle single client at a time. this could be a reasonable assumption. > I'm currently doing this in two separate steps, first starting > rfcomm_sppd with some arbitrary pty, then coldsync talking to that pty. > So yes, this definitely works. also your idea about putting rfcomm_sppd(8) entries into /etc/ttys should work as it is, no? did you try to put rfcomm_sppd(8) into /etc/tty entry for the pseudo terminal (slave) part and run coldsync on mater pty? thanks, max