From owner-freebsd-bluetooth@FreeBSD.ORG  Tue Jan 23 19:05:52 2007
Return-Path: <owner-freebsd-bluetooth@FreeBSD.ORG>
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 1BC2416A40F
	for <freebsd-bluetooth@freebsd.org>;
	Tue, 23 Jan 2007 19:05:52 +0000 (UTC)
	(envelope-from plunky@rya-online.net)
Received: from smarthost01.eng.net (smarthost01.eng.net [213.130.146.173])
	by mx1.freebsd.org (Postfix) with ESMTP id 5A50213C50D
	for <freebsd-bluetooth@freebsd.org>;
	Tue, 23 Jan 2007 19:05:50 +0000 (UTC)
	(envelope-from plunky@rya-online.net)
Received: from netmail01.eng.net ([213.130.128.38] helo=rya-online.net)
	by smarthost01.eng.net with smtp (Exim 4.62)
	(envelope-from <plunky@rya-online.net>)
	id 1H9Qxg-0004An-G5; Tue, 23 Jan 2007 19:05:45 +0000
Received: (nullmailer pid 2412 invoked by uid 1000);
	Tue, 23 Jan 2007 17:59:42 -0000
Date: Tue, 23 Jan 2007 17:59:42 +0000 (GMT)
To: Maksim Yevmenkin <maksim.yevmenkin@savvis.net>
In-Reply-To: <45A7C992.4040805@savvis.net>
References: <20070112082200.GA67105@old.com.ua> <45A7C992.4040805@savvis.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-Id: <1169575182.661050.3030.nullmailer@galant.ukfsn.org>
From: Iain Hibbert <plunky@rya-online.net>
Cc: freebsd-bluetooth@freebsd.org
Subject: rfcomm_sppd
X-BeenThere: freebsd-bluetooth@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Using Bluetooth in FreeBSD environments
	<freebsd-bluetooth.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth>, 
	<mailto:freebsd-bluetooth-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bluetooth>
List-Post: <mailto:freebsd-bluetooth@freebsd.org>
List-Help: <mailto:freebsd-bluetooth-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth>, 
	<mailto:freebsd-bluetooth-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jan 2007 19:05:52 -0000

Hi Max,
       I was working on rfcomm_sppd(1) today (because for NetBSD I didn't
port rfcomm_pppd but somebody was asking after server functionality) and I
think I discovered the solution to a longstanding problem, which is..

..if I use 'rfcomm_sppd -a phone -c dun -t ttyp9', then try to access the
remote service with 'cu -l ttyp9' it never did work properly and I didn't
understand why.

Anyway, I was fiddling around and I saw that you had set the slave tty
into raw mode. If I remove that, then 'cu -l ttyp9' works just fine!

So, I wonder if this is different on FreeBSD?

Do you recall why you chose to put the slave tty into raw mode? I claim no
expertise over pty(4) but I can't really think why rfcomm_sppd should care
about the slave tty settings?

regards,
iain