From owner-freebsd-bluetooth@FreeBSD.ORG Thu May 14 08:32:47 2009 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B3CB1065689 for ; Thu, 14 May 2009 08:32:47 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from smtp02.one2one.net (smtp02.one2one.net [149.254.192.174]) by mx1.freebsd.org (Postfix) with ESMTP id E16558FC1A for ; Thu, 14 May 2009 08:32:46 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from [127.0.0.1] (helo=localhost) by localhost.t-mobile.co.uk with esmtp (Exim 4.50) id 1M4WMr-0006Wz-5Z; Thu, 14 May 2009 08:32:41 +0000 Received: from localhost.t-mobile.co.uk ([127.0.0.1]) by localhost (smtpbeckt01 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24593-07; Thu, 14 May 2009 09:32:40 +0100 (BST) Received: from [10.214.182.214] (helo=rya-online.net) by localhost.t-mobile.co.uk with smtp (Exim 4.50) id 1M4WMp-0006Wg-GG; Thu, 14 May 2009 08:32:40 +0000 Received: (nullmailer pid 857 invoked by uid 1000); Thu, 14 May 2009 08:31:52 -0000 Date: Thu, 14 May 2009 09:31:52 +0100 (BST) To: Daniel O'Connor In-Reply-To: <200905141438.17380.doconnor@gsoft.com.au> References: <200905141438.17380.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1242289912.789883.948.nullmailer@galant.ukfsn.org> From: Iain Hibbert X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at example.com X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: plunky@rya-online.net X-SA-Exim-Scanned: No (on localhost.t-mobile.co.uk); SAEximRunCond expanded to false Cc: freebsd-bluetooth@freebsd.org Subject: Re: btpand example X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2009 08:32:47 -0000 On Thu, 14 May 2009, Daniel O'Connor wrote: > Also, I found the MTU by trial and error, 600 works for me, 650 does > not. I am guessing this is a bluetooth thing but I'm not sure.. If it > is would it be possible for btpand to set the MTU? Why did you think to change the MTU and what was the failure? btpand itself doesn't actually care about the interface MTU and I talk to a WinMo 6.0 system fine (from NetBSD) with default ethernet MTU of 1500. On the bluetooth side, the BNEP minimum MTU is 1691 but we won't send anything bigger than as we don't create any extension headers in client mode. Packets will be what came from the tap. regards, iain