From owner-freebsd-net@FreeBSD.ORG Wed Oct 17 04:21:27 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 1763E2EC for ; Wed, 17 Oct 2012 04:21:27 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9EF018FC08 for ; Wed, 17 Oct 2012 04:21:26 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id x43so5203396wey.13 for ; Tue, 16 Oct 2012 21:21:25 -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=EVk0+JpVZR97dDKwYc1f/u2nwwRLlFzR5orOm0fhA6U=; b=TNr064IOj8i1KDLR2GBc2omcLI0CVueiztYi+RXJv9L6JX+dYEiIKf7msoM6ppDuv3 kDNE6gNnnphyWDldNrgc5wqVE1hWHTm9acqbgTm0LRl72rNoIF0In1fB7NFjhoWVLEeV QI24y6zJdsrmvU/VEU224CsuZNBpoc/Rfm6ztiJMNEg5RdnKAH5acG3UqN5gPO62RA7A wqhbcmBfezYoz5kfL5fagMfE4KUNS8ML8b40P3d7og7Vmh2B8yTcxZpgnbK3QGxib9jL HbogWnHCrU1oMJaO6v7YhY4CUjpgg8pW5zqY4V14Y1lPiPKeyCNORk25dxLmafyWf46b R6Lw== MIME-Version: 1.0 Received: by 10.216.197.104 with SMTP id s82mr10013089wen.62.1350447685564; Tue, 16 Oct 2012 21:21:25 -0700 (PDT) Received: by 10.223.66.194 with HTTP; Tue, 16 Oct 2012 21:21:25 -0700 (PDT) In-Reply-To: <15066.1350443909@tristatelogic.com> References: <15066.1350443909@tristatelogic.com> Date: Tue, 16 Oct 2012 21:21:25 -0700 Message-ID: Subject: Re: Wireless Networking Bug(s) in 9.1-RC2 (?) From: Kevin Oberman To: "Ronald F. Guilmette" Content-Type: text/plain; charset=UTF-8 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, 17 Oct 2012 04:21:27 -0000 On Tue, Oct 16, 2012 at 8:18 PM, Ronald F. Guilmette wrote: > > > Greerings, > > I am currently running 9.1-RC2 on my laptop, and I'm wondering what the > proper procedure is for reporting bugs in not-yet-released releases. > Could somebody please tell me? Should I just file a regular PR? (I've > never done this before for anything that's not an official -RELEASE, > and I don't want to be busting anybody's chops over something that isn't > considered ready-for-prine-time anyway.) I think stable@ is probably the best choice. wireless@ would also be an appropriate place. > So anyway, I'll give the issue to you in a nutshell... This laptop has > both wired ethernet and wireless (11{b,g,n}) capabilities. I have a > Linksys E1000 which I had this thing successfully talking to/with > (using 11n) under 9.0-RELEASE. (The Linksys is set to speak `N-Only'.) > > Now however, it does appear to me that in 9.1-RC2 there may perhaps be > a problem which is causing the iwn0 interface to want to speak to the > Linksys using 11b, of all things. (I would have though that if it was > giving up on `N' it would have fallen back to `G' next.) > > I include below relevant portions of my /etc/rc.conf file and the output > I am now getting from ifconfig -a. > > Guidance would be appreciated. Should I be filing a PR? Is my rc.conf > goofed? > > > Regards, > rfg > > > P.S. Actually, I've never tried running _both_ the wired & wireless stuff > on this laptop in parallel before now. Is that part of the problem? And > anyway, how exactly does the system establish a default route to 192.168.1.1 > when there are two (or more) ways to get there from here? > > > rc.conf: > ============================================================================= > hostname="slim.tristatelogic.com" > ifconfig_re0="inet 192.168.1.23 netmask 255.255.255.0" > defaultrouter="192.168.1.1" > # > wlans_iwn0="wlan0" > ifconfig_wlan0="WPA inet 192.168.1.21 netmask 255.255.255.0 ssid ronair2-1" > ============================================================================= > > ifconfig -a: > ============================================================================= > re0: flags=8843 metric 0 mtu 1500 > options=8209b > ether 00:24:21:65:ad:a0 > inet 192.168.1.23 netmask 0xffffff00 broadcast 192.168.1.255 > inet6 fe80::224:21ff:fe65:ada0%re0 prefixlen 64 scopeid 0x4 > nd6 options=29 > media: Ethernet autoselect (100baseTX ) > status: active > iwn0: flags=8803 metric 0 mtu 2290 > ether 00:22:fb:76:6d:18 > nd6 options=29 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11b > status: associated > lo0: flags=8049 metric 0 mtu 16384 > options=600003 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0xa > inet 127.0.0.1 netmask 0xff000000 > nd6 options=21 > wlan0: flags=8803 metric 0 mtu 1500 > ether 00:22:fb:76:6d:18 > inet 192.168.1.21 netmask 0xffffff00 broadcast 192.168.1.255 > inet6 fe80::222:fbff:fe76:6d18%wlan0 prefixlen 64 tentative scopeid 0xb > nd6 options=29 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > ssid ronair2-1 channel 1 (2412 MHz 11b) > country US authmode WPA1+WPA2/802.11i privacy OFF txpower 15 bmiss 10 > scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 > roam:rate 1 wme roaming MANUAL bintval 0 > ============================================================================= I don't see any real issue with your configuration, but I do see something odd and it may be tied to the problem you are seeing. FWIW, I also have an agn iwn card, but I only have a G access point at this time and it runs fine in G. The oddity is that you specify your ssid in the rc.conf file while using WPA. I've never seen that before. It's in my wpa_supplicant.conf file. It seems more reasonable for a laptop that may need to associate with a home and a work SSID as well as ones at conferences and, in my case alternate work and home SSIDs. When it is in the rc.conf file, it requires change with every relocation. in any case, you might try moving the SID into the wpa_supplicant.conf file, but my bet is it is N specific. Paging Adrian. -- R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com