Date: Fri, 7 Jan 2005 22:37:25 +0100 From: Jes <jjess@freebsd.polarhome.com> To: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> Cc: freebsd-bluetooth@freebsd.org Subject: Re: [spam] Re: Motorola E1000 and obexapp 1.4.4 in server mode Message-ID: <20050107223725.15a4554d@zurich.homeunix.com> In-Reply-To: <41DEE958.70403@savvis.net> References: <20050107163705.616cbe5f@zurich.homeunix.com> <41DECEA3.5080500@savvis.net> <20050107195406.0c76f42e@zurich.homeunix.com> <41DEE958.70403@savvis.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> at this point i'm not sure who is at fault here. after reading the spec > i was not sure if *entire* rfcomm frame must fit into l2cap mtu, or > segmentation is allowed. i need to re-read the spec and look at more > dumps from different bluetooth devices. it seems to me that if l2cap > channel was configured to use 132 bytes mtu then device should not send > larger packets, so my first impression is that the phone has a bug. > > as workaround you might want to try this: > > 1) edit /sys/netgraph/bluetooth/include/ng_btsocket_rfcomm.h file and > change RFCOMM_DEFAULT_MTU from 127 to 667. > > 2) re-compile ng_btsocket module, i.e. > > # cd /sys/modules/netgraph/bluetooth/socket/ > # make depend > # make > # make install > > 3) reboot and try again > No, it doesn't work nor obexapp in client mode with that change. It really doesn't matter because of I can retrieve files from pc in client mode... Thanks in deed Max Jes -- If only God would give me some clear sign! Like making a large deposit in my name at a Swiss bank. -- Woody Allen, "Without Feathers"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050107223725.15a4554d>