LAN over rfcomm_pppd failure with 5.3-STABLE

Petr Panteleyev peterp at online.ru
Thu Jan 27 09:37:55 PST 2005


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


More information about the freebsd-bluetooth mailing list