From owner-freebsd-current@FreeBSD.ORG Tue Jan 25 00:30:51 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64B3916A4CE for ; Tue, 25 Jan 2005 00:30:51 +0000 (GMT) Received: from ank-pki.ru (mercury.ank-pki.ru [213.170.76.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6C7543D31 for ; Tue, 25 Jan 2005 00:30:49 +0000 (GMT) (envelope-from toxa@cterra.ru) Received: (qmail 89252 invoked by uid 0); 25 Jan 2005 03:30:47 +0300 Received: from toxa@cterra.ru by mercury.ank-pki.ru by uid 0 with qmail-scanner-1.22 (spamassassin: 3.0.2. Clear:RC:0(62.89.204.62):SA:0(?/?):. Processed in 10.345258 secs); 25 Jan 2005 00:30:47 -0000 Received: from unknown (HELO localhost) (toxa@62.89.204.62) by mail.ank-pki.ru with SMTP; 25 Jan 2005 03:30:37 +0300 Date: Tue, 25 Jan 2005 03:28:41 +0300 From: Toxa To: FreeBSD-CURRENT X-Comment-To: "Anton Karpov" Message-ID: <20050125002841.GA11564@laptoxa.toxa.lan> Mail-Followup-To: FreeBSD-CURRENT , m_evmenkin@yahoo.com Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline User-Agent: Outluck Express 1.5.6i for MS-DOS 6.22-SMP X-Mailer: See User-Agent above :) X-Operating-System: MS-DOS 6.22-CURRENT on Sony VAIO laptop X-PGP-Public-Key: http://toxahost.org/gpg/pubkey.asc X-Useless-Header: Do Androids Dream of Electric Sheep? X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on mercury.ank-pki.ru X-Spam-Level: X-Spam-Status: No, score=0.0 required=7.0 tests=none autolearn=failed version=3.0.2 cc: m_evmenkin@yahoo.com Subject: troubles with rfcomm_sppd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 00:30:51 -0000 The same problem with rfcomm_sppd onto 6-current (23 Jan kernel&world) and 5-stable (4 Jan kernel) I used to use rfcomm_sppd with my BT-capable mobile phone to get access to internet via gprs. I used to run it like this (and it worked several months ago): rfcomm_sppd -a 00:01:e3:3f:d1:9a -b -t /dev/ttyp4 It was ok but now it is not, as I get such a message: Jan 25 02:38:22 laptoxa rfcomm_sppd: Could not open(/dev/ptyp4). Input/output error When trying to change device to ptyp4 like this: rfcomm_sppd -a 00:01:e3:3f:d1:9a -b -t /dev/ptyp4 I'm getting another message: Jan 25 02:39:09 laptoxa rfcomm_sppd: Master and slave tty are the same (/dev/ptyp4) I confused with "Could not open(/dev/ptyp4)" in the first example due ti the fact I run rfcomm_sppd with "-t /dev/ttyp4" Any ideas? Thanks in advance.