From owner-freebsd-hackers  Sun Feb  2 19:56:43 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 23D5A37B401; Sun,  2 Feb 2003 19:56:42 -0800 (PST)
Received: from scl8owa02.int.exodus.net (scl8out02.exodus.net [66.35.230.242])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 8AE4343E4A; Sun,  2 Feb 2003 19:56:41 -0800 (PST)
	(envelope-from Maksim.Yevmenkin@cw.com)
Received: from SJDCEX01.int.exodus.net ([165.193.27.80]) by scl8owa02.int.exodus.net with Microsoft SMTPSVC(5.0.2195.5329);
	 Sun, 2 Feb 2003 19:56:41 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Subject: RE: PPP in -direct mode does not execute any chat scripts
Date: Sun, 2 Feb 2003 19:56:41 -0800
Message-ID: <45258A4365C6B24A9832BFE224837D552B1286@sjdcex01.int.exodus.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: PPP in -direct mode does not execute any chat scripts
thread-index: AcLLMy49eGVenVwORrybTbZ69Ga4BAAALzYP
From: "Maksim Yevmenkin" <Maksim.Yevmenkin@cw.com>
To: "M. Warner Losh" <imp@bsdimp.com>
Cc: <hackers@FreeBSD.ORG>, <questions@FreeBSD.ORG>
X-OriginalArrivalTime: 03 Feb 2003 03:56:41.0374 (UTC) FILETIME=[427AB3E0:01C2CB38]
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Warner,

> Is there any reason that RFCOMM doesn't give full tty support, like
> the various USB modem drivers do?  That's likely the best way to deal
> with this.  Then ppp or whatever application you want will just work.

Yes, there is. RFCOMM connection can only be established when
baseband link is open. Also RFCOMM connection exists between
pair of device and identified by source address, destination
address and channel. In fact up to 60 RFCOMM channels can exist
on the same baseband link between the same pair of devices.

So, with tty device things look a bit weird. for example if
user wants to dial out then user must do three things:

1) establish binding between source, destination address, channel
   and particular tty device;
2) open RFCOMM channel on the tty device;
3) start PPP on the tty device.

Things gets even more tricky when you want to run server
on specific RFCOMM channel. In this case tty device does not
exist at all until RFCOMM connection is establised. So it is
really hard to do binding between connection and tty device.
May be if we could clone tty devices then if would be easier.

Also Bluetooth spec. has redefined some aspects of GSM 07.10
spec. and all Bluetooth 1.1 devices do not use modem signals
defined in GSM 07.10. Instead there is something called=20
'credit based flow control'.

So you see it is probably possible to build a tty-like interface,
but i do not think it really worth the trouble. In fact one
can do it right now with the help of nmdm(4) driver. It is a
simple wrapper that would pass the data between socket and
/dev/nmdm0{A|B}.

thanks,
max


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message