From owner-freebsd-wireless@FreeBSD.ORG Tue Dec 11 20:46:54 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D91A669E for ; Tue, 11 Dec 2012 20:46:54 +0000 (UTC) (envelope-from moonlightakkiy@yahoo.ca) Received: from nm29.bullet.mail.bf1.yahoo.com (nm29.bullet.mail.bf1.yahoo.com [98.139.212.188]) by mx1.freebsd.org (Postfix) with ESMTP id 868868FC1C for ; Tue, 11 Dec 2012 20:46:54 +0000 (UTC) Received: from [98.139.212.148] by nm29.bullet.mail.bf1.yahoo.com with NNFMP; 11 Dec 2012 20:46:46 -0000 Received: from [98.139.211.198] by tm5.bullet.mail.bf1.yahoo.com with NNFMP; 11 Dec 2012 20:46:46 -0000 Received: from [127.0.0.1] by smtp207.mail.bf1.yahoo.com with NNFMP; 11 Dec 2012 20:46:46 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1355258806; bh=YtNz4BY7bjgEZ3xUxR0XocKzBiF5DzamsII8uoKG75I=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Received:MIME-Version:Received:Received:Date:Message-ID:Subject:From:To:Cc:Content-Type; b=365i+70DoTSVJ3eulp4GHezy9KAoZSIqb+Vl858Dz7a7l8UyxJNlhQn0VkoCA2xnj92QOUY1ABa3A0C0yevwZa4wUUUfokpfrQPWtVC2DB2iGoTAhY9AbCy6NcO0uINssyh4BgJJVTMaUIwG5zKz3W3nOMGCeUDu9woBBy7nZeE= X-Yahoo-Newman-Id: 870703.87651.bm@smtp207.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: AsZuS6QVM1kaI_mp1KaUiV0CeQSzDqgNmXnxNxlMlaqYepX vK7ANE57ZlQ1IXG8DREmNMIsfepfQoVjf3d9JF9PmP9uyN8nyide_DCgjnjr DWbR6cvIC2kaM0y5xOT7.u9EwPT.MxpCkmPUynbKXmkoBu8gXRTXIdm6Tr86 ZOLOj4EdJeQhKPWouu1dtPKXobcV6w2gjvlz5JAK34LZEgW.MCzWlaEt.ZlD vL5UOUwW97J_o73Zaavhv529LnpbLbEE5vECC_wd109LncrMX1CnoQ4HJB0i bDH_nAcaaf0nrZ20F5Z2fgjIy6o0b3AeNg8J.vrqcaWId8HJBNUSzqTUWXFK Zv6gqYSyXN0ePgTzXXebFwQg7KMY3hs2gwrEX0_ldrol9_u.q.IxIOi8230l oAGUOLG2vJtVSp4O6zL_BpacLXlxpXAwXa..GFpjOWsL0wQEv3SNOz_ZEjVy DV30Nge3r8Kiw.ee.AQ-- X-Yahoo-SMTP: Xr6qjFWswBAEmd20sAvB4Q3keqXvXsIH9TjJ Received: from mail-vb0-f54.google.com (moonlightakkiy@209.85.212.54 with plain) by smtp207.mail.bf1.yahoo.com with SMTP; 11 Dec 2012 12:46:46 -0800 PST Received: by mail-vb0-f54.google.com with SMTP id l1so5357172vba.13 for ; Tue, 11 Dec 2012 12:46:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.220.115.19 with SMTP id g19mr12042289vcq.69.1355258806457; Tue, 11 Dec 2012 12:46:46 -0800 (PST) Received: by 10.58.182.72 with HTTP; Tue, 11 Dec 2012 12:46:46 -0800 (PST) Date: Tue, 11 Dec 2012 13:46:46 -0700 Message-ID: Subject: Re: 11n in adhoc mode From: PseudoCylon To: Adrian Chadd , Johann Hugo Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Dec 2012 20:46:55 -0000 > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 11 Dec 2012 01:19:51 -0800 > From: Adrian Chadd > To: Johann Hugo > Cc: freebsd-wireless@freebsd.org > Subject: Re: 11n in adhoc mode > Message-ID: > > Content-Type: text/plain; charset=ISO-8859-1 > > .. so now I have 11n IBSS working, but the performance is pretty > shocking. I bet there's some timers that are just not programmed > correctly. > I see massive numbers of long retries and CRC errors. Are protection modes set correctly on both ends? This happens when each end uses different prot mode. > * Then some ancillary stuff - mostly processing beacon frames from > peers and handling HT IE changes correctly. Because this is an adhoc mode issue, this may not apply. But, this is what I have been seeing. Yet another ancillary stuff. Currently, protection mode is updated though ieee80211_htprot_update() (finally iv_update_beacon() is called), and it is called only in hostap mode. When occupancy changes, an ap updates beacon and tells driver to updated the prot mode. Even though, other ends receives updated beacon, ieee80211 stack doesn't tell driver to update the mode (other than in ap mode). As the result, those nics run on different prot modes. When operating with mismatched mode, retry and crc error counts skyrocket. I think we need to add ic_update_prot(). AK