From owner-freebsd-net@FreeBSD.ORG Wed Oct 10 21:38:10 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 37225589 for ; Wed, 10 Oct 2012 21:38:10 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 0CC128FC18 for ; Wed, 10 Oct 2012 21:38:09 +0000 (UTC) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 502E550840; Wed, 10 Oct 2012 14:38:09 -0700 (PDT) To: Bernhard Schmidt Subject: Re: Oops! (was: Support for Intel 5100 WiFi ?) In-Reply-To: <201210101938.01847.bschmidt@techwires.net> Date: Wed, 10 Oct 2012 14:38:09 -0700 Message-ID: <40913.1349905089@tristatelogic.com> From: "Ronald F. Guilmette" Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Oct 2012 21:38:10 -0000 Thanks Bernhard for all the additional info about the current state of the iwn driver. I still do have a couple more small questions however. First it really does appear to me that even when my iwm0 device is successfully connecting to an AP which has been set to do "N-only", the information that is displayed via "ifconfig -a" is still showing it as if it were communicating using 11g: >re0: flags=8802 metric 0 mtu 1500 > options=389b > ether 00:24:21:65:ad:a0 > nd6 options=29 > media: Ethernet autoselect (10baseT/UTP ) > status: no carrier >iwn0: flags=8843 metric 0 mtu 2290 > ether 00:22:fb:76:6d:18 > nd6 options=29 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng > status: associated >lo0: flags=8049 metric 0 mtu 16384 > options=3 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0xa > inet 127.0.0.1 netmask 0xff000000 > nd6 options=21 >wlan0: flags=8843 metric 0 mtu 1500 > ether 00:22:fb:76:6d:18 > inet 192.168.1.23 netmask 0xffffff00 broadcast 192.168.1.255 > inet6 fe80::222:fbff:fe76:6d18%wlan0 prefixlen 64 scopeid 0xb > nd6 options=29 > media: IEEE 802.11 Wireless Ethernet OFDM/24Mbps mode 11ng > status: associated > ssid ronair2-1 channel 11 (2462 MHz 11g ht/40-) bssid c0:c1:c0:8b:4b:f3 ^^^ > country US authmode WPA2/802.11i privacy ON deftxkey UNDEF > AES-CCM 2:128-bit txpower 15 bmiss 10 scanvalid 450 bgscan > bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 64 protmode CTS > ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi wme > roaming MANUAL Should I file a PR on this small problem/issue? Second, and again based on the output shown via "ifconfig -a", it appears to me that even when it is in `N' mode (and even when my AP is set to "auto" selection of either 40 or 20Mhz channels), the card is never managing to get above 54Mbps, tops (and often considerably less, as you can see above). So what am I doing wrong exactly? I had been trying some different equipment earlier, but in the same locations and at the same distance, and in that case I was routinely getting between 117Mbps and as much as 130Mbps... or anyway, so said dd-wrt. Ultimately, I want to stream HD out to the laptop that has the Intel 5100 in in, and thus, I really would like to get something above 54Mbps. And it seems to me that this _should_ be possible. (In theory, I should be able to get all of the way to 150Mbps, right?) So why can't I get my iwn0 device (Intel 5100) under FreeBSD going anywhere near that fast? Regards, rfg