From owner-freebsd-bluetooth@FreeBSD.ORG Thu Oct 18 16:36:01 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 57D5912E for ; Thu, 18 Oct 2012 16:36:01 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 20CBB8FC08 for ; Thu, 18 Oct 2012 16:36:01 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id rp8so9190673pbb.13 for ; Thu, 18 Oct 2012 09:36:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=OAJOoZt7gaVS8inkrK5NYzgKoggrTP29jsDRw4cpPj4=; b=Ud9NEciO+H+bxgmR9yoKl+UCBfABLlP5FQDFc4j3ntYUs1QYFyASil11B3GFSsdSoM FC1w4/WLjoNDEhRenv0m0E6HzO42DeXvjqqSu/cKSfP8+BmFigDLbSil07jeS9T5aDRl edoIWDbHHdzlF2pTeb4LUsNKJS5ijsEwcDyz15XWJz5u9E5z9vw33kHBxYjQFjGjcYAT GuSIfaKMd/flNbh13sWMP63mI+tsBMxKl2w6XfOgMrp79zN5FFDuJi97xDJjP+FuYQsF IOzn7JI+iy9SGHOsrWknfPBPC/07ybO1j0GvF2kpwNZJznaF3MxTdZAQr4sGhthdOjta dJhQ== MIME-Version: 1.0 Received: by 10.68.222.37 with SMTP id qj5mr66874914pbc.132.1350578160635; Thu, 18 Oct 2012 09:36:00 -0700 (PDT) Received: by 10.68.240.38 with HTTP; Thu, 18 Oct 2012 09:36:00 -0700 (PDT) In-Reply-To: <507C7D76.4090303@incore.de> References: <507736A8.4050605@incore.de> <5077490F.7010901@incore.de> <50782E05.5080005@incore.de> <5079E8F7.5050903@incore.de> <507B0C57.7030506@incore.de> <507C7D76.4090303@incore.de> Date: Thu, 18 Oct 2012 09:36:00 -0700 Message-ID: Subject: Re: btpand problem From: Maksim Yevmenkin To: Andreas Longwitz Content-Type: text/plain; charset=ISO-8859-1 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: Thu, 18 Oct 2012 16:36:01 -0000 On Mon, Oct 15, 2012 at 2:17 PM, Andreas Longwitz wrote: > Hi, > >> 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.. > > I agree. > >>> 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? > > Yes and the arp answer comes in. > >>> 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. > > My problem was a phantom ! It seems to be normal behavior in any network > and has nothing to do with btpand or tap interface. This was a little > bit suprising to me but I have checked this on several networks. An > explanation for this was given on freebsd-net some years ago titled > Lost fragment when send to ip that need arp resolve. > > Thanks again for help! just in case Author: emax Date: Thu Oct 18 16:34:00 2012 New Revision: 241699 URL: http://svn.freebsd.org/changeset/base/241699 Log: make sure that socket's send and receive buffers are properly sized Submitted by: Iain Hibbert plunky at rya-online dot net MFC after: 3 weeks Modified: head/usr.sbin/bluetooth/btpand/client.c head/usr.sbin/bluetooth/btpand/server.c thanks max