From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 27 17:37:55 2005 Return-Path: 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 1488E16A4CF for ; Thu, 27 Jan 2005 17:37:55 +0000 (GMT) Received: from smtp.rol.ru (smtp.rol.ru [194.67.1.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FBE643D41 for ; Thu, 27 Jan 2005 17:37:54 +0000 (GMT) (envelope-from peterp@online.ru) Received: from ts11-a132.Spb.dial.rol.ru ([212.46.200.132]:44036 "EHLO [212.46.200.132]" smtp-auth: "peterp@online.ru" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: ) by gnome10.net.rol.ru with ESMTPSA id S27576AbVA0Rhu (ORCPT ); Thu, 27 Jan 2005 20:37:50 +0300 Message-ID: <41F9273C.8020401@online.ru> Date: Thu, 27 Jan 2005 20:39:08 +0300 From: Petr Panteleyev User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: ru-ru, ru MIME-Version: 1.0 To: freebsd-bluetooth@freebsd.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Subject: LAN over rfcomm_pppd failure with 5.3-STABLE X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jan 2005 17:37:55 -0000 I'm trying to connect WinXP with 5.3-STABLE via Bluetooth using USB dongles. Specifically, BSD box has dongle that is recognized by the ng_ubt with the following trace: ubt0: SiW SiW, rev 1.10/15.00, addr 2 ubt0: SiW SiW, rev 1.10/15.00, addr 2 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, buffer size=294 I followed Handbook, set up and started rc.bluetooth, hcsecd, sdpd and rfcomm_pppd. My dongle is recognized, pairing from WinXP side goes well. Connection from WinXP to FreeBSD can be always established but when I'm trying to send any data over this connection, it drops very soon with the following diagnostics: Jan 22 21:34:49 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x4, len=124. Queue full Jan 22 21:34:49 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x4, len=13. Queue full Jan 22 21:34:49 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x4, len=124. Queue full Jan 22 21:34:49 elrond last message repeated 3 times Jan 22 21:34:49 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x4, len=13. Queue full Jan 22 21:47:37 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x6, len=124. Queue full Jan 22 21:47:37 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x6, len=13. Queue full Jan 22 21:47:37 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x6, len=124. Queue full Jan 22 21:47:37 elrond last message repeated 2 times Jan 22 21:47:37 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x6, len=13. Queue full Jan 22 21:47:46 elrond kernel: ng_btsocket_rfcomm_session_send: Could not send data to L2CAP socket, error=40 Jan 22 21:47:46 elrond kernel: ng_l2cap_l2ca_receive: ubt0l2cap - unexpected L2CAP data packet. Invalid channel state, cid=75, state=5 I tried to reduce MTU and MRU for ppp down to 512. It helped a bit - connection was alive a bit longer. Then again, connection dropped with the above diagnostics. Just have no idea where to dig further. Regards, Petr