From owner-freebsd-bluetooth@FreeBSD.ORG Mon Oct 15 09:25:25 2012 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B7062296 for ; Mon, 15 Oct 2012 09:25:25 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from smtpout.wanadoo.co.uk (smtpout3.wanadoo.co.uk [80.12.242.59]) by mx1.freebsd.org (Postfix) with ESMTP id 2CB8D8FC0C for ; Mon, 15 Oct 2012 09:25:24 +0000 (UTC) Received: from galant.ukfsn.org ([109.249.107.220]) by mwinf5d44 with ME id BMRD1k0034lLfvR03MRD7v; Mon, 15 Oct 2012 11:25:17 +0200 Received: by galant.ukfsn.org (Postfix, from userid 1000) id F27B12600A0; Mon, 15 Oct 2012 10:16:15 +0100 (BST) Date: Mon, 15 Oct 2012 10:16:15 +0100 (BST) From: Iain Hibbert To: Andreas Longwitz Subject: Re: btpand problem In-Reply-To: <507B0C57.7030506@incore.de> Message-ID: References: <507736A8.4050605@incore.de> <5077490F.7010901@incore.de> <50782E05.5080005@incore.de> <5079E8F7.5050903@incore.de> <507B0C57.7030506@incore.de> User-Agent: Alpine 2.00 (NEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-bluetooth@freebsd.org X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Oct 2012 09:25:25 -0000 On Sun, 14 Oct 2012, Andreas Longwitz wrote: > Hi, thanks for the patch. > > > > but, btpand should also ensure that the buffer sizes are suitable. The > > > server_init() function already does this in FreeBSD, though I also added > > > some code to increase the RCVBUF size in NetBSD code, and also added (but > > > didn't yet commit) the similar for client code.. I will prepare a patch > > > > patch for btpand attached > > I tried your patch and it works, I do not need the kernel patch for the > default size of NG_BTSOCKET_L2CAP_SENDSPACE anymore. as I said, I think 672 is a bit low, though I used 4096 for NetBSD (with a sysctl for runtime adjustment if necessary) and that is still potentially prone to error with larger packets (L2CAP MTU between 48-65535 bytes is valid) so I guess that requiring the application to set the buffer size is best practice.. > Now I describe another problem with my ping test, I am not sure if this > problem concerns btpand too. If the ICMP packet must be fragmented, then the > first fragment ist lost on the tap interface (and can not be found by tcpdump > running on this tap) if an ARP request is necessary. > ping -c 1 -s 1400 panserver > works all the time, > ping -c 1 -s 1600 panserver > only works if the ip address of panserver is in the arp cache. does the ARP request get sent out? > I did nothing special with the tap interface, it is included in my > "cloned_interfaces" in rc.conf and opened by btpand. > > Any ideas ? No, I confess.. I am not a networking expert :) btpand does change the address on the tap, so in the first instance the address will be unknown to the rest of the kernel I guess.. should it generate a notification of the address change somehow? iain