From owner-freebsd-wireless@freebsd.org Sun Oct 9 06:25:38 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9DE74C07829 for ; Sun, 9 Oct 2016 06:25:38 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 776FBE42 for ; Sun, 9 Oct 2016 06:25:38 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yuri.doctorlan.com (c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id u996Pbpd019387 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Sat, 8 Oct 2016 23:25:37 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190] claimed to be yuri.doctorlan.com To: freebsd-wireless From: Yuri Subject: What is the best choice of USB WiFi adapter working on FreeBSD? Message-ID: <96108220-fc4f-8c71-8df1-c683aa8d2406@rawbw.com> Date: Sat, 8 Oct 2016 23:25:36 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Oct 2016 06:25:38 -0000 I have Belkin F5D7050 USB WiFI NIC, but zyd driver is faulty and the card freezes up with the timeout message: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=138292. Can anybody recommend the USB NIC that works well on FreeBSD, is inexpensive and easily available? Yuri From owner-freebsd-wireless@freebsd.org Sun Oct 9 07:01:51 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B33BC07F2A for ; Sun, 9 Oct 2016 07:01:51 +0000 (UTC) (envelope-from vbotka@gmail.com) Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A2124DDE for ; Sun, 9 Oct 2016 07:01:50 +0000 (UTC) (envelope-from vbotka@gmail.com) Received: by mail-wm0-x22e.google.com with SMTP id f193so4670186wmg.1 for ; Sun, 09 Oct 2016 00:01:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references :organization:mime-version; bh=rid/vykG4DkHyt3Acn2h298xXEFR31ysAeSxOTa+S0I=; b=F1muXpDMSx8qVD9X1umzrfaftLo9Acp8IygYIhM5o5Of9zF2JeF46GVYMM2CyKkHwv fdzJLvQDWgazaSReYQ9vyCdVVPEWodAjUDa45BrI68uy0OH91YVBpjdhnOHoSe1nCAtN YMf5UvNkGXupm0kxOcpwD0+xuY74FWcWiZ+KrQ1aRy3pWHesaidUBAMt22NMo29uDRyz IC7WR9m9lLApfhbdR6qs43xY1mOA1+Ng1pQv4noe07TZIcWXpM1NiyIMTwFtn9NGQ2I6 sQpRftk8erDO5yz1fUg/YCg/DXhuPg331Kg8/nM4hM1fYirLBt+elJvbyLLlkP0XjSJ3 igxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:organization:mime-version; bh=rid/vykG4DkHyt3Acn2h298xXEFR31ysAeSxOTa+S0I=; b=YlvHDiK3D1luwNRi7OnnzomNJpWLptv6EMfEM4UxwBSnThudAhJXkE8RqNeA7Kg5ct 1ZlqECfs1xyKZC1Xdu54vD18H2VEX14ejZa1p5m5BNiEQ/E0Jx4eHIdFMrVdb+quQvvH 2VOxm4kLCCwO0Go0RG14YyXbd/HC/D/bEzBIzUBH45YYdjfQF/dGgG8OXchvvy41HfK7 FPabAv+7c2AVYj5llfsi3wIqqJDjWVwzDquLd101Zg3z+ktanOUDCXsa9Q15pkHEYPo3 bphObMQhU6DYkqUNrXw400UsZdJUsgBaqmBUmUDjB6jm87qlGQ+rv94ba7Un1qGIamqL J8Ew== X-Gm-Message-State: AA6/9RmcuUE9s2GdWI+iGEwsB7ug8KvRuzHatBbI4rDTXdAb9smSPDFRg+RahnHPD3U5VQ== X-Received: by 10.194.158.193 with SMTP id ww1mr22224129wjb.176.1475996508217; Sun, 09 Oct 2016 00:01:48 -0700 (PDT) Received: from planb.netng.org (ip-89-177-54-54.net.upcbroadband.cz. [89.177.54.54]) by smtp.gmail.com with ESMTPSA id rk14sm28428876wjb.6.2016.10.09.00.01.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 09 Oct 2016 00:01:47 -0700 (PDT) Date: Sun, 9 Oct 2016 09:01:44 +0200 From: Vladimir Botka To: Yuri Cc: freebsd-wireless Subject: Re: wpa_supplicant doesn't communicate with zyd(4) interface well Message-ID: <20161009090144.31a827ea@planb.netng.org> In-Reply-To: <3da5f80c-610e-d079-c0b4-fa2a9a9b120a@rawbw.com> References: <3da5f80c-610e-d079-c0b4-fa2a9a9b120a@rawbw.com> Organization: na X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; i686-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/Z5yrbu=uq1BupNRCf8rB5SM"; protocol="application/pgp-signature" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Oct 2016 07:01:51 -0000 --Sig_/Z5yrbu=uq1BupNRCf8rB5SM Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hello! On Sat, 8 Oct 2016 16:09:30 -0700 Yuri wrote: > I use wpa_gui program (net/wpa_gui port), and it talked to ndis-based=20 > driver very well. wpa_supplicant is the latest version from ports. > Now I switched to the Belkin device using zyd driver, and wpa_gui just=20 > doesn't communicate well with it. It can't switch wifi network using the= =20 > combobox, for example. > Anybody know what might be the problem? > Yuri To find the problem more details from wpa_supplicant would be needed. You might want to add following line to /etc/rc.conf and post the log. wpa_supplicant_flags=3D"-dd -t -f /var/log/wpa_supplicant.log" But, I'd recommend to try and configure the interface without wpa_gui first. If this doesn't work wpa_gui won't help. wpa_gui is just an GUI to configure wpa_supplicant. https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-wireless= .html But, to save time, you might want to change the adapter. Best choice is Intel for client and Atheros for hostap. Ralink is doing well too. For example RT5370 USB dongles work fine for me in 10.3. Available from $20 (amazon) to $3 (aliexpress). # usbconfig -u 0 -a 4 dump_device_desc ugen0.4: <802.11 n WLAN Ralink> at usbus0, cfg=3D0 md=3DHOST spd=3DFULL (12Mbps) pwr=3DON (450mA) bLength =3D 0x0012=20 bDescriptorType =3D 0x0001=20 bcdUSB =3D 0x0200=20 bDeviceClass =3D 0x0000 bDeviceSubClass =3D 0x0000=20 bDeviceProtocol =3D 0x0000=20 bMaxPacketSize0 =3D 0x0040=20 idVendor =3D 0x148f=20 idProduct =3D 0x5370=20 bcdDevice =3D 0x0101=20 iManufacturer =3D 0x0001 iProduct =3D 0x0002 iSerialNumber =3D 0x0003 bNumConfigurations =3D 0x0001 HTH. Cheers and have fun, -vlado --Sig_/Z5yrbu=uq1BupNRCf8rB5SM Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEbBAEBCAAGBQJX+etZAAoJEJDRmRKO1E8B8UQH93Vn8P4EKP/uRrbSy2NvBqjr BkPJbMEWC/M78QxVcNQSZ9VB3PQkI2E/VrRVSebnFzZXidypRiiVxzlEsVu2Xp/f He+O/mYF7mFoq4rghzf3rn2IWsyfsG4OTm2gYbQBWW19J97KsXSp1B0O5lT13L64 7zXvay/WC0Jl8+WsyHpgQagjl9WZfC+Ob6oDyA579NG+g6lfJBuuppcE+WEyy3uo pRFMxtnp2rZfuk1XZ6doZwskQ1z3rQfyX3zp15pKPN7iyfhBNvJTmjxLuI5JRhMo 6OGngFjvfdqUdYHwV7ED3HkD0cKaslZpO9Dd6C8pbqdNwPUTm8TUY1bWgkZauQ== =k0mc -----END PGP SIGNATURE----- --Sig_/Z5yrbu=uq1BupNRCf8rB5SM-- From owner-freebsd-wireless@freebsd.org Sun Oct 9 07:09:14 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41C33C0503B for ; Sun, 9 Oct 2016 07:09:14 +0000 (UTC) (envelope-from vbotka@gmail.com) Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C8D949 for ; Sun, 9 Oct 2016 07:09:13 +0000 (UTC) (envelope-from vbotka@gmail.com) Received: by mail-wm0-x231.google.com with SMTP id f193so4856498wmg.1 for ; Sun, 09 Oct 2016 00:09:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references :organization:mime-version; bh=CrlZLU2XBBtW5uV/IUqdYy6jzG8O3MiLocgOZkVFdpk=; b=rOQtIcHeh5CiEMYKAzUBE8T29snKRhZKsoyl7hmeVQTjlwQugmdQzCjkBa05rvr22J FFQem/vC8o2qhdWFz7bVYG0XjnhYtO17I3ldfgyneclBVzVPvZRVsLQK0VKPsFhc0rCB Uuz6KR4rViu6CwON5RkO7HUmdlPMapXZYJzuLIYIiXnQv/XB9DHARpjnqh36Fw1KZENV Vfgd4iBKd/kgw+q2+8ldbYoic9u7KqVxC7LlwmBdWlLNJvsY8FDAbE0CzaaiIv4j2Ge6 UC4fOuQhl8p1b5YckPgyQU36s3lPEbSovmWO7NNHFwvM/N8MflVB1abOvzKFqg80zBKC uo4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:organization:mime-version; bh=CrlZLU2XBBtW5uV/IUqdYy6jzG8O3MiLocgOZkVFdpk=; b=BUNL+XapyethEKiav302D5lYl30ibL2L1UVoHQzJu0ykUBEMiD6xAkRXWjCZywSeSd aFl2RaUFmnmIE67lhEFVtRJl5trqExIAdmw2H7lc8HCvkCXtuweA5fxzPb/eDF/IaH0d ZYzskTMi4T5xWU3TpBqT5TX8lh/3gJxaTL2HSqMeErHVlk4wWJUnCKtlSs36CmS5fTWD I+P82h188RwaD/YouBEe4tXfdrQgxgGNk3Aew5u2QVbW9FXKeVt9OuW4eYXG+ETeUdR3 lWslY36UHSJMYuWVaGi42OupRV6u8U5SZ3/JaBc51VP090nWFan/U5zG84BSnT7Q9ml+ l3Ew== X-Gm-Message-State: AA6/9Rlp5MduSHJgpj6IebhBWNGoUHcKheYGv9fhO69Z/6z2ufwjRKp1yUbZ8szc/xKS/Q== X-Received: by 10.28.203.136 with SMTP id b130mr5017345wmg.120.1475996951785; Sun, 09 Oct 2016 00:09:11 -0700 (PDT) Received: from planb.netng.org (ip-89-177-54-54.net.upcbroadband.cz. [89.177.54.54]) by smtp.gmail.com with ESMTPSA id rk14sm28455548wjb.6.2016.10.09.00.09.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 09 Oct 2016 00:09:10 -0700 (PDT) Date: Sun, 9 Oct 2016 09:09:08 +0200 From: Vladimir Botka To: Yuri Cc: freebsd-wireless Subject: Re: What is the best choice of USB WiFi adapter working on FreeBSD? Message-ID: <20161009090908.63fbb546@planb.netng.org> In-Reply-To: <96108220-fc4f-8c71-8df1-c683aa8d2406@rawbw.com> References: <96108220-fc4f-8c71-8df1-c683aa8d2406@rawbw.com> Organization: na X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; i686-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/bYUQ2OQxCFbsGcjr8ucO6eK"; protocol="application/pgp-signature" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Oct 2016 07:09:14 -0000 --Sig_/bYUQ2OQxCFbsGcjr8ucO6eK Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hello! On Sat, 8 Oct 2016 23:25:36 -0700 Yuri wrote: > I have Belkin F5D7050 USB WiFI NIC, but zyd driver is faulty and the=20 > card freezes up with the timeout message:=20 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D138292. > Can anybody recommend the USB NIC that works well on FreeBSD, is=20 > inexpensive and easily available? > Yuri RT5370 USB dongles work for me without any problem for over a year. (No 11n for USB in 10.3, just 11g). https://www.aliexpress.com/price/ralink-rt5370_price.html Cheers, -vlado --Sig_/bYUQ2OQxCFbsGcjr8ucO6eK Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJX+e0VAAoJEJDRmRKO1E8BNvYH/0qK78CxfNzlsczNuX0xiYMy rk+2CTrgPxL4iCAwBSymARob5ozM9kKQbrqLmLEuevMS83SWKGcdDH7iYxmpzvaH Ug9HX1BmEpwXNt4xd1l9Z7/DFmp7H1auTCReXSDW36ODQgs/ImIIxT/IBWs9Rct+ 2/H4MlUOADV1jIRtBb98bK/hby/0n2PZlfdgeiXNHR2dFMa2gvSeLfLYeQG6QJL7 k/jkbIw8pTGZLF41aB5vK/HTWqk7cd8lnuY16Cyq+ASgXznXMMtYSNMFJKwTzmzx TgkCAGI9orFsTfnhhdMq3KgKsMLScLGSOJg1CzXBiNRZE56UzmYWsVsPWP/UGVw= =ReaI -----END PGP SIGNATURE----- --Sig_/bYUQ2OQxCFbsGcjr8ucO6eK-- From owner-freebsd-wireless@freebsd.org Sun Oct 9 07:32:19 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CBEA9C05579 for ; Sun, 9 Oct 2016 07:32:19 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id BC4A8B0D for ; Sun, 9 Oct 2016 07:32:19 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yuri.doctorlan.com (c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id u997WI41022359 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Sun, 9 Oct 2016 00:32:18 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190] claimed to be yuri.doctorlan.com Subject: Re: wpa_supplicant doesn't communicate with zyd(4) interface well References: <3da5f80c-610e-d079-c0b4-fa2a9a9b120a@rawbw.com> <20161009090144.31a827ea@planb.netng.org> To: freebsd-wireless From: Yuri Message-ID: Date: Sun, 9 Oct 2016 00:32:17 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <20161009090144.31a827ea@planb.netng.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Oct 2016 07:32:19 -0000 On 10/09/2016 00:01, Vladimir Botka wrote: > To find the problem more details from wpa_supplicant would be needed. > You might want to add following line to /etc/rc.conf and post the log. > > wpa_supplicant_flags="-dd -t -f /var/log/wpa_supplicant.log" Thank you for your answer. I found that this long-standing bug in zyd(4) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=138292 is probably causing this problem as I am also getting the device timeout messages. Yuri From owner-freebsd-wireless@freebsd.org Sun Oct 9 08:55:33 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A95ACC07D42 for ; Sun, 9 Oct 2016 08:55:33 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6A01A961 for ; Sun, 9 Oct 2016 08:55:33 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x236.google.com with SMTP id k64so8412396itb.0 for ; Sun, 09 Oct 2016 01:55:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=KpEwEFYrg8hSxn+rzwpJnVTOSbgdj+d8QhL/JIlyk7A=; b=W2MyuDCwtCHD1N/UMYVpJDoRZNn90LS9F4YSFqEo8hEToz9MdLHvR6vUOdu7GTEWMP 5DAta7rVgNEAMRiT4QbtBht8gD5mD5V2GO7NaytL9AE1sppYFtvWXHoaPZZwLimm/EmN voAxBcDz3wgBCk8kDSP68A/aZcV2lROdkho77huyOQWbEpIVdlbk7bQYfh2RXwKLq+Bt pENtNELHCtQu7ZQGC/RhaAbjj7vcuIqgKiGL8NGjw8SsEMQr4x9HuM719QUcWs4gHcqC HSKrEGYzANJD1DEvSXVcjKBhCz5+I9SM39v8HwvyrN/ueMAV8OLe2ITH2O2blEOd/1nU UBjQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=KpEwEFYrg8hSxn+rzwpJnVTOSbgdj+d8QhL/JIlyk7A=; b=OT2O5oLaUm4wIg0BIiU5hX6pfu+6wk/OxllzmvJ6/jD05ZwVJVsS0/RsOZxgmkdLvJ r+P7rWCEerYOXaWBWkOqP3KQijCr7o0yQ4X67tlv6tl4PWrZuxjL84p6wEFpd+6mk0JT 2jfBfk+efdmYoTQ9WWdfQQq6k+amLTXgcqDkW8PWBAJLTxbDnPLBEw8ztmnqoPqP+2+H COTuMdZ95fbQ0/pFahwnC4vPfwCeO2wkDZqUGt3wJ7skD7HkfBx7geY2uQtaydmDTbgy zsdAe4a66+LxCH8OwSRAjXI7PLxqx5qSNm4c+mXl55YGxNniyjUu1S+Zdwnw7gGGw5FW Ovxg== X-Gm-Message-State: AA6/9RlakwJn9X7QS5+EPiSgC3oO9a0MmJOYouon5vDeBx1bexb7Y7HGtgh6Ej421VZUQj5Jz1imWEOeRwXHsA== X-Received: by 10.36.135.138 with SMTP id f132mr5324318ite.101.1476003332562; Sun, 09 Oct 2016 01:55:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.57.215 with HTTP; Sun, 9 Oct 2016 01:55:32 -0700 (PDT) In-Reply-To: <20161009090908.63fbb546@planb.netng.org> References: <96108220-fc4f-8c71-8df1-c683aa8d2406@rawbw.com> <20161009090908.63fbb546@planb.netng.org> From: blubee blubeeme Date: Sun, 9 Oct 2016 16:55:32 +0800 Message-ID: Subject: Re: What is the best choice of USB WiFi adapter working on FreeBSD? To: Vladimir Botka Cc: Yuri , freebsd-wireless Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Oct 2016 08:55:33 -0000 I have a TP-LINK TL-WDN3200 works great. On Sun, Oct 9, 2016 at 3:09 PM, Vladimir Botka wrote: > Hello! > > On Sat, 8 Oct 2016 23:25:36 -0700 > Yuri wrote: > > I have Belkin F5D7050 USB WiFI NIC, but zyd driver is faulty and the > > card freezes up with the timeout message: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=138292. > > Can anybody recommend the USB NIC that works well on FreeBSD, is > > inexpensive and easily available? > > Yuri > > RT5370 USB dongles work for me without any problem for over a year. (No > 11n for USB in 10.3, just 11g). > https://www.aliexpress.com/price/ralink-rt5370_price.html > > Cheers, > > -vlado > From owner-freebsd-wireless@freebsd.org Sun Oct 9 18:17:27 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CA22EC07900 for ; Sun, 9 Oct 2016 18:17:27 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 911DB6EB for ; Sun, 9 Oct 2016 18:17:27 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-it0-x22a.google.com with SMTP id o19so60956950ito.1 for ; Sun, 09 Oct 2016 11:17:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=fRkN60eKDTxM25HAkiK4xY01vTd0XOiJRNZ+ScaoLgQ=; b=UE8J+/OQT/6W0b41WwWlDk2GuX0EIRxQ5sNoxhFRvjxbf5AZjDpIwyrJ3+fI5LEwjT 6tQmh+DqCnP67GoHAmefQy58mdx8+kH6kO6kJWGjxp5Lwpitv+N9UmHSFLa3GU1ldAIr r6h+e4U3jqAlpgvXBnUtVE80ls9hVGHYlkgdFEw7KpaXc5193ed9E74MAx3LnVDydEIb 4b1/WfFXkgGZ+F4KDnyKvk9PuZsMV+2x5MX8r8o5RUvqZNzdcfIHzQh/L4Dp2ImMCf4z ua0vVEMQs1T197wt6G9GTKZyrnrcKiMgeoSvkmGuRQ9VxYWrMQRBChsJcOX5sqtLEpyP gtVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=fRkN60eKDTxM25HAkiK4xY01vTd0XOiJRNZ+ScaoLgQ=; b=ZRSbaxDdHjlJc7k64VQJ1Ej3Q/kEtHzSq83UAEoK3Ti+sv3xzoDd2MvX9/rlFCA7dH oKgbBf/wvGr0sU2MfrqAm3x4ErCg1VOIqXRyNjlWf2rGQcPcgv4KBaoizTZ92UAZyQP4 ZbcqAgC0E2pzGoo3/4hfWBe4H4gCF87VX4/CNG/vu0NCeH9Iv4kcwSNF1evcBY51VHAV DmVzparFcaQAOHGwXItkhjJtXbvIKC8hltFQR8PAv/bjvnEotXeOh2d36pb5OnA9vAby Wysxhi7vb7CtIfRgQN6+Fc0Gx2xoXbd0QsBow3RzMEXT0rnREuDc5I3Vkg7FTpoeuH2X OISQ== X-Gm-Message-State: AA6/9Rn/Ix2h6YyhzHpTvTeZakdyl6AkZi0lRo3DfgTY9UEmD+p6yqSbc/dBdPtWG7cck7K2sd5UkG2HRbOmyQ== X-Received: by 10.36.228.195 with SMTP id o186mr6398710ith.39.1476037047019; Sun, 09 Oct 2016 11:17:27 -0700 (PDT) MIME-Version: 1.0 Sender: adrian.chadd@gmail.com Received: by 10.36.141.129 with HTTP; Sun, 9 Oct 2016 11:17:24 -0700 (PDT) Received: by 10.36.141.129 with HTTP; Sun, 9 Oct 2016 11:17:24 -0700 (PDT) In-Reply-To: References: <3da5f80c-610e-d079-c0b4-fa2a9a9b120a@rawbw.com> <20161009090144.31a827ea@planb.netng.org> From: Adrian Chadd Date: Sun, 9 Oct 2016 11:17:24 -0700 X-Google-Sender-Auth: 86F5xmLnMdcOnAXzb8lMXhO578U Message-ID: Subject: Re: wpa_supplicant doesn't communicate with zyd(4) interface well To: Yuri Cc: freebsd-wireless Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Oct 2016 18:17:27 -0000 Hi, I'll go see if we can add more device debugging to that driver. I remember fixing TX hangs in other USB drivers. A On Oct 9, 2016 12:32 AM, "Yuri" wrote: > On 10/09/2016 00:01, Vladimir Botka wrote: > >> To find the problem more details from wpa_supplicant would be needed. >> You might want to add following line to /etc/rc.conf and post the log. >> >> wpa_supplicant_flags="-dd -t -f /var/log/wpa_supplicant.log" >> > > > Thank you for your answer. I found that this long-standing bug in zyd(4) > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=138292 is probably > causing this problem as I am also getting the device timeout messages. > > > Yuri > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org > " > From owner-freebsd-wireless@freebsd.org Sun Oct 9 18:33:27 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1D481C07C5E for ; Sun, 9 Oct 2016 18:33:27 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 0A5A7CBD; Sun, 9 Oct 2016 18:33:26 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yuri.doctorlan.com (c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id u99IXPYP085232 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sun, 9 Oct 2016 11:33:25 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190] claimed to be yuri.doctorlan.com Subject: Re: wpa_supplicant doesn't communicate with zyd(4) interface well To: Adrian Chadd References: <3da5f80c-610e-d079-c0b4-fa2a9a9b120a@rawbw.com> <20161009090144.31a827ea@planb.netng.org> Cc: freebsd-wireless From: Yuri Message-ID: <940ff60e-8466-2a4f-8f9a-80d6b9b62831@rawbw.com> Date: Sun, 9 Oct 2016 11:33:24 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Oct 2016 18:33:27 -0000 On 10/09/2016 11:17, Adrian Chadd wrote: > > I'll go see if we can add more device debugging to that driver. I > remember fixing TX hangs in other USB drivers. > Yes, please do. Please let me know if you need me to test it. Thanks, Yuri From owner-freebsd-wireless@freebsd.org Sun Oct 9 21:00:38 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 08347C0742E for ; Sun, 9 Oct 2016 21:00:38 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D09FE6E5 for ; Sun, 9 Oct 2016 21:00:37 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u99L01cA089625 for ; Sun, 9 Oct 2016 21:00:37 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201610092100.u99L01cA089625@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-wireless@FreeBSD.org Subject: Problem reports for freebsd-wireless@FreeBSD.org that need special attention Date: Sun, 09 Oct 2016 21:00:37 +0000 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Oct 2016 21:00:38 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 206801 | iwn(4) page fault on netif restart Open | 154598 | [ath] Atheros 5424/2424 can't connect to WPA netw Open | 163312 | [panic] [ath] kernel panic: page fault with ath0 Open | 166190 | [ath] TX hangs and frames stuck in TX queue Open | 166357 | [ath] 802.11n TX stall when the first frame in th Open | 169362 | [ath] AR5416: radar pulse PHY errors sometimes in Open | 169433 | [iwn] iwn(4) doesn't support 6235 chip. Open | 211689 | panic with lagg failover wireless ath and iwm 8 problems total for which you should take action. From owner-freebsd-wireless@freebsd.org Sun Oct 9 22:22:02 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BECF8C0BB38; Sun, 9 Oct 2016 22:22:02 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 81F10B81; Sun, 9 Oct 2016 22:22:02 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-it0-x236.google.com with SMTP id z65so54930320itc.0; Sun, 09 Oct 2016 15:22:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=B7EPTlsI4G18YWl8Gqv99gHK6oJWO1ja8qOG598UxMQ=; b=YQk2c3ruPWNpzkUWm3MD6WfGZTkIqNe0Co16TOEWq7RUXF/sgvfQxALWB9vCY5S3TH VT90T0M3vjHfNr/0qWhewry+5wnOJYLw/5eDLPUZ8MURYfIln1PayPKRAlJqZX6fOv9g cl/hOurwi/mvWq3C4ta3D6Dw3vWyh9S1vIShXwvbqpwYI0UggjspH5pmLJDj5FB7rZRw 6EXhbeuXTB/UpfbPv143QeoSy3Ype5WDH0FyjjjRxPXaBHllOjw7rJ7K+LP4d5wmGKI6 STQ2CqK20khyGG9WqhpDBhgifB7fHdSlt8MeeGTYxmSBXuQHOPd5VIXagqDGXcJY8VIU HUZg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=B7EPTlsI4G18YWl8Gqv99gHK6oJWO1ja8qOG598UxMQ=; b=kG+ucCXXqnprW6RQGb6L0Yw66E5f5e/Owcrx1JZaHX3YlTLSIu3y8ONaJIdn7RCGt7 XcZARn+K1th+ipqOaUps3ekE6FTt6DSerY9TDsPT9owH5QxYN5KLgACAYWBw27ZaTuUA 6U8wYAwDGs9iQjq2HSkbIyh76pL0lMo1W+UMhxoYvcKbZNop2d5J/dwgEaop70cNNf9B mmqFx26z/Wd/FgUZDJxMdE32hwMkQdL0HlVEEZQZ46W5iWddwMs+n7iSj3NLJlaHpFGZ FlOtaYLfhSZ5o7I0y2j1VY18Wu7c8ak2PCyVeJD10F9kVXzfdzUpekszjk4S2po/91Hp pkCA== X-Gm-Message-State: AA6/9RkjlnMs5r4vfnT/8IIB7KLVG9nqHgrmu5NpBZTwvxaMS+TdwrsQ5ClsDO+nC401g72Zi0rDV+y36EeYRA== X-Received: by 10.36.228.195 with SMTP id o186mr7128882ith.39.1476051721818; Sun, 09 Oct 2016 15:22:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.141.129 with HTTP; Sun, 9 Oct 2016 15:22:00 -0700 (PDT) In-Reply-To: <13052a1c-db9b-6e08-eb1a-d75b93c67c33@ambient-md.com> References: <3684c340-3020-31f7-64f1-babf90be8565@ambient-md.com> <13052a1c-db9b-6e08-eb1a-d75b93c67c33@ambient-md.com> From: Adrian Chadd Date: Sun, 9 Oct 2016 15:22:00 -0700 Message-ID: Subject: Re: RPI2 AP To: Peter Garshtja , "freebsd-wireless@freebsd.org" Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Oct 2016 22:22:02 -0000 hiya, ok. We'll need some more debugging from the driver and net80211. Andriy? Any ideas? -a On 8 October 2016 at 08:11, Peter Garshtja wrote: > Good Morning Adrian, > > I added and rebooted RPI2, but the result is the same > > wlan_amrr_load="YES" to /boot/loader.conf > > ifconfig wlan0 list sta > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > 50:55:27:ff:dc:04 1 5 54M 20.5 0 2482 38240 EPS AQE RSN > WME > 00:13:ef:66:18:49 2 5 1M 14.0 0 7130 27104 EPS AQE RSN > WME > > After ~ 5 minutes all the stations were disconnected > > 10:43 # ifconfig wlan0 list sta > 10:43 # ifconfig wlan0 list sta > 10:43 # > > WLAN interface details > ------------------------------ > ifconfig wlan0 list caps > drivercaps=591c541 > cryptocaps=b > htcaps=6000c<> > ------------------------------ > > Kernel modules loaded > > Id Refs Address Size Name > 1 31 0xc0100000 9bfaec kernel > 2 1 0xc0ac0000 a168 wlan_amrr.ko > 3 7 0xc0acb000 59a18 wlan.ko > 4 1 0xc46d2000 11000 if_bridge.ko > 5 1 0xc46e3000 e000 bridgestp.ko > 6 1 0xc4731000 d000 if_vlan.ko > 7 1 0xc484c000 27000 if_urtwn.ko > 8 1 0xc4774000 b000 firmware.ko > 9 1 0xc46bf000 a000 pflog.ko > 10 1 0xc4b2c000 3a000 pf.ko > 11 1 0xc4e25000 9000 wlan_xauth.ko > 12 1 0xc4888000 a000 wlan_wep.ko > 13 1 0xc4ef9000 b000 wlan_tkip.ko > 14 1 0xc4f0c000 e000 wlan_ccmp.ko > > I have 2 different wifi dongles with the same chipset and the behavior is > the same. > > Also here is the dmesg after reboot > > Copyright (c) 1992-2016 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 11.0-RELEASE-p1 #0 r306544M: Fri Sep 30 18:26:52 EDT 2016 > ptg@rpi2:/root/crochet/work/obj/arm.armv6/usr/src/sys/RPI2 arm > FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM > 3.8.0) > VT: init without driver. > sema_sysinit > CPU: Cortex A7 rev 5 (Cortex-A core) > Supported features: ARM_ISA THUMB2 JAZELLE THUMBEE ARMv4 Security_Ext > WB enabled LABT branch prediction disabled > LoUU:2 LoC:3 LoUIS:2 > Cache level 1: > 32KB/64B 4-way data cache WB Read-Alloc Write-Alloc > 32KB/32B 2-way instruction cache Read-Alloc > Cache level 2: > 512KB/64B 8-way unified cache WB Read-Alloc Write-Alloc > real memory = 989851648 (943 MB) > avail memory = 955379712 (911 MB) > > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > random: entropy device external interface > kbd0 at kbdmux0 > ofwbus0: > simplebus0: mem 0x3f000000-0x3fffffff on > ofwbus0 > local_intc0: mem 0x40000000-0x400000ff on > simplebus0 > generic_timer0: on ofwbus0 > Timecounter "ARM MPCore Timecounter" frequency 19200000 Hz quality 1000 > Event timer "ARM MPCore Eventtimer" frequency 19200000 Hz quality 1000 > intc0: mem 0xb200-0xb3ff on simplebus0 > bcmwd0: mem 0x10001c-0x100027 on simplebus0 > gpio0: mem 0x200000-0x2000af on simplebus0 > gpio0: read-only pins: 46,48-53. > gpio0: reserved pins: 48-53. > gpiobus0: on gpio0 > gpioled0: at pin 35 on gpiobus0 > gpioled1: at pin 47 on gpiobus0 > gpioc0: on gpio0 > iichb0: mem 0x205000-0x20501f on simplebus0 > iicbus0: on iichb0 > iic0: on iicbus0 > iichb1: mem 0x804000-0x80401f on simplebus0 > iicbus1: on iichb1 > iic1: on iicbus1 > spi0: mem 0x204000-0x20401f on simplebus0 > spibus0: on spi0 > bcm_dma0: mem 0x7000-0x7fff,0xe05000-0xe05fff on > simplebus0 > mbox0: mem 0xb880-0xb8bf on simplebus0 > sdhci_bcm0: mem 0x300000-0x3000ff on > simplebus0 > mmc0: on sdhci_bcm0 > uart0: mem 0x201000-0x201fff on simplebus0 > uart0: console (115200,n,8,1) > vchiq0: mem 0xb800-0xb84f on simplebus0 > vchiq: local ver 8 (min 3), remote ver 8. > pcm0: on vchiq0 > bcm283x_dwcotg0: mem > 0x980000-0x99ffff on simplebus0 > usbus0 on bcm283x_dwcotg0 > cpulist0: on ofwbus0 > cpu0: on cpulist0 > bcm2835_cpufreq0: on cpu0 > cpu1: on cpulist0 > cpu2: on cpulist0 > cpu3: on cpulist0 > fb0: on ofwbus0 > fbd0 on fb0 > VT: initialize with new VT driver "fb". > fb0: 1680x1050(1680x1050@0,0) 24bpp > fb0: fbswap: 1, pitch 5040, base 0x3d384000, screen_size 5322240 > cryptosoft0: > Timecounters tick every 10.000 msec > usbus0: 480Mbps High Speed USB v2.0 > ugen0.1: at usbus0 > uhub0: on usbus0 > mmcsd0: 8GB at mmc0 > 41.6MHz/4bit/65535-block > bcm2835_cpufreq0: ARM 600MHz, Core 250MHz, SDRAM 400MHz, Turbo OFF > Release APs > Trying to mount root from ufs:/dev/mmcsd0s2a [rw,noatime]... > warning: no time-of-day clock registered, system time will not be set > accurately > uhub0: 1 port with 1 removable, self powered > ugen0.2: at usbus0 > uhub1: on > usbus0 > uhub1: MTT enabled > random: unblocking device. > uhub1: 5 ports with 4 removable, self powered > ugen0.3: at usbus0 > smsc0: on usbus0 > smsc0: chip 0xec00, rev. 0002 > miibus0: on smsc0 > ukphy0: PHY 1 on miibus0 > ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > ue0: on smsc0 > ue0: Ethernet address: b8:27:eb:f2:8e:4e > ugen0.4: at usbus0 > bridge0: Ethernet address: 02:fd:a6:82:73:00 > ue0: changing name to 'mgmt' > smsc0: chip 0xec00, rev. 0002 > mgmt: link state changed to DOWN > vlan0: changing name to 'wan' > vlan1: changing name to 'lan' > mgmt: link state changed to UP > lan: link state changed to UP > wan: link state changed to UP > urtwn0: on usbus0 > urtwn0: MAC/BB RTL8188EU, RF 6052 1T1R > urtwn0: enabling 11n > wlan0: Ethernet address: 00:c6:d2:21:c9:34 > wlan0: promiscuous mode enabled > bridge0: link state changed to UP > pflog0: promiscuous mode enabled > mgmt: promiscuous mode enabled > lan: promiscuous mode enabled > > > Thanks, > Peter > > > On 10/8/2016 12:51 AM, Adrian Chadd wrote: > > heh, try adding wlan_amrr_load="YES" to /boot/loader.conf and rebooting? > > > -a > > > On 7 October 2016 at 18:59, Peter Garshtja > wrote: > > Greetings, > > Here is uname - 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0 r306544M > > > Below is dmesg > > > Copyright (c) 1992-2016 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 11.0-RELEASE-p1 #0 r306544M: Fri Sep 30 18:26:52 EDT 2016 > ptg@rpi2:/root/crochet/work/obj/arm.armv6/usr/src/sys/RPI2 arm > FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM > 3.8.0) > VT: init without driver. > sema_sysinit > CPU: Cortex A7 rev 5 (Cortex-A core) > Supported features: ARM_ISA THUMB2 JAZELLE THUMBEE ARMv4 Security_Ext > WB enabled LABT branch prediction disabled > LoUU:2 LoC:3 LoUIS:2 > Cache level 1: > 32KB/64B 4-way data cache WB Read-Alloc Write-Alloc > 32KB/32B 2-way instruction cache Read-Alloc > Cache level 2: > 512KB/64B 8-way unified cache WB Read-Alloc Write-Alloc > real memory = 989851648 (943 MB) > avail memory = 956411904 (912 MB) > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > random: entropy device external interface > kbd0 at kbdmux0 > ofwbus0: > simplebus0: mem 0x3f000000-0x3fffffff on > ofwbus0 > local_intc0: mem 0x40000000-0x400000ff on > simplebus0 > generic_timer0: on ofwbus0 > Timecounter "ARM MPCore Timecounter" frequency 19200000 Hz quality 1000 > Event timer "ARM MPCore Eventtimer" frequency 19200000 Hz quality 1000 > intc0: mem 0xb200-0xb3ff on simplebus0 > bcmwd0: mem 0x10001c-0x100027 on simplebus0 > gpio0: mem 0x200000-0x2000af on simplebus0 > gpio0: read-only pins: 46,48-53. > gpio0: reserved pins: 48-53. > gpiobus0: on gpio0 > gpioled0: at pin 35 on gpiobus0 > gpioled1: at pin 47 on gpiobus0 > gpioc0: on gpio0 > iichb0: mem 0x205000-0x20501f on simplebus0 > iicbus0: on iichb0 > iic0: on iicbus0 > iichb1: mem 0x804000-0x80401f on simplebus0 > iicbus1: on iichb1 > iic1: on iicbus1 > spi0: mem 0x204000-0x20401f on simplebus0 > spibus0: on spi0 > bcm_dma0: mem 0x7000-0x7fff,0xe05000-0xe05fff on > simplebus0 > mbox0: mem 0xb880-0xb8bf on simplebus0 > sdhci_bcm0: mem 0x300000-0x3000ff on > simplebus0 > mmc0: on sdhci_bcm0 > uart0: mem 0x201000-0x201fff on simplebus0 > uart0: console (115200,n,8,1) > vchiq0: mem 0xb800-0xb84f on simplebus0 > vchiq: local ver 8 (min 3), remote ver 8. > pcm0: on vchiq0 > bcm283x_dwcotg0: mem > 0x980000-0x99ffff on simplebus0 > usbus0 on bcm283x_dwcotg0 > cpulist0: on ofwbus0 > cpu0: on cpulist0 > bcm2835_cpufreq0: on cpu0 > cpu1: on cpulist0 > cpu2: on cpulist0 > cpu3: on cpulist0 > fb0: on ofwbus0 > fbd0 on fb0 > VT: initialize with new VT driver "fb". > fb0: 1680x1050(1680x1050@0,0) 24bpp > fb0: fbswap: 1, pitch 5040, base 0x3d384000, screen_size 5322240 > cryptosoft0: > Timecounters tick every 10.000 msec > usbus0: 480Mbps High Speed USB v2.0 > ugen0.1: at usbus0 > uhub0: on usbus0 > mmcsd0: 8GB at mmc0 > 41.6MHz/4bit/65535-block > bcm2835_cpufreq0: ARM 600MHz, Core 250MHz, SDRAM 400MHz, Turbo OFF > Release APs > Trying to mount root from ufs:/dev/mmcsd0s2a [rw,noatime]... > WARNING: / was not properly dismounted > warning: no time-of-day clock registered, system time will not be set > accurately > uhub0: 1 port with 1 removable, self powered > ugen0.2: at usbus0 > uhub1: on > usbus0 > uhub1: MTT enabled > uhub1: 5 ports with 4 removable, self powered > random: unblocking device. > ugen0.3: at usbus0 > smsc0: on usbus0 > smsc0: chip 0xec00, rev. 0002 > miibus0: on smsc0 > ukphy0: PHY 1 on miibus0 > ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > ue0: on smsc0 > ue0: Ethernet address: b8:27:eb:f2:8e:4e > ugen0.4: at usbus0 > bridge0: Ethernet address: 02:fd:a6:82:73:00 > ue0: changing name to 'mgmt' > smsc0: chip 0xec00, rev. 0002 > mgmt: link state changed to DOWN > vlan0: changing name to 'wan' > vlan1: changing name to 'lan' > mgmt: link state changed to UP > lan: link state changed to UP > wan: link state changed to UP > urtwn0: on usbus0 > > *urtwn0: MAC/BB RTL8188EU, RF 6052 1T1R > > *urtwn0: enabling 11n > mgmt: link state changed to DOWN > lan: link state changed to DOWN > wan: link state changed to DOWN > mgmt: link state changed to UP > lan: link state changed to UP > wan: link state changed to UP > ieee80211_load_module: load the wlan_amrr module by hand for now. > wlan0: Ethernet address: 00:c6:d2:21:c9:34 > wlan0: promiscuous mode enabled > bridge0: link state changed to UP > pflog0: promiscuous mode enabled > mgmt: promiscuous mode enabled > lan: promiscuous mode enabled > > Thanks in advance, > > Peter > > On 10/7/2016 4:36 PM, Adrian Chadd wrote: > > + freebsd-wireless > > can you post a 'dmesg' output? That way we can see which urtwn NIC it > is and whether it logged anything. > > > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > > From owner-freebsd-wireless@freebsd.org Sun Oct 9 22:24:23 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A881C0BBC0; Sun, 9 Oct 2016 22:24:23 +0000 (UTC) (envelope-from andriyvos@gmail.com) Received: from mail-lf0-f49.google.com (mail-lf0-f49.google.com [209.85.215.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D7230C7D; Sun, 9 Oct 2016 22:24:22 +0000 (UTC) (envelope-from andriyvos@gmail.com) Received: by mail-lf0-f49.google.com with SMTP id b81so93812780lfe.1; Sun, 09 Oct 2016 15:24:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:cc:subject:references:date:mime-version :content-transfer-encoding:from:message-id:in-reply-to:user-agent; bh=NVH/5Ta2qEMQVL/dObZ9uNxT0ArF/pk7n7IgdywfD+I=; b=mnYU+sAls4/fq6abt5MfG27lQxwUzKHt6+lG06/LWyZINu0SouiH/N8hYfE9tKCgHO oMxxMDDkLisFI5i8r92rbbs6mBZIriBGVWwnNasMwQ/dmfKkxpLmmkyXDv+KPyYBjy6x 6c7PKyRi1PjDE2Eu9vogpgFFI3jA5SSP/SstIcvzfnXghkq6ovay8iXCyuMVdOxsdfTe +KzIPLW307FHMpoJfeUz+03ioFporRJFyaQLPUVaVWZNd+jB+800RfuTX40F5nhpvFaN 0gef25j5bR0vPsdNb8ZGNzjnrs4bWUKuB5+biu3xwf9EFdYXcCi/PPsXCQfH6yXMUTzD sRiw== X-Gm-Message-State: AA6/9Rk9M2LW5N8/MldGiZBdP9ezZkXUr6EgCwy2/mW+lmDco4GhpQSaRRxTggxcFa0Xlw== X-Received: by 10.25.18.97 with SMTP id h94mr12710701lfi.106.1476051854499; Sun, 09 Oct 2016 15:24:14 -0700 (PDT) Received: from localhost (host-176-37-109-22.la.net.ua. [176.37.109.22]) by smtp.gmail.com with ESMTPSA id b71sm5466842lfb.42.2016.10.09.15.24.13 (version=TLS1 cipher=AES128-SHA bits=128/128); Sun, 09 Oct 2016 15:24:14 -0700 (PDT) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Peter Garshtja" , "freebsd-wireless@freebsd.org" , "Adrian Chadd" Cc: "freebsd-arm@freebsd.org" Subject: Re: RPI2 AP References: <3684c340-3020-31f7-64f1-babf90be8565@ambient-md.com> <13052a1c-db9b-6e08-eb1a-d75b93c67c33@ambient-md.com> Date: Mon, 10 Oct 2016 01:24:14 +0300 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Andriy Voskoboinyk" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.16 (FreeBSD) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Oct 2016 22:24:23 -0000 Mon, 10 Oct 2016 01:22:00 +0300 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0=D0= =BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Adrian Chadd = : Have you tried to use the driver from https://github.com/s3erios/rtwn ? > hiya, > > ok. We'll need some more debugging from the driver and net80211. > > Andriy? Any ideas? > > > -a > > > On 8 October 2016 at 08:11, Peter Garshtja > wrote: >> Good Morning Adrian, >> >> I added and rebooted RPI2, but the result is the same >> >> wlan_amrr_load=3D"YES" to /boot/loader.conf >> >> ifconfig wlan0 list sta >> ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >> 50:55:27:ff:dc:04 1 5 54M 20.5 0 2482 38240 EPS AQE = = >> RSN >> WME >> 00:13:ef:66:18:49 2 5 1M 14.0 0 7130 27104 EPS AQE = = >> RSN >> WME >> >> After ~ 5 minutes all the stations were disconnected >> >> 10:43 # ifconfig wlan0 list sta >> 10:43 # ifconfig wlan0 list sta >> 10:43 # >> >> WLAN interface details >> ------------------------------ >> ifconfig wlan0 list caps >> drivercaps=3D591c541 >> cryptocaps=3Db >> htcaps=3D6000c<> >> ------------------------------ >> >> Kernel modules loaded >> >> Id Refs Address Size Name >> 1 31 0xc0100000 9bfaec kernel >> 2 1 0xc0ac0000 a168 wlan_amrr.ko >> 3 7 0xc0acb000 59a18 wlan.ko >> 4 1 0xc46d2000 11000 if_bridge.ko >> 5 1 0xc46e3000 e000 bridgestp.ko >> 6 1 0xc4731000 d000 if_vlan.ko >> 7 1 0xc484c000 27000 if_urtwn.ko >> 8 1 0xc4774000 b000 firmware.ko >> 9 1 0xc46bf000 a000 pflog.ko >> 10 1 0xc4b2c000 3a000 pf.ko >> 11 1 0xc4e25000 9000 wlan_xauth.ko >> 12 1 0xc4888000 a000 wlan_wep.ko >> 13 1 0xc4ef9000 b000 wlan_tkip.ko >> 14 1 0xc4f0c000 e000 wlan_ccmp.ko >> >> I have 2 different wifi dongles with the same chipset and the behavio= r = >> is >> the same. >> >> Also here is the dmesg after reboot >> >> Copyright (c) 1992-2016 The FreeBSD Project. >> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1= 994 >> The Regents of the University of California. All rights = >> reserved. >> FreeBSD is a registered trademark of The FreeBSD Foundation. >> FreeBSD 11.0-RELEASE-p1 #0 r306544M: Fri Sep 30 18:26:52 EDT 2016 >> ptg@rpi2:/root/crochet/work/obj/arm.armv6/usr/src/sys/RPI2 arm >> FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on= = >> LLVM >> 3.8.0) >> VT: init without driver. >> sema_sysinit >> CPU: Cortex A7 rev 5 (Cortex-A core) >> Supported features: ARM_ISA THUMB2 JAZELLE THUMBEE ARMv4 Security_Ex= t >> WB enabled LABT branch prediction disabled >> LoUU:2 LoC:3 LoUIS:2 >> Cache level 1: >> 32KB/64B 4-way data cache WB Read-Alloc Write-Alloc >> 32KB/32B 2-way instruction cache Read-Alloc >> Cache level 2: >> 512KB/64B 8-way unified cache WB Read-Alloc Write-Alloc >> real memory =3D 989851648 (943 MB) >> avail memory =3D 955379712 (911 MB) >> >> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs >> random: entropy device external interface >> kbd0 at kbdmux0 >> ofwbus0: >> simplebus0: mem = >> 0x3f000000-0x3fffffff on >> ofwbus0 >> local_intc0: mem 0x40000000-0x400000ff= on >> simplebus0 >> generic_timer0: on ofwbus0 >> Timecounter "ARM MPCore Timecounter" frequency 19200000 Hz quality 10= 00 >> Event timer "ARM MPCore Eventtimer" frequency 19200000 Hz quality 100= 0 >> intc0: mem 0xb200-0xb3ff on simplebus0= >> bcmwd0: mem 0x10001c-0x100027 on simplebus0 >> gpio0: mem 0x200000-0x2000af on = >> simplebus0 >> gpio0: read-only pins: 46,48-53. >> gpio0: reserved pins: 48-53. >> gpiobus0: on gpio0 >> gpioled0: at pin 35 on gpiobus0 >> gpioled1: at pin 47 on gpiobus0 >> gpioc0: on gpio0 >> iichb0: mem 0x205000-0x20501f on = >> simplebus0 >> iicbus0: on iichb0 >> iic0: on iicbus0 >> iichb1: mem 0x804000-0x80401f on = >> simplebus0 >> iicbus1: on iichb1 >> iic1: on iicbus1 >> spi0: mem 0x204000-0x20401f on simplebu= s0 >> spibus0: on spi0 >> bcm_dma0: mem 0x7000-0x7fff,0xe05000-0xe05ff= f = >> on >> simplebus0 >> mbox0: mem 0xb880-0xb8bf on simplebus0 >> sdhci_bcm0: mem 0x300000-0x3000ff on= >> simplebus0 >> mmc0: on sdhci_bcm0 >> uart0: mem 0x201000-0x201fff on simplebus0 >> uart0: console (115200,n,8,1) >> vchiq0: mem 0xb800-0xb84f on simplebus0 >> vchiq: local ver 8 (min 3), remote ver 8. >> pcm0: on vchiq0 >> bcm283x_dwcotg0: me= m >> 0x980000-0x99ffff on simplebus0 >> usbus0 on bcm283x_dwcotg0 >> cpulist0: on ofwbus0 >> cpu0: on cpulist0 >> bcm2835_cpufreq0: on cpu0 >> cpu1: on cpulist0 >> cpu2: on cpulist0 >> cpu3: on cpulist0 >> fb0: on ofwbus0 >> fbd0 on fb0 >> VT: initialize with new VT driver "fb". >> fb0: 1680x1050(1680x1050@0,0) 24bpp >> fb0: fbswap: 1, pitch 5040, base 0x3d384000, screen_size 5322240 >> cryptosoft0: >> Timecounters tick every 10.000 msec >> usbus0: 480Mbps High Speed USB v2.0 >> ugen0.1: at usbus0 >> uhub0: on usb= us0 >> mmcsd0: 8GB at mmc0 >> 41.6MHz/4bit/65535-block >> bcm2835_cpufreq0: ARM 600MHz, Core 250MHz, SDRAM 400MHz, Turbo OFF >> Release APs >> Trying to mount root from ufs:/dev/mmcsd0s2a [rw,noatime]... >> warning: no time-of-day clock registered, system time will not be set= >> accurately >> uhub0: 1 port with 1 removable, self powered >> ugen0.2: at usbus0 >> uhub1: = >> on >> usbus0 >> uhub1: MTT enabled >> random: unblocking device. >> uhub1: 5 ports with 4 removable, self powered >> ugen0.3: at usbus0 >> smsc0: on usbus= 0 >> smsc0: chip 0xec00, rev. 0002 >> miibus0: on smsc0 >> ukphy0: PHY 1 on miibus0 >> ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >> ue0: on smsc0 >> ue0: Ethernet address: b8:27:eb:f2:8e:4e >> ugen0.4: at usbus0 >> bridge0: Ethernet address: 02:fd:a6:82:73:00 >> ue0: changing name to 'mgmt' >> smsc0: chip 0xec00, rev. 0002 >> mgmt: link state changed to DOWN >> vlan0: changing name to 'wan' >> vlan1: changing name to 'lan' >> mgmt: link state changed to UP >> lan: link state changed to UP >> wan: link state changed to UP >> urtwn0: on = >> usbus0 >> urtwn0: MAC/BB RTL8188EU, RF 6052 1T1R >> urtwn0: enabling 11n >> wlan0: Ethernet address: 00:c6:d2:21:c9:34 >> wlan0: promiscuous mode enabled >> bridge0: link state changed to UP >> pflog0: promiscuous mode enabled >> mgmt: promiscuous mode enabled >> lan: promiscuous mode enabled >> >> >> Thanks, >> Peter >> >> >> On 10/8/2016 12:51 AM, Adrian Chadd wrote: >> >> heh, try adding wlan_amrr_load=3D"YES" to /boot/loader.conf and reboo= ting? >> >> >> -a >> >> >> On 7 October 2016 at 18:59, Peter Garshtja >> wrote: >> >> Greetings, >> >> Here is uname - 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0 r30654= 4M >> >> >> Below is dmesg >> >> >> Copyright (c) 1992-2016 The FreeBSD Project. >> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1= 994 >> The Regents of the University of California. All rights = >> reserved. >> FreeBSD is a registered trademark of The FreeBSD Foundation. >> FreeBSD 11.0-RELEASE-p1 #0 r306544M: Fri Sep 30 18:26:52 EDT 2016 >> ptg@rpi2:/root/crochet/work/obj/arm.armv6/usr/src/sys/RPI2 arm >> FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on= = >> LLVM >> 3.8.0) >> VT: init without driver. >> sema_sysinit >> CPU: Cortex A7 rev 5 (Cortex-A core) >> Supported features: ARM_ISA THUMB2 JAZELLE THUMBEE ARMv4 Security_Ex= t >> WB enabled LABT branch prediction disabled >> LoUU:2 LoC:3 LoUIS:2 >> Cache level 1: >> 32KB/64B 4-way data cache WB Read-Alloc Write-Alloc >> 32KB/32B 2-way instruction cache Read-Alloc >> Cache level 2: >> 512KB/64B 8-way unified cache WB Read-Alloc Write-Alloc >> real memory =3D 989851648 (943 MB) >> avail memory =3D 956411904 (912 MB) >> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs >> random: entropy device external interface >> kbd0 at kbdmux0 >> ofwbus0: >> simplebus0: mem = >> 0x3f000000-0x3fffffff on >> ofwbus0 >> local_intc0: mem 0x40000000-0x400000ff= on >> simplebus0 >> generic_timer0: on ofwbus0 >> Timecounter "ARM MPCore Timecounter" frequency 19200000 Hz quality 10= 00 >> Event timer "ARM MPCore Eventtimer" frequency 19200000 Hz quality 100= 0 >> intc0: mem 0xb200-0xb3ff on simplebus0= >> bcmwd0: mem 0x10001c-0x100027 on simplebus0 >> gpio0: mem 0x200000-0x2000af on = >> simplebus0 >> gpio0: read-only pins: 46,48-53. >> gpio0: reserved pins: 48-53. >> gpiobus0: on gpio0 >> gpioled0: at pin 35 on gpiobus0 >> gpioled1: at pin 47 on gpiobus0 >> gpioc0: on gpio0 >> iichb0: mem 0x205000-0x20501f on = >> simplebus0 >> iicbus0: on iichb0 >> iic0: on iicbus0 >> iichb1: mem 0x804000-0x80401f on = >> simplebus0 >> iicbus1: on iichb1 >> iic1: on iicbus1 >> spi0: mem 0x204000-0x20401f on simplebu= s0 >> spibus0: on spi0 >> bcm_dma0: mem 0x7000-0x7fff,0xe05000-0xe05ff= f = >> on >> simplebus0 >> mbox0: mem 0xb880-0xb8bf on simplebus0 >> sdhci_bcm0: mem 0x300000-0x3000ff on= >> simplebus0 >> mmc0: on sdhci_bcm0 >> uart0: mem 0x201000-0x201fff on simplebus0 >> uart0: console (115200,n,8,1) >> vchiq0: mem 0xb800-0xb84f on simplebus0 >> vchiq: local ver 8 (min 3), remote ver 8. >> pcm0: on vchiq0 >> bcm283x_dwcotg0: me= m >> 0x980000-0x99ffff on simplebus0 >> usbus0 on bcm283x_dwcotg0 >> cpulist0: on ofwbus0 >> cpu0: on cpulist0 >> bcm2835_cpufreq0: on cpu0 >> cpu1: on cpulist0 >> cpu2: on cpulist0 >> cpu3: on cpulist0 >> fb0: on ofwbus0 >> fbd0 on fb0 >> VT: initialize with new VT driver "fb". >> fb0: 1680x1050(1680x1050@0,0) 24bpp >> fb0: fbswap: 1, pitch 5040, base 0x3d384000, screen_size 5322240 >> cryptosoft0: >> Timecounters tick every 10.000 msec >> usbus0: 480Mbps High Speed USB v2.0 >> ugen0.1: at usbus0 >> uhub0: on usb= us0 >> mmcsd0: 8GB at mmc0 >> 41.6MHz/4bit/65535-block >> bcm2835_cpufreq0: ARM 600MHz, Core 250MHz, SDRAM 400MHz, Turbo OFF >> Release APs >> Trying to mount root from ufs:/dev/mmcsd0s2a [rw,noatime]... >> WARNING: / was not properly dismounted >> warning: no time-of-day clock registered, system time will not be set= >> accurately >> uhub0: 1 port with 1 removable, self powered >> ugen0.2: at usbus0 >> uhub1: = >> on >> usbus0 >> uhub1: MTT enabled >> uhub1: 5 ports with 4 removable, self powered >> random: unblocking device. >> ugen0.3: at usbus0 >> smsc0: on usbus= 0 >> smsc0: chip 0xec00, rev. 0002 >> miibus0: on smsc0 >> ukphy0: PHY 1 on miibus0 >> ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >> ue0: on smsc0 >> ue0: Ethernet address: b8:27:eb:f2:8e:4e >> ugen0.4: at usbus0 >> bridge0: Ethernet address: 02:fd:a6:82:73:00 >> ue0: changing name to 'mgmt' >> smsc0: chip 0xec00, rev. 0002 >> mgmt: link state changed to DOWN >> vlan0: changing name to 'wan' >> vlan1: changing name to 'lan' >> mgmt: link state changed to UP >> lan: link state changed to UP >> wan: link state changed to UP >> urtwn0: on = >> usbus0 >> >> *urtwn0: MAC/BB RTL8188EU, RF 6052 1T1R >> >> *urtwn0: enabling 11n >> mgmt: link state changed to DOWN >> lan: link state changed to DOWN >> wan: link state changed to DOWN >> mgmt: link state changed to UP >> lan: link state changed to UP >> wan: link state changed to UP >> ieee80211_load_module: load the wlan_amrr module by hand for now. >> wlan0: Ethernet address: 00:c6:d2:21:c9:34 >> wlan0: promiscuous mode enabled >> bridge0: link state changed to UP >> pflog0: promiscuous mode enabled >> mgmt: promiscuous mode enabled >> lan: promiscuous mode enabled >> >> Thanks in advance, >> >> Peter >> >> On 10/7/2016 4:36 PM, Adrian Chadd wrote: >> >> + freebsd-wireless >> >> can you post a 'dmesg' output? That way we can see which urtwn NIC it= >> is and whether it logged anything. >> >> >> >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org= " >> >> > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to = > "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@freebsd.org Tue Oct 11 01:28:13 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 636CBC0B54B; Tue, 11 Oct 2016 01:28:13 +0000 (UTC) (envelope-from kevlo@ns.kevlo.org) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 074BD6E5; Tue, 11 Oct 2016 01:28:12 +0000 (UTC) (envelope-from kevlo@ns.kevlo.org) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.15.2/8.15.2) with ESMTPS id u9B1R3NO036722 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 11 Oct 2016 09:27:04 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.15.2/8.15.2/Submit) id u9B1R3qM036721; Tue, 11 Oct 2016 09:27:03 +0800 (CST) (envelope-from kevlo) Date: Tue, 11 Oct 2016 09:27:02 +0800 From: Kevin Lo To: Andriy Voskoboinyk Cc: "freebsd-wireless@freebsd.org" , "freebsd-current@freebsd.org" , Adrian Chadd Subject: Re: urtwn(4) / rtwn(4) drivers are merged - call for review / testing Message-ID: <20161011012702.GA36712@ns.kevlo.org> References: <20160922092442.GA72044@ns.kevlo.org> <20160923015840.GA77979@ns.kevlo.org> <20160923071830.GA79146@ns.kevlo.org> <20161001150924.GA48641@ns.kevlo.org> <20161003005523.GA57437@ns.kevlo.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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 Oct 2016 01:28:13 -0000 On Sat, Oct 08, 2016 at 02:18:54AM +0300, Andriy Voskoboinyk wrote: > > Mon, 03 Oct 2016 03:55:23 +0300 було написано Kevin Lo : > > Hi! Hi Andriy, > Can you refresh the tree and retest it (dev.rtwn.0.debug=0x829f) ? I refreshed the tree and retested it, unfortunately it's still the same. Here's the log: https://people.freebsd.org/~kevlo/rtl8188ce-debuglog > > P.S. If Rx is still broken (status is always 0) try to execute > 'ifconfig wlan0 promisc' It doesn't help either :( > > On Sun, Oct 02, 2016 at 10:15:49AM -0700, Adrian Chadd wrote: > >> > >> hi, > > > > Hi Adrian, > > > >> can you turn on debugging? Do you see RX frames? > > > > No Rx frames. The log is pretty much the same one I sent on the list: > > https://lists.freebsd.org/pipermail/freebsd-wireless/2016-September/007093.html > > > >> -a > > > > Thanks, > > Kevin > > > >> On 1 October 2016 at 08:09, Kevin Lo wrote: > >> > Strange, rtwn(4) stops working. I tried to scan for the available > >> network, > >> > but it just returns empty results. > >> > > >> > On Fri, Sep 23, 2016 at 02:44:13PM +0300, Andriy Voskoboinyk wrote: > >> >> > >> >> Fri, 23 Sep 2016 10:18:30 +0300 було написано Kevin Lo > >> : > >> >> > >> >> Few more questions: > >> >> 1) does it work with h/w encryption support? (enabled by default) > >> >> (if 'yes' - I will remove 'hardware crypto enabled' warning). > >> >> 2) is there rate control support? (wlandebug -i wlan0 rate ; then > >> transmit > >> >> something - if it works then AMRR will print it's current status > >> >> periodically) > >> >> 3) can you test some disabled capabilities? (ad-hoc/AP modes, 11n) > >> >> (see r92ce_adj_devcaps() in > >> sys/dev/rtwn/rtl8192c/pci/r92ce_attach.c). > >> >> > >> >> > It works for me, thanks :) > >> >> > > >> >> > Kevin > >> >> > > >> >> > On Fri, Sep 23, 2016 at 09:08:15AM +0300, Andriy Voskoboinyk wrote: > >> >> >> > >> >> >> Fri, 23 Sep 2016 04:58:40 +0300 було написано Kevin Lo > >> >> >> : > >> >> >> > >> >> >> Thanks for the log file, > >> >> >> > >> >> >> Tx 'device timeouts' should be fixed in > >> >> >> > >> https://github.com/s3erios/rtwn/commit/f78d51b6ed8590e3aeb65fbf616aa767034a89f5 > >> >> >> (currently I'm reviewing PCI-specific code to see if there are any > >> >> >> additional > >> >> >> issues - e.g., there are no Rx events in the log file). > >> >> >> > >> >> >> > On Thu, Sep 22, 2016 at 01:54:21PM +0300, Andriy Voskoboinyk > >> wrote: > >> >> >> >> > >> >> >> >> Thu, 22 Sep 2016 12:24:42 +0300 було написано Kevin Lo > >> >> >> >> : > >> >> >> >> > >> >> >> >> Hi, > >> >> >> >> > >> >> >> >> So, the driver was fully tested. Thanks! > >> >> >> >> Can you set dev.rtwn.0.debug=0x829f for RTL8188CE to see how > >> big > >> >> >> >> the problem is? > >> >> >> > > >> >> >> > Sure. Here you go > >> >> >> https://people.freebsd.org/~kevlo/rtl8188ce-debug.txt > >> >> >> > > >> >> >> > Thanks, > >> >> >> > Kevin > >> >> >> > > >> >> >> >> > Hi Andriy, > >> >> >> >> > > >> >> >> >> > First of all, THANK YOU! You're doing amazing work! > >> >> >> >> > Second, I've done some testing on the following devices, > >> >> >> downloading > >> >> >> >> > FreeBSD-12.0-CURRENT-amd64-20160809-r303880-disc1.iso from > >> >> >> >> > ftp.freebsd.org: > >> >> >> >> > > >> >> >> >> > - ASUS USB-N10 NANO (RTL8188CUS): > >> >> >> >> > rtwn0: >> 2.00/2.00, > >> >> >> addr > >> >> >> >> > 3> on usbus0 > >> >> >> >> > rtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R > >> >> >> >> > > >> >> >> >> > - TP-Link TL-WN725N v2 (RTL8188EU): > >> >> >> >> > rtwn0: >> addr 4> on > >> >> >> >> > usbus0 > >> >> >> >> > rtwn0: MAC/BB RTL8188EU, RF 6052 1T1R > >> >> >> >> > > >> >> >> >> > - D-Link DWA-131 (RTL8192CU): > >> >> >> >> > rtwn0: >> 2.00/2.00, > >> >> >> addr > >> >> >> >> > 3> on usbus0 > >> >> >> >> > rtwn0: MAC/BB RTL8192CU, RF 6052 2T2R > >> >> >> >> > > >> >> >> >> > - TP-Link Archer T4U (RTL8812AU): > >> >> >> >> > rtwn0: >> addr 7> on > >> >> >> >> > usbus0 > >> >> >> >> > rtwn0: MAC/BB RTL8812AU, RF 6052 2T2R > >> >> >> >> > > >> >> >> >> > - D-Link DWA-171 rev A1 (RTL8821AU): > >> >> >> >> > rtwn0: <802.11n WLAN Adapter> on usbus0 > >> >> >> >> > rtwn0: MAC/BB RTL8821AU, RF 6052 1T1R > >> >> >> >> > > >> >> >> >> > - RTL8188CE mini pcie: > >> >> >> >> > rtwn0: port 0xd000-0xd0ff mem > >> >> >> >> > 0x90800000-0x90803fff irq 17 at device 0.0 on pci1 > >> >> >> >> > rtwn0: r92ce_attach: warning: hardware crypto enabled > >> >> >> >> > rtwn0: MAC/BB RTL8188CE, RF 6052 1T1R > >> >> >> >> > > >> >> >> >> > All seems to be ok, except RTL8188CE PCIe adapter doesn't > >> work: > >> >> >> >> > > >> >> >> >> > rtwn0: r92ce_post_init: warning: net80211 ratectl is used > >> >> >> >> > rtwn0: device timeout > >> >> >> >> > > >> >> >> >> > Kevin > >> >> >> >> > > >> >> >> >> > On Mon, Sep 19, 2016 at 04:26:38PM +0300, Andriy Voskoboinyk > >> wrote: > >> >> >> >> >> > >> >> >> >> >> Thu, 01 Sep 2016 19:29:03 +0300 було написано Andriy > >> Voskoboinyk > >> >> >> >> >> : > >> >> >> >> >> > >> >> >> >> >> Now it resides on https://github.com/s3erios/freebsd-rtwn > >> >> >> (integrated > >> >> >> >> >> into src tree, so it can be built with 'make buildkernel' / > >> 'make > >> >> >> >> >> buildworld'). > >> >> >> >> >> > >> >> >> >> >> This the last stage; once all reported issues will be > >> resolved, > >> >> >> I'm > >> >> >> >> >> going to merge it into HEAD. > >> >> >> >> >> > >> >> >> >> >> > Hi everyone, > >> >> >> >> >> > > >> >> >> >> >> > rtwn(4), urtwn(4) and urtwm (from previous emails) > >> drivers were > >> >> >> >> merged > >> >> >> >> >> > into a > >> >> >> >> >> > single rtwn driver (plus rtwn_usb / rtwn_pci device > >> glue); the > >> >> >> >> code is > >> >> >> >> >> > available on https://github.com/s3erios/rtwn repository. > >> Among > >> >> >> >> >> bugfixes / > >> >> >> >> >> > code deduplication, there some new features too: > >> >> >> >> >> > > >> >> >> >> >> > 1) multi-vap support (one any wireless interface + one STA > >> >> >> >> interface + > >> >> >> >> >> > any number of monitor mode interfaces). > >> >> >> >> >> > 2) few new sysctls: > >> >> >> >> >> > * dev.rtwn.#.crypto - controls how to use hardware > >> crypto > >> >> >> >> >> acceleration > >> >> >> >> >> > * dev.rtwn.#.ratectl_selected > >> >> >> >> >> > * dev.rtwn.#.ratectl - selects current 'rate control' > >> >> >> algorithm > >> >> >> >> >> > (currently only 'none' and 'net80211' are supported; > >> RTL8192CE > >> >> >> >> needs > >> >> >> >> >> > testing > >> >> >> >> >> > with the last). > >> >> >> >> >> > 3) (incomplete) power management support for RTL8188EU > >> (requires > >> >> >> >> >> > firmware). > >> >> >> >> >> > 4) Short Guard Interval support. > >> >> >> >> >> > > >> >> >> >> >> > It's known to work with RTL8188CUS, RTL8188EU and > >> RTL8821AU; > >> >> >> >> however, > >> >> >> >> >> > it was never tested with RTL8192CE or RTL8812AU. > >> >> >> >> >> > > >> >> >> >> >> > How-to-build: > >> >> >> >> >> > 1) download / checkout the repository. > >> >> >> >> >> > 2) apply 'patch-usbdevs.diff' against '/usr/src' > >> >> >> >> >> > 3) build and install rtwn module: > >> >> >> >> >> > cd $repository/sys/modules/rtwn && make && make > >> install > >> >> >> >> >> > 4) build and install rtwn_usb/rtwn_pci: > >> >> >> >> >> > cd ../rtwn_usb && make && make install > >> >> >> >> >> > cd ../rtwn_pci && make && make install > >> >> >> >> >> > 5) unload previous && load current drivers: > >> >> >> >> >> > kldunload if_urtwn if_rtwn > >> >> >> >> >> > kldload /boot/modules/if_rtwn.ko > >> >> >> /boot/modules/if_rtwn_usb.ko > >> >> >> >> >> > /boot/modules/if_rtwn_pci.ko > >> >> >> >> >> > 6) Use. > >> >> >> >> >> _______________________________________________ > >> >> >> >> >> freebsd-wireless@freebsd.org mailing list > >> >> >> >> >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > >> >> >> >> >> To unsubscribe, send any mail to > >> >> >> >> >> "freebsd-wireless-unsubscribe@freebsd.org" > >> >> >> >> >> > >> >> >> >> > >> >> >> _______________________________________________ > >> >> >> freebsd-current@freebsd.org mailing list > >> >> >> https://lists.freebsd.org/mailman/listinfo/freebsd-current > >> >> >> To unsubscribe, send any mail to > >> >> >> "freebsd-current-unsubscribe@freebsd.org" > >> >> >> > >> >> >> > >> >> > _______________________________________________ > >> >> > freebsd-wireless@freebsd.org mailing list > >> >> > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > >> >> > To unsubscribe, send any mail to > >> >> > "freebsd-wireless-unsubscribe@freebsd.org" > >> >> > >> >> > >> > _______________________________________________ > >> > freebsd-current@freebsd.org mailing list > >> > https://lists.freebsd.org/mailman/listinfo/freebsd-current > >> > To unsubscribe, send any mail to > >> "freebsd-current-unsubscribe@freebsd.org" > >> > >> > > _______________________________________________ > > freebsd-wireless@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > > To unsubscribe, send any mail to > > "freebsd-wireless-unsubscribe@freebsd.org" > > From owner-freebsd-wireless@freebsd.org Tue Oct 11 20:21:40 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B737EC0DA4E; Tue, 11 Oct 2016 20:21:40 +0000 (UTC) (envelope-from andriyvos@gmail.com) Received: from mail-lf0-f44.google.com (mail-lf0-f44.google.com [209.85.215.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 453D9AB1; Tue, 11 Oct 2016 20:21:39 +0000 (UTC) (envelope-from andriyvos@gmail.com) Received: by mail-lf0-f44.google.com with SMTP id b75so55558578lfg.3; Tue, 11 Oct 2016 13:21:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:cc:subject:references:date:mime-version :content-transfer-encoding:from:message-id:in-reply-to:user-agent; bh=MPG1u7jiQC6tzI11BpZKI3eYKzu3WwlZheT/DYrPDoQ=; b=itIAV9tFmcxpQCyVfmG487jUXbs0OjwOS5Xe9mMfudwLsqhos4lK2fJLmB2AVJu4aA YedzBGNjunqK9rRgn5s27jpsXMastd0TMuFMjf0PLK0uFCodwNwanWQhLpnuRP7OemlZ WZ+zoZ7uP/X7+ToljDt4zHwiwSNAZXDnlD6ITiyttECS752vCOs2mEn4uRtUS1GvNxJA GEsn6YTaDIyQByRtTWOLoMTJjafZxYM9o41Yqyn3t+jO/xK7+QzVhsUTxSkTIZN/VHHh D9EoYx+l8f3SNwv/mDcHMNNmoBAiNirp6G4L5oZzMhLJa0qQEeISlVn3dejTJXRBLVJN hjYw== X-Gm-Message-State: AA6/9RmtPJ5+dCxqlaCP2ZJ85qDbwtxR8AITcnOtZ2BNGN9Hon3R7Xiply4GgcHjo4HCDg== X-Received: by 10.25.212.212 with SMTP id l203mr4524197lfg.2.1476217291751; Tue, 11 Oct 2016 13:21:31 -0700 (PDT) Received: from localhost (host-176-37-109-22.la.net.ua. [176.37.109.22]) by smtp.gmail.com with ESMTPSA id 102sm1467442lft.33.2016.10.11.13.21.30 (version=TLS1 cipher=AES128-SHA bits=128/128); Tue, 11 Oct 2016 13:21:30 -0700 (PDT) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Kevin Lo" Cc: "freebsd-wireless@freebsd.org" , "freebsd-current@freebsd.org" , "Adrian Chadd" Subject: Re: urtwn(4) / rtwn(4) drivers are merged - call for review / testing References: <20160922092442.GA72044@ns.kevlo.org> <20160923015840.GA77979@ns.kevlo.org> <20160923071830.GA79146@ns.kevlo.org> <20161001150924.GA48641@ns.kevlo.org> <20161003005523.GA57437@ns.kevlo.org> <20161011012702.GA36712@ns.kevlo.org> Date: Tue, 11 Oct 2016 23:21:24 +0300 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Andriy Voskoboinyk" Message-ID: In-Reply-To: <20161011012702.GA36712@ns.kevlo.org> User-Agent: Opera Mail/12.16 (FreeBSD) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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 Oct 2016 20:21:40 -0000 Tue, 11 Oct 2016 04:27:02 +0300 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0=D0= =BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Kevin Lo : I have created 'pci_modified' branch to speed-up the process (RTL881*AU = = will not work with it for now); right now it contains (mostly) unmodified initialization path from rtwn(4) driver. If this version will work, I will revert some 'RTWN_PCI_WORKAROUND' temporary blocks until the culprit is found. > On Sat, Oct 08, 2016 at 02:18:54AM +0300, Andriy Voskoboinyk wrote: >> >> Mon, 03 Oct 2016 03:55:23 +0300 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0= =D0=BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Kevin Lo = >> : >> >> Hi! > > Hi Andriy, > >> Can you refresh the tree and retest it (dev.rtwn.0.debug=3D0x829f) ? > > I refreshed the tree and retested it, unfortunately it's still the sam= e. > Here's the log: https://people.freebsd.org/~kevlo/rtl8188ce-debuglog >> >> P.S. If Rx is still broken (status is always 0) try to execute >> 'ifconfig wlan0 promisc' > > It doesn't help either :( From owner-freebsd-wireless@freebsd.org Wed Oct 12 02:08:09 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF91AC0D303; Wed, 12 Oct 2016 02:08:09 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B5BC810FA; Wed, 12 Oct 2016 02:08:09 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-it0-x231.google.com with SMTP id e203so70803418itc.0; Tue, 11 Oct 2016 19:08:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=4O2RMNlKO4erAK/bE8A+KfvkLy7U6jDibA1qsj5kQn4=; b=r+Ewp5UCMZq5gQ1W6wTEPp/3GYQn5TgBZ/NW3ciOEWKK/gPcDC12NxdQxj0c4/Gx74 QCvO58jJyElbMZCrG+8nyT3ZV/W3fF+O0DIUhbk9IxKzwEHI3dJKL2ddrcHEN6k6xWtv 9p8U8LNBwpkniM+ckT8ii7zMzKjJuORn66V3/RtVIxdQZ9CSdNiWKIoYs9z+6EjmXwLi ZNlPbguqu5Qm/Axw9GlaKHpyjOHmiEt9SkFeyZokjKr+dhnrFZRwQSjosp3GU9Cuypbc lbYlkIjuKG4oCLXe/INcM3VQfklx4WuBz4+IlAPDMbcb/5eqFQGsRNsf0jxlP9lJb2yv 8y7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=4O2RMNlKO4erAK/bE8A+KfvkLy7U6jDibA1qsj5kQn4=; b=ZTNCq/Hh5ZRVuNBI9d0u+/OuOfMInQjvWe5P9j/i9fSWEsckqCN5yLISF92YRT9/WF epZqRfhJMw6H6vngLZ80zqYk1YGyj3t4eSn2vhcG1eJnnhQZ71KQX1UaEV5aztf1mm/x DxQkFm/1kKbtUpoFdRU8lrnkd8ez6UiE/HmhtwgYluILc9btRA4X07dGL3DqiAzevrZ2 LY0Czx02zA/PhJsh1/n+XwlHWLWuvPYynKHZGAZ5vDWcDuqvdCyaUyA3hunXZ9VEESCu GHQiaZIBWMQATKiSosAas2DpZ8+zEewAQhMrAharOIxebg9jEJzGAzjAd16MdXS9WuFI Dgzw== X-Gm-Message-State: AA6/9RnDdHf8yufkgGOnxHuS3+ePEDc4dgcmW8XNAIMvcHx4iEGo7u6QwPdcUHvcmbTTgkq6uDHlp8IeVofFvA== X-Received: by 10.36.52.141 with SMTP id z135mr566301itz.78.1476238088976; Tue, 11 Oct 2016 19:08:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.141.129 with HTTP; Tue, 11 Oct 2016 19:08:07 -0700 (PDT) In-Reply-To: References: <20160922092442.GA72044@ns.kevlo.org> <20160923015840.GA77979@ns.kevlo.org> <20160923071830.GA79146@ns.kevlo.org> <20161001150924.GA48641@ns.kevlo.org> <20161003005523.GA57437@ns.kevlo.org> <20161011012702.GA36712@ns.kevlo.org> From: Adrian Chadd Date: Tue, 11 Oct 2016 19:08:07 -0700 Message-ID: Subject: Re: urtwn(4) / rtwn(4) drivers are merged - call for review / testing To: Andriy Voskoboinyk Cc: Kevin Lo , "freebsd-wireless@freebsd.org" , "freebsd-current@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Wed, 12 Oct 2016 02:08:10 -0000 Hiya, So uhm - normal rtwn works fine, but andriy's merged version doesn't? -a From owner-freebsd-wireless@freebsd.org Wed Oct 12 04:35:30 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6DBE3C0BDDD; Wed, 12 Oct 2016 04:35:30 +0000 (UTC) (envelope-from kevlo@ns.kevlo.org) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DAF48DC1; Wed, 12 Oct 2016 04:35:28 +0000 (UTC) (envelope-from kevlo@ns.kevlo.org) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.15.2/8.15.2) with ESMTPS id u9C4YFMS045678 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 12 Oct 2016 12:34:16 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.15.2/8.15.2/Submit) id u9C4YFli045677; Wed, 12 Oct 2016 12:34:15 +0800 (CST) (envelope-from kevlo) Date: Wed, 12 Oct 2016 12:34:15 +0800 From: Kevin Lo To: Andriy Voskoboinyk Cc: "freebsd-wireless@freebsd.org" , "freebsd-current@freebsd.org" , Adrian Chadd Subject: Re: urtwn(4) / rtwn(4) drivers are merged - call for review / testing Message-ID: <20161012043415.GA45653@ns.kevlo.org> References: <20160923015840.GA77979@ns.kevlo.org> <20160923071830.GA79146@ns.kevlo.org> <20161001150924.GA48641@ns.kevlo.org> <20161003005523.GA57437@ns.kevlo.org> <20161011012702.GA36712@ns.kevlo.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Wed, 12 Oct 2016 04:35:30 -0000 I tried to use https://github.com/s3erios/rtwn/tree/pci_modified, still no luck. BTW, there's a compilation error: http://pastebin.com/hCFfYVSj To ensure that the adapter is not faulty, I tested with the snapshots image (FreeBSD-12.0-CURRENT-amd64-20160829-r305028-memstick.img), rtwn(4) works fine. Kevin On Tue, Oct 11, 2016 at 11:21:24PM +0300, Andriy Voskoboinyk wrote: > > Tue, 11 Oct 2016 04:27:02 +0300 було написано Kevin Lo : > > I have created 'pci_modified' branch to speed-up the process (RTL881*AU > will > not work with it for now); right now it contains (mostly) unmodified > initialization path from rtwn(4) driver. > > If this version will work, I will revert some 'RTWN_PCI_WORKAROUND' > temporary blocks until the culprit is found. > > > On Sat, Oct 08, 2016 at 02:18:54AM +0300, Andriy Voskoboinyk wrote: > >> > >> Mon, 03 Oct 2016 03:55:23 +0300 було написано Kevin Lo > >> : > >> > >> Hi! > > > > Hi Andriy, > > > >> Can you refresh the tree and retest it (dev.rtwn.0.debug=0x829f) ? > > > > I refreshed the tree and retested it, unfortunately it's still the same. > > Here's the log: https://people.freebsd.org/~kevlo/rtl8188ce-debuglog > >> > >> P.S. If Rx is still broken (status is always 0) try to execute > >> 'ifconfig wlan0 promisc' > > > > It doesn't help either :( > > From owner-freebsd-wireless@freebsd.org Wed Oct 12 15:17:14 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 023B8C0F774 for ; Wed, 12 Oct 2016 15:17:14 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from homobox.opal.com (opalcom-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:113d::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "opal.com", Issuer "OpalCA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A9410C5A for ; Wed, 12 Oct 2016 15:17:13 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from shibato (ANice-654-1-24-64.w83-197.abo.wanadoo.fr [83.197.219.64]) (authenticated bits=0) by homobox.opal.com (8.15.2/8.15.2) with ESMTPSA id u9CFH7MD065083 (version=TLSv1.2 cipher=AES128-GCM-SHA256 bits=128 verify=NO) for ; Wed, 12 Oct 2016 11:17:10 -0400 (EDT) (envelope-from fbsd@opal.com) Date: Wed, 12 Oct 2016 17:17:00 +0200 From: "J.R. Oldroyd" To: freebsd-wireless@freebsd.org Subject: Regression: ethernet + wireless/ath under lagg Message-ID: <20161012171700.5b4f9ea8@shibato> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd10.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (homobox.opal.com [100.64.0.6]); Wed, 12 Oct 2016 11:17:10 -0400 (EDT) X-Spam-Status: No, score=1.9 required=5.0 tests=AWL,BAYES_00, FSL_HELO_NON_FQDN_1,RCVD_IN_PBL,RCVD_IN_SORBS_DUL,RDNS_DYNAMIC shortcircuit=no autolearn=no autolearn_force=no version=3.4.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on homobox.opal.com X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Wed, 12 Oct 2016 15:17:14 -0000 Since something like 9.0-release, I have used the following to config an re and an ath interface together in a lagg. The intent is to have both ethernet and wireless interfaces share the lagg and be seamlessly pluggable between the two networks. It was necessary to set the ath's MAC address to be the same as the re's, else the wlan created from the ath would not associate. (The wlan's MAC address must be the same as the underlying device's MAC, else the wlan fails WPA authentication. Changing the underlying device's MAC before the wlan is created works OK.) This config has worked just fine on both 9.x and 10.x: In /etc/rc.conf: ifconfig_re0="up" ifconfig_re0_ipv6="inet6 accept_rtadv" ifconfig_ath0="`ifconfig re0 ether`" ifconfig_ath0="ether ${ifconfig_ath0##*ether }" wlans_ath0=wlan0 create_args_wlan0="regdomain FCC country US" ifconfig_wlan0="WPA" ifconfig_wlan0_ipv6="inet6 accept_rtadv" cloned_interfaces="lagg0" ifconfig_lagg0="laggproto failover laggport re0 laggport wlan0 DHCP" # WAN_IF ifconfig_lagg0_ipv6="inet6 accept_rtadv" Now, with 11.0-release, this no longer works because the ath interface doesn't exist any more, so ifconfig cannot pre-change its MAC. And, I have been unable to find a way of either determining or setting the ath's MAC address using sysctls. Now, the following does work, hard-coding the ath's MAC, and changing the re's address to that value, instead of the other way around: ether_ath0="70:1a:11:22:33:44" # actual ath0 MAC address ifconfig_re0="ether $ether_ath0 up" ifconfig_re0_ipv6="inet6 accept_rtadv" wlans_ath0=wlan0 create_args_wlan0="regdomain FCC country US" ifconfig_wlan0="WPA" ifconfig_wlan0_ipv6="inet6 accept_rtadv" cloned_interfaces="lagg0" ifconfig_lagg0="laggproto failover laggport re0 laggport wlan0 DHCP" # WAN_IF ifconfig_lagg0_ipv6="inet6 accept_rtadv" Obviously, hard-coding a MAC address isn't a good solution. Am I missing something? Is there a way to config this without a hard-coded address? Or, do we need to fix the bug that is preventing setting the wlan's MAC address to be something different from the underlying ath's address? -jr From owner-freebsd-wireless@freebsd.org Wed Oct 12 16:08:22 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1C203C0EBA8 for ; Wed, 12 Oct 2016 16:08:22 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DBC2B7E4 for ; Wed, 12 Oct 2016 16:08:21 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-it0-x22b.google.com with SMTP id e203so92449394itc.0 for ; Wed, 12 Oct 2016 09:08:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Bia0snmdIRhasPOVAP+pWT2V8KL36E2b6hqmoAmhPCc=; b=fqYNQgOAHiUD1RCcDWcwCWWGneeEEUDj6QMij0dtGua5/zohkaccNaR8KDaRgqLt/o PVCDsDYUhrjnljGz2x+0fg4h4T2Ei4coNywPSKKgosjrslaZEaEfh7kzb1fyFkp46Bq1 ftHJmZVuC2W+jbVuMpGJ2bNWMcc1Z+yZvD7KDaGrv1q8K1jHJMd/9CixO+0Fo4SotA2+ sZ6P/o/pBzc56RLXUCBc8wWoTPU9NwaDQKYs07MlsDJSnmqQEcoXUytj6v6D48nl6azX 3Y2YrPtdJ7iHwGQperHIXJrgJRUwSN2T1MVfqt/9VXNeZfUNQqXm8ZNaw4lHNsJutIdI xbOQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Bia0snmdIRhasPOVAP+pWT2V8KL36E2b6hqmoAmhPCc=; b=U1c7amqzVa/MtrWLs7s3L8vtQ0218wylwTzswRfT2BSaN9EFI8Ll0zOgCVVVw35eHl hFiZRDICPgo+EaiWu9GBZi2VoPL7dieKxsOJI5QgdRmYcoEKFV6jfF2sdi0DnRjoBRFR 6snG3p6xbc2oYvnKXlMUM5jFRiTX/hoiwXB3HcbikXvtIueHZuR5YWsgHaF+gDybCXkI G++Xi1G5bncrtYNAyEDrD42IRDVoA7zHyIvlq2eUOxyG8u8weC4sZrmpr+rOmi2kYIjX m6djJcM7Ygu+Ds84U1PEqyMmR3grAOnxc7s9zJog1YF//AlMk5y5odZSJIJCojAvFthT vqWw== X-Gm-Message-State: AA6/9RnLDmZ4YHl7+kI21ErHjAsRAz8bAiuepxrkK+sQtjFVIX1O7AVNIkMQliRo6GPTWq+1/kkSROcVwJ2ELA== X-Received: by 10.36.69.9 with SMTP id y9mr3171333ita.39.1476288501244; Wed, 12 Oct 2016 09:08:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.141.129 with HTTP; Wed, 12 Oct 2016 09:08:20 -0700 (PDT) In-Reply-To: <20161012171700.5b4f9ea8@shibato> References: <20161012171700.5b4f9ea8@shibato> From: Adrian Chadd Date: Wed, 12 Oct 2016 09:08:20 -0700 Message-ID: Subject: Re: Regression: ethernet + wireless/ath under lagg To: "J.R. Oldroyd" Cc: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Wed, 12 Oct 2016 16:08:22 -0000 hiya, there should be a way to create a vap with a specific mac address upon creation time. Sorry, doing lagg+wlan is not something we've been collectively using. :( Thanks, -adrian On 12 October 2016 at 08:17, J.R. Oldroyd wrote: > Since something like 9.0-release, I have used the following to config > an re and an ath interface together in a lagg. The intent is to have > both ethernet and wireless interfaces share the lagg and be seamlessly > pluggable between the two networks. It was necessary to set the ath's > MAC address to be the same as the re's, else the wlan created from the > ath would not associate. (The wlan's MAC address must be the same as > the underlying device's MAC, else the wlan fails WPA authentication. > Changing the underlying device's MAC before the wlan is created works > OK.) This config has worked just fine on both 9.x and 10.x: > > In /etc/rc.conf: > > ifconfig_re0="up" > ifconfig_re0_ipv6="inet6 accept_rtadv" > ifconfig_ath0="`ifconfig re0 ether`" > ifconfig_ath0="ether ${ifconfig_ath0##*ether }" > wlans_ath0=wlan0 > create_args_wlan0="regdomain FCC country US" > ifconfig_wlan0="WPA" > ifconfig_wlan0_ipv6="inet6 accept_rtadv" > cloned_interfaces="lagg0" > ifconfig_lagg0="laggproto failover laggport re0 laggport wlan0 DHCP" # WAN_IF > ifconfig_lagg0_ipv6="inet6 accept_rtadv" > > Now, with 11.0-release, this no longer works because the ath interface > doesn't exist any more, so ifconfig cannot pre-change its MAC. And, I > have been unable to find a way of either determining or setting the > ath's MAC address using sysctls. > > Now, the following does work, hard-coding the ath's MAC, and changing > the re's address to that value, instead of the other way around: > > ether_ath0="70:1a:11:22:33:44" # actual ath0 MAC address > ifconfig_re0="ether $ether_ath0 up" > ifconfig_re0_ipv6="inet6 accept_rtadv" > wlans_ath0=wlan0 > create_args_wlan0="regdomain FCC country US" > ifconfig_wlan0="WPA" > ifconfig_wlan0_ipv6="inet6 accept_rtadv" > cloned_interfaces="lagg0" > ifconfig_lagg0="laggproto failover laggport re0 laggport wlan0 DHCP" # WAN_IF > ifconfig_lagg0_ipv6="inet6 accept_rtadv" > > Obviously, hard-coding a MAC address isn't a good solution. > > Am I missing something? Is there a way to config this without a > hard-coded address? > > Or, do we need to fix the bug that is preventing setting the wlan's > MAC address to be something different from the underlying ath's > address? > > -jr > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@freebsd.org Wed Oct 12 18:31:39 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D790DC0FF04 for ; Wed, 12 Oct 2016 18:31:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C6F06BC0 for ; Wed, 12 Oct 2016 18:31:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9CIVdmq014576 for ; Wed, 12 Oct 2016 18:31:39 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213207] ath: Unable to set device MAC in FreeBSD 11 Date: Wed, 12 Oct 2016 18:31:39 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: avos@freebsd.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Wed, 12 Oct 2016 18:31:39 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213207 --- Comment #8 from Andriy Voskoboinyk --- Created attachment 175673 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D175673&action= =3Dedit wlanaddr fix Can you try the patch? It may fix MAC address change via 'wlanaddr' (but not via 'ether'). --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Wed Oct 12 19:33:05 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B387AC0F14C for ; Wed, 12 Oct 2016 19:33:05 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from homobox.opal.com (opalcom-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:113d::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "opal.com", Issuer "OpalCA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6461EDD9 for ; Wed, 12 Oct 2016 19:33:05 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from shibato (ANice-654-1-24-64.w83-197.abo.wanadoo.fr [83.197.219.64]) (authenticated bits=0) by homobox.opal.com (8.15.2/8.15.2) with ESMTPSA id u9CJX1bu066683 (version=TLSv1.2 cipher=AES128-GCM-SHA256 bits=128 verify=NO); Wed, 12 Oct 2016 15:33:02 -0400 (EDT) (envelope-from fbsd@opal.com) Date: Wed, 12 Oct 2016 21:32:55 +0200 From: "J.R. Oldroyd" To: Adrian Chadd Cc: "freebsd-wireless@freebsd.org" Subject: Re: Regression: ethernet + wireless/ath under lagg Message-ID: <20161012213255.585a7278@shibato> In-Reply-To: References: <20161012171700.5b4f9ea8@shibato> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd10.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (homobox.opal.com [100.64.0.6]); Wed, 12 Oct 2016 15:33:03 -0400 (EDT) X-Spam-Status: No, score=1.4 required=5.0 tests=AWL,BAYES_00, FSL_HELO_NON_FQDN_1,RCVD_IN_PBL,RCVD_IN_SORBS_DUL,RDNS_DYNAMIC shortcircuit=no autolearn=no autolearn_force=no version=3.4.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on homobox.opal.com X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Wed, 12 Oct 2016 19:33:05 -0000 On Wed, 12 Oct 2016 09:08:20 -0700 Adrian Chadd wrote: > > hiya, > > there should be a way to create a vap with a specific mac address upon > creation time. Sorry, doing lagg+wlan is not something we've been > collectively using. :( > > Thanks, > > > -adrian > > PR#213207 appears to be discussing this same problem. I am truly amazed that this "is not something we've been collectively using"! Here, we have all of Macs, Windows, Linux for which this "just works" and it also worked fine (with the config I posted earlier) on 9.x and 10.x. Your bog-standard, cheapo Linksys/Netgear/ whatever, bridge their wireless network to their wired ports, and it is common practice here to be using wireless and then to later plug into a wired port on those routers and have connections continue seamlessly. A way of determining the ath's MAC address so it can be used to set the re's MAC, or a way of setting the ath's MAC address prior to wlan creation is needed in 11.x. -jr From owner-freebsd-wireless@freebsd.org Wed Oct 12 19:47:36 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 25078C0F3E7 for ; Wed, 12 Oct 2016 19:47:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 14CF6330 for ; Wed, 12 Oct 2016 19:47:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9CJlZJh019939 for ; Wed, 12 Oct 2016 19:47:35 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213207] ath: Unable to set device MAC in FreeBSD 11 Date: Wed, 12 Oct 2016 19:47:35 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: fbsd@opal.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Wed, 12 Oct 2016 19:47:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213207 --- Comment #9 from fbsd@opal.com --- This affects us here, too. In an email thread on freebsd-wireless, "Regression: ethernet + wireless/ath under lagg", I posted an alternative work-around, but both the solution here and that one require hard-coded MAC addresses in config files, which isn't a good solution. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Wed Oct 12 19:54:39 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D1DB3C0F594 for ; Wed, 12 Oct 2016 19:54:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C18B4A19 for ; Wed, 12 Oct 2016 19:54:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9CJsdWc035358 for ; Wed, 12 Oct 2016 19:54:39 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213207] ath: Unable to set device MAC in FreeBSD 11 Date: Wed, 12 Oct 2016 19:54:39 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: fbsd@opal.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Wed, 12 Oct 2016 19:54:39 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213207 --- Comment #10 from fbsd@opal.com --- Oh, to follow-up on what I said in that thread, we need either a way to determine the ath's MAC address, e.g., a sysctl dev.ath.N.macaddr or simila= r, so that we can use this to set the ethernet's MAC, or we need a way to set = the ath's MAC address prior to wlan creation. Or both! As Adrian Chadd replied, "there should be a way to create a vap with a spec= ific mac address upon creation time". --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Wed Oct 12 20:32:17 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 95477C0FE6A for ; Wed, 12 Oct 2016 20:32:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 84B3D118 for ; Wed, 12 Oct 2016 20:32:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9CKWGJj061765 for ; Wed, 12 Oct 2016 20:32:17 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213207] ath: Unable to set device MAC in FreeBSD 11 Date: Wed, 12 Oct 2016 20:32:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Wed, 12 Oct 2016 20:32:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213207 Adrian Chadd changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adrian@freebsd.org --- Comment #11 from Adrian Chadd --- So, the challenge is thus. The device has a MAC address. There's a BSSID and a macaddress field. then, when creating say, cloned AP vaps, the isn't a list of MACs that the NIC ha= s - the reason they're typically only a small difference is there's a BSSID /ma= sk/ field for matching against. look at if_ath.c:assign_address() - and that on= ly happens for hostap and mbss modes. Now, before glebius removed the device entries from ifconfig, changing the parent device MAC would change what's effectively now ic->ic_macaddr. When= you create a new VAP, it clones ic->ic_macaddr unless you provide IEEE80211_CLONE_MACADDR as an argument and a separate MAC address. In that instance, the VAP is created with a completely different MAC address. Now t= hat there's no parent ifnet, there's no easy (ie, same for all devices) way of modifying ic_macaddr and having that programmed into the hardware for subsequent device updates. So here's what's going on: * the device will read its MAC from EEPROM, etc, and feed it into ic_macaddr * when creating VAPs, net80211 will use ic_macaddr unless given IEEE80211_CLONE_MACADDR as an argument - at which point it'll use a complet= ely separate MAC address for that argument. * trouble is, that won't really help with STA mode (at least on ath(4)) as there is only one MAC address, and that is what's prgorammed in via ath_hal_setmac() * when cloning AP VAPs, if_ath.c:assign_address() will update the chipset B= SSID mask, so multiple sequential MACs are accepted as "local" * .. but that doesn't do anything useful for STA mode, so setting the VAP M= AC address to anything that isn't ic_macaddr won't affect anything useful. Ok, so what we really need is: * fix up the hint.ath.X.macaddr thing to work right if it doesn't * figure out a generic way to fetch a wifi device mac address, now that 'ifconfig' can't do it; * figure out a generic way to re-program the device MAC address when the fi= rst VAP is created if it has changed, so the first VAP creation can be given an ethernet address and it will actually program the device; or * .. document one way (eg andriy's way, where setting the wlanaddr on the f= irst VAP will program the NIC MAC, and any subsequent creations can only vary depending upon what the hardware will provide) - and then audit /all/ drive= rs to make sure that method works. I think andriy's way is fine, and we just need to document it in the manpage/docbook and then audit every wifi driver. But I'd still like some generic way to fetch ic_macaddr from a device - eg by sysctl, or if we can = do it via an existing device ioctl, that. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Wed Oct 12 20:37:22 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A588BC0FF84 for ; Wed, 12 Oct 2016 20:37:22 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6FBB4316 for ; Wed, 12 Oct 2016 20:37:22 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-it0-x22b.google.com with SMTP id z65so65992562itc.0 for ; Wed, 12 Oct 2016 13:37:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fN6UtLiK5VKnQYmrqqjSibt/FKVEbelGQZjHKIO/QPs=; b=M81uR9FmAzT9b8+o5CnjRNQnMzyWwqlZVq50mIr2mIlWUzHMGraKt28rMlCkUOO2SF 4MP853tYzwy6n3xNI68HhU/EmIZBVXVI4NNRuIiQlSHCiya2P8auOgEH8xbJh37cQe+g IN+c8YunHQi1tiJblmWM6ufD43rOMDPiJNz4zWWH6VT5ib9vhnHWX5yPA3WQJWl1Pn+f He9ogHx0bmMffxNSC5OHwddNM36WmeLKyPvx9bKZJ2Te8W8hS/u56pjLGR+v1/j11/Tg XJnWoR4kf77aMZH+czKb43MoAv3M1H7LeM5eJHF0AEnJy/SIvZ5gG87Q8HrWFuwdfD2+ +WRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fN6UtLiK5VKnQYmrqqjSibt/FKVEbelGQZjHKIO/QPs=; b=TND2rkW+8O419/SfN4WqSm3WAN5jLoZ3Rd8PTdh3HQYSf5Nj6pqlmI8uxK1gFoxtzf y1aIRavZvoPrpqJ/XPOIKp5JJhq+7xvRW8sVICQWYMgU+5MdLkV5Rxt0WKenK1iQwRkl s+HcA/Xr3SM0isXQEne8FXA1HmqAXnfSdkOHi3uzSsh+gpb13xNQsY6e29j2aCoOFlH/ QcejtjWgVJeBSq2bTIa0t/0nDyvYsb1B2hmKccgrbiavt54VhgzM+FiM3zlWbCCzf+EV FZb7P7BeOW/O26jBX4CyTfb0VLgBUpr8uqd6BC+wi2MUTMKWuguSk392o1MNaaSO6Exm ObGQ== X-Gm-Message-State: AA6/9Rl+uLvmejP30Opz9E1mN3aZSNAzISwbQIVjGaKTFTxwuPINA6i461kAnEp6pxUPH1j9IkUYsegMjyigkA== X-Received: by 10.36.127.140 with SMTP id r134mr3299115itc.29.1476304641879; Wed, 12 Oct 2016 13:37:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.141.129 with HTTP; Wed, 12 Oct 2016 13:37:21 -0700 (PDT) In-Reply-To: <20161012213255.585a7278@shibato> References: <20161012171700.5b4f9ea8@shibato> <20161012213255.585a7278@shibato> From: Adrian Chadd Date: Wed, 12 Oct 2016 13:37:21 -0700 Message-ID: Subject: Re: Regression: ethernet + wireless/ath under lagg To: "J.R. Oldroyd" Cc: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Wed, 12 Oct 2016 20:37:22 -0000 On 12 October 2016 at 12:32, J.R. Oldroyd wrote: > On Wed, 12 Oct 2016 09:08:20 -0700 Adrian Chadd wrote: >> >> hiya, >> >> there should be a way to create a vap with a specific mac address upon >> creation time. Sorry, doing lagg+wlan is not something we've been >> collectively using. :( >> >> Thanks, >> >> >> -adrian >> >> > > PR#213207 appears to be discussing this same problem. > > I am truly amazed that this "is not something we've been collectively > using"! Here, we have all of Macs, Windows, Linux for which this > "just works" and it also worked fine (with the config I posted > earlier) on 9.x and 10.x. Your bog-standard, cheapo Linksys/Netgear/ > whatever, bridge their wireless network to their wired ports, and it > is common practice here to be using wireless and then to later plug > into a wired port on those routers and have connections continue > seamlessly. Sure, but the set of wifi developers and set of wifi users is as big as the smallest set, and the set of wifi developers is like what, 3? 4? None of us were bitten by this because I don't think any of the wifi developers (me included) use lagg and failover. > A way of determining the ath's MAC address so it can be used to set > the re's MAC, or a way of setting the ath's MAC address prior to wlan > creation is needed in 11.x. Andriy has proposed one way, which I like. We'd just have to do that method for all wifi drivers, as well as making sure drivers can fail the VAP creation if a MAC is again requested and the device doesn't support it. -a From owner-freebsd-wireless@freebsd.org Thu Oct 13 11:04:15 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AF724C0FD53 for ; Thu, 13 Oct 2016 11:04:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9EA22F80 for ; Thu, 13 Oct 2016 11:04:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9DB4FJH028442 for ; Thu, 13 Oct 2016 11:04:15 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213444] iwn Wi-Fi not working after suspend/resume, after upgrading to 11.0 Date: Thu, 13 Oct 2016 11:04:15 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: maxim.usatov@bcsatellite.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Thu, 13 Oct 2016 11:04:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213444 Bug ID: 213444 Summary: iwn Wi-Fi not working after suspend/resume, after upgrading to 11.0 Product: Base System Version: 11.0-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: wireless Assignee: freebsd-wireless@FreeBSD.org Reporter: maxim.usatov@bcsatellite.net CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org After upgrading to 11.0-RELEASE wlan0 is not working (NO CARRIER) after lap= top is suspended. Can be fixed by adding this to /etc/rc.resume: sleep 5 service netif restart dhclient wlan0=20 It was working fine on 10.2-RELEASE.=20 My laptop is Thinkpad T400, using iwn driver for wireless. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Thu Oct 13 11:30:29 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1A9FFC0E8F3 for ; Thu, 13 Oct 2016 11:30:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 09D18D34 for ; Thu, 13 Oct 2016 11:30:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9DBUSbN085648 for ; Thu, 13 Oct 2016 11:30:28 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213444] iwn Wi-Fi not working after suspend/resume, after upgrading to 11.0 Date: Thu, 13 Oct 2016 11:30:29 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: maxim.usatov@bcsatellite.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Thu, 13 Oct 2016 11:30:29 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213444 --- Comment #1 from Maxim Usatov --- It appears I was too quick with a fix, I apologize. The issue seems to be chaotic. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Thu Oct 13 16:15:47 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C90B3C0FBE2 for ; Thu, 13 Oct 2016 16:15:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B8970EF5 for ; Thu, 13 Oct 2016 16:15:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9DGFlpk016438 for ; Thu, 13 Oct 2016 16:15:47 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213453] ath0 driver complains on Asus EEE PC 1005PE Date: Thu, 13 Oct 2016 16:15:47 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Thu, 13 Oct 2016 16:15:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213453 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-wireless@FreeBSD.or | |g CC|freebsd-i386@FreeBSD.org | --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Thu Oct 13 16:19:02 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B2DFC10023 for ; Thu, 13 Oct 2016 16:19:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0A552686 for ; Thu, 13 Oct 2016 16:19:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9DGJ11B021695 for ; Thu, 13 Oct 2016 16:19:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213444] iwn Wi-Fi not working after suspend/resume, after upgrading to 11.0 Date: Thu, 13 Oct 2016 16:19:01 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Thu, 13 Oct 2016 16:19:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213444 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression CC|freebsd-amd64@FreeBSD.org | --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Thu Oct 13 16:32:58 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 95EAEC10682 for ; Thu, 13 Oct 2016 16:32:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8560218E for ; Thu, 13 Oct 2016 16:32:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9DGWwZY062020 for ; Thu, 13 Oct 2016 16:32:58 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213444] iwn Wi-Fi not working after suspend/resume, after upgrading to 11.0 Date: Thu, 13 Oct 2016 16:32:58 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: avos@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Thu, 13 Oct 2016 16:32:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213444 Andriy Voskoboinyk changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |avos@freebsd.org --- Comment #2 from Andriy Voskoboinyk --- Hi, Can you attach `dmesg` output before suspend/after resume with 'wlandebug -i wlan0 state+auth+assoc' set (before suspend)? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Thu Oct 13 16:33:59 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 834B3C106E4 for ; Thu, 13 Oct 2016 16:33:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5A3601DC for ; Thu, 13 Oct 2016 16:33:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9DGXxau063939 for ; Thu, 13 Oct 2016 16:33:59 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213444] iwn Wi-Fi not working after suspend/resume, after upgrading to 11.0 Date: Thu, 13 Oct 2016 16:33:59 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: david@catwhisker.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Thu, 13 Oct 2016 16:33:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213444 david@catwhisker.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |david@catwhisker.org --- Comment #3 from david@catwhisker.org --- My hardware and experience are both different; whether one has a significant effect on the other, I don't know. Summary: I don't see the problem. More details: Information on my laptop may be found at . As noted there, I field-replaced the Broadcom wireless/Bluetooth card (whi= ch was apparently not supported) with the Intel WiFi Link 5100 that I pulled o= ut of my previous laptop (Dell M4400). Further, I have (also) been tracking head on the same laptop (on a different slice of the boot drive). Once stable/11 was branched, I copied the head slice's / and /usr file systems to a 3rd slice, then used "svn switch" to update that slice's /usr/src from head to stable/11; I have been tracking h= ead, stable/11, and stable/10 daily on the m4800 since. While I have had issues with suspend/resume (e.g., a recent update to x11/nvidia/driver appears to have broken resume for me until I switched from x11/nvidia-driver to x11/nvidia-driver-340), I do not recall ever having an issue with iwn/wlan0 failing to work on resume. (And yes, I do exercise suspend/resume: I suspend the laptop before getting on my bike to get to the shuttle stop, resume once on shuttle (and use wireless to access the Intern= et), then suspend again once we reach work (before I stuff the laptop back in my backpack), then resume again once I'm at my desk.) And for the past 3 weeks or so, I've been running stable/11 on the laptop Monday - Friday. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Thu Oct 13 16:35:23 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5CDBCC10756 for ; Thu, 13 Oct 2016 16:35:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4BC4C24F for ; Thu, 13 Oct 2016 16:35:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9DGZNCe066502 for ; Thu, 13 Oct 2016 16:35:23 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213444] iwn Wi-Fi not working after suspend/resume, after upgrading to 11.0 Date: Thu, 13 Oct 2016 16:35:23 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: avos@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_severity Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Thu, 13 Oct 2016 16:35:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213444 Andriy Voskoboinyk changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Affects Many People |Affects Only Me --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Thu Oct 13 16:38:22 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A5421C10886 for ; Thu, 13 Oct 2016 16:38:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8A3F830B for ; Thu, 13 Oct 2016 16:38:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9DGcMju072145 for ; Thu, 13 Oct 2016 16:38:22 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213456] Problem with iwn firmware on 11-RELEASE Date: Thu, 13 Oct 2016 16:38:22 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: kpect@protonmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Thu, 13 Oct 2016 16:38:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213456 Bug ID: 213456 Summary: Problem with iwn firmware on 11-RELEASE Product: Base System Version: 11.0-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: wireless Assignee: freebsd-wireless@FreeBSD.org Reporter: kpect@protonmail.com CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Hello. After upgrading from 10.3 to 11.0 I've got new problems with my iwn driver = on Lenovo T430. Before 11 I didn't have such issues. $ uname -a FreeBSD KPECT 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0: Tue Oct 11 20:41:= 43 MSK 2016 root@KPECT amd64 wlan0: Ethernet address: a4:4e:31:2a:64:5c iwn0: iwn_read_firmware: ucode rev=3D0x12a80601 wlan0: link state changed to UP wlan0: link state changed to DOWN iwn0: device timeout iwn0: iwn_read_firmware: ucode rev=3D0x12a80601 iwn0: scan timeout iwn0: iwn_read_firmware: ucode rev=3D0x12a80601 wlan0: link state changed to UP Link goes up and down several times before actual authentication which is m= uch longer now. Once I even got following: Oct 12 19:07:57 KPECT kernel: wlan0: Ethernet address: a4:4e:31:2a:64:5c Oct 12 19:07:57 KPECT kernel: iwn0: iwn_read_firmware: ucode rev=3D0x12a806= 01 Oct 12 19:07:57 KPECT kernel: wlan0: link state changed to UP Oct 12 19:07:57 KPECT kernel: iwn0: iwn_intr: fatal firmware error Oct 12 19:07:57 KPECT kernel: firmware error log: Oct 12 19:07:57 KPECT kernel: error type =3D "UNKNOWN" (0x00000038) Oct 12 19:07:57 KPECT kernel: program counter =3D 0x00009918 Oct 12 19:07:57 KPECT kernel: source line =3D 0x000003C4 Oct 12 19:07:57 KPECT kernel: error data =3D 0x0000000000000000 Oct 12 19:07:57 KPECT kernel: branch link =3D 0x0000991400009914 Oct 12 19:07:57 KPECT kernel: interrupt link =3D 0x0000D6BE00000000 Oct 12 19:07:57 KPECT kernel: time =3D 7449 Oct 12 19:07:57 KPECT kernel: driver status: Oct 12 19:07:57 KPECT kernel: tx ring 0: qid=3D0 cur=3D0 queued=3D0=20= =20 Oct 12 19:07:57 KPECT kernel: tx ring 1: qid=3D1 cur=3D0 queued=3D0=20= =20 Oct 12 19:07:57 KPECT kernel: tx ring 2: qid=3D2 cur=3D0 queued=3D0=20= =20 Oct 12 19:07:57 KPECT kernel: tx ring 3: qid=3D3 cur=3D2 queued=3D0=20= =20 Oct 12 19:07:57 KPECT kernel: tx ring 4: qid=3D4 cur=3D0 queued=3D0=20= =20 Oct 12 19:07:57 KPECT kernel: tx ring 5: qid=3D5 cur=3D0 queued=3D0=20= =20 Oct 12 19:07:57 KPECT kernel: tx ring 6: qid=3D6 cur=3D0 queued=3D0=20= =20 Oct 12 19:07:57 KPECT kernel: tx ring 7: qid=3D7 cur=3D0 queued=3D0=20= =20 Oct 12 19:07:57 KPECT kernel: tx ring 8: qid=3D8 cur=3D0 queued=3D0=20= =20 Oct 12 19:07:57 KPECT kernel: tx ring 9: qid=3D9 cur=3D83 queued=3D0=20= =20 Oct 12 19:07:57 KPECT kernel: tx ring 10: qid=3D10 cur=3D0 queued=3D0=20= =20 Oct 12 19:07:57 KPECT kernel: tx ring 11: qid=3D11 cur=3D0 queued=3D0=20= =20 Oct 12 19:07:57 KPECT kernel: tx ring 12: qid=3D12 cur=3D0 queued=3D0=20= =20 Oct 12 19:07:57 KPECT kernel: tx ring 13: qid=3D13 cur=3D0 queued=3D0=20= =20 Oct 12 19:07:57 KPECT kernel: tx ring 14: qid=3D14 cur=3D0 queued=3D0=20= =20 Oct 12 19:07:57 KPECT kernel: tx ring 15: qid=3D15 cur=3D0 queued=3D0=20= =20 Oct 12 19:07:57 KPECT kernel: tx ring 16: qid=3D16 cur=3D0 queued=3D0=20= =20 Oct 12 19:07:57 KPECT kernel: tx ring 17: qid=3D17 cur=3D0 queued=3D0=20= =20 Oct 12 19:07:57 KPECT kernel: tx ring 18: qid=3D18 cur=3D0 queued=3D0=20= =20 Oct 12 19:07:57 KPECT kernel: tx ring 19: qid=3D19 cur=3D0 queued=3D0=20= =20 Oct 12 19:07:57 KPECT kernel: rx ring: cur=3D5 Oct 12 19:07:57 KPECT kernel: iwn0: iwn_panicked: controller panicked, iv_s= tate =3D 5; restarting Oct 12 19:07:57 KPECT kernel: wlan0: link state changed to DOWN Oct 12 19:07:57 KPECT kernel: iwn0: iwn_read_firmware: ucode rev=3D0x12a806= 01 Oct 12 19:07:57 KPECT kernel: wlan0: link state changed to UP Oct 12 19:07:57 KPECT kernel: wlan0: link state changed to DOWN Oct 12 19:07:57 KPECT kernel: iwn0: device timeout Oct 12 19:07:57 KPECT kernel: iwn0: iwn_read_firmware: ucode rev=3D0x12a806= 01 Oct 12 19:07:57 KPECT kernel: iwn0: scan timeout Oct 12 19:07:57 KPECT kernel: iwn0: iwn_read_firmware: ucode rev=3D0x12a806= 01 Oct 12 19:07:57 KPECT kernel: wlan0: link state changed to UP Regards, Sergey. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Thu Oct 13 16:39:51 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 48649C108F5 for ; Thu, 13 Oct 2016 16:39:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 380BE3D6 for ; Thu, 13 Oct 2016 16:39:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9DGdoA7074963 for ; Thu, 13 Oct 2016 16:39:51 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213456] Problem with iwn firmware on 11-RELEASE Date: Thu, 13 Oct 2016 16:39:51 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: kpect@protonmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Thu, 13 Oct 2016 16:39:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213456 --- Comment #1 from Sergey --- the firmware is compiled into kernel $ kldstat -v |grep iwn 54 pci/iwn 55 iwn6000g2afw_fw --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Thu Oct 13 16:54:55 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 72E9CC10DED for ; Thu, 13 Oct 2016 16:54:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6293FBD for ; Thu, 13 Oct 2016 16:54:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9DGst66017608 for ; Thu, 13 Oct 2016 16:54:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213456] Problem with iwn firmware on 11-RELEASE Date: Thu, 13 Oct 2016 16:54:55 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Thu, 13 Oct 2016 16:54:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213456 Adrian Chadd changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adrian@freebsd.org --- Comment #2 from Adrian Chadd --- Is it associating as an 11n station now? that may be triggering issues. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Thu Oct 13 17:39:47 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C4775C10B8E for ; Thu, 13 Oct 2016 17:39:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B3EAACE9 for ; Thu, 13 Oct 2016 17:39:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9DHdkLH066372 for ; Thu, 13 Oct 2016 17:39:47 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213456] Problem with iwn firmware on 11-RELEASE Date: Thu, 13 Oct 2016 17:39:47 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jrm@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Thu, 13 Oct 2016 17:39:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213456 Joseph Mingrone changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jrm@freebsd.org --- Comment #3 from Joseph Mingrone --- I've also seen it take longer to establish a connection after upgrading to = 11.=20 This is on a Lenovo X220 and a T530. We have switched to the 5 GHz band at home, but I recall testing with all things the same as before the upgrade and still seeing the problem. Once the connection is established it is stable [1]. Here is partial output from /var/run/dmesg.boot on the T530: iwn0: mem 0xf1c00000-0xf1c01fff irq 17 at device 0.0 on pci2 ... iwn0: iwn_read_firmware: ucode rev=3D0x12a80601 wlan0: link state changed to UP wlan0: link state changed to DOWN iwn0: scan timeout iwn0: iwn_read_firmware: ucode rev=3D0x12a80601 wlan0: link state changed to UP iwn0: iwn_intr: fatal firmware error firmware error log: error type =3D "UNKNOWN" (0x00000038) program counter =3D 0x00009918 source line =3D 0x000003C4 error data =3D 0x0000000000000000 branch link =3D 0x0000991400009914 interrupt link =3D 0x0000D6BE00000000 time =3D 3538 driver status: tx ring 0: qid=3D0 cur=3D0 queued=3D0=20=20 tx ring 1: qid=3D1 cur=3D0 queued=3D0=20=20 tx ring 2: qid=3D2 cur=3D0 queued=3D0=20=20 tx ring 3: qid=3D3 cur=3D2 queued=3D0=20=20 tx ring 4: qid=3D4 cur=3D0 queued=3D0=20=20 tx ring 5: qid=3D5 cur=3D0 queued=3D0=20=20 tx ring 6: qid=3D6 cur=3D0 queued=3D0=20=20 tx ring 7: qid=3D7 cur=3D0 queued=3D0=20=20 tx ring 8: qid=3D8 cur=3D0 queued=3D0=20=20 tx ring 9: qid=3D9 cur=3D66 queued=3D0=20=20 tx ring 10: qid=3D10 cur=3D0 queued=3D0=20=20 tx ring 11: qid=3D11 cur=3D0 queued=3D0=20=20 tx ring 12: qid=3D12 cur=3D0 queued=3D0=20=20 tx ring 13: qid=3D13 cur=3D0 queued=3D0=20=20 tx ring 14: qid=3D14 cur=3D0 queued=3D0=20=20 tx ring 15: qid=3D15 cur=3D0 queued=3D0=20=20 tx ring 16: qid=3D16 cur=3D0 queued=3D0=20=20 tx ring 17: qid=3D17 cur=3D0 queued=3D0=20=20 tx ring 18: qid=3D18 cur=3D0 queued=3D0=20=20 tx ring 19: qid=3D19 cur=3D0 queued=3D0=20=20 rx ring: cur=3D46 iwn0: iwn_panicked: controller panicked, iv_state =3D 5; restarting wlan0: link state changed to DOWN iwn0: iwn_read_firmware: ucode rev=3D0x12a80601 wlan0: link state changed to UP iwn0: iwn_intr: fatal firmware error firmware error log: error type =3D "UNKNOWN" (0x00000038) program counter =3D 0x00009918 source line =3D 0x000003C4 error data =3D 0x0000000000000000 branch link =3D 0x0000991400009914 interrupt link =3D 0x0000D6BE00000000 time =3D 27953 driver status: tx ring 0: qid=3D0 cur=3D0 queued=3D0=20=20 tx ring 1: qid=3D1 cur=3D0 queued=3D0=20=20 tx ring 2: qid=3D2 cur=3D0 queued=3D0=20=20 tx ring 3: qid=3D3 cur=3D3 queued=3D0=20=20 tx ring 4: qid=3D4 cur=3D0 queued=3D0=20=20 tx ring 5: qid=3D5 cur=3D0 queued=3D0=20=20 tx ring 6: qid=3D6 cur=3D0 queued=3D0=20=20 tx ring 7: qid=3D7 cur=3D0 queued=3D0=20=20 tx ring 8: qid=3D8 cur=3D0 queued=3D0=20=20 tx ring 9: qid=3D9 cur=3D92 queued=3D0=20=20 tx ring 10: qid=3D10 cur=3D0 queued=3D0=20=20 tx ring 11: qid=3D11 cur=3D0 queued=3D0=20=20 tx ring 12: qid=3D12 cur=3D0 queued=3D0=20=20 tx ring 13: qid=3D13 cur=3D0 queued=3D0=20=20 tx ring 14: qid=3D14 cur=3D0 queued=3D0=20=20 tx ring 15: qid=3D15 cur=3D0 queued=3D0=20=20 tx ring 16: qid=3D16 cur=3D0 queued=3D0=20=20 tx ring 17: qid=3D17 cur=3D0 queued=3D0=20=20 tx ring 18: qid=3D18 cur=3D0 queued=3D0=20=20 tx ring 19: qid=3D19 cur=3D0 queued=3D0=20=20 rx ring: cur=3D33 iwn0: iwn_panicked: controller panicked, iv_state =3D 5; restarting wlan0: link state changed to DOWN iwn0: iwn_read_firmware: ucode rev=3D0x12a80601 wlan0: link state changed to UP Here is partial output from ifconfig (home network): wlan0: flags=3D8843 metric 0 mtu 15= 00 ether 84:3a:xx:xx:xx:xx inet 192.168.2.5 netmask 0xffffff00 broadcast 192.168.2.255 nd6 options=3D29 media: IEEE 802.11 Wireless Ethernet MCS mode 11na status: associated ssid trp-5 channel 157 (5785 MHz 11a ht/40+) bssid 4c:xx:xx:xx:xx:xx regdomain FCC country US authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 2:128-bit txpower 23 bmiss 10 mcastrate 6 mgmtrate 6 scanvalid 60 ampdulimit 64k ampdudensity 4 -amsdutx amsd= urx shortgi -stbc wme roaming MANUAL groups: wlan [1] As an aside, at work, the wireless network uses WPA-EAP. Before 11, = the connection would drop so often it was not usable, but things seem to have greatly improved in 11. Thanks! Partial ifconfig output (work): wlan0: flags=3D8843 metric 0 mtu 15= 00 ether 8c:xx:xx:xx:xx:xx inet 134.xxx.xxx.xxx netmask 0xfffffe00 broadcast 134.xxx.xxx.255 nd6 options=3D29 media: IEEE 802.11 Wireless Ethernet MCS mode 11ng status: associated ssid Dal-WPA2 channel 11 (2462 MHz 11g ht/20) bssid 00:xx:xx:xx:xx:= xx regdomain FCC country US authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi -stbc wme roaming MANUAL groups: wlan /etc/wpa_supplicant.conf (work): network=3D{ ssid=3D"Dal-WPA2" key_mgmt=3DWPA-EAP pairwise=3DCCMP group=3DCCMP TKIP eap=3DPEAP ca_cert=3D"/usr/local/share/certs/ca-root-nss.crt" identity=3D"xxx" subject_match=3D"network-authentication.dal.ca" #phase1=3D"peaplabel=3D0" phase2=3D"auth=3DMSCHAPV2" password=3D"xxx" } --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Thu Oct 13 18:29:10 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 16013C108D8 for ; Thu, 13 Oct 2016 18:29:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0515FB03 for ; Thu, 13 Oct 2016 18:29:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9DIT9Ca033981 for ; Thu, 13 Oct 2016 18:29:09 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213444] iwn Wi-Fi not working after suspend/resume, after upgrading to 11.0 Date: Thu, 13 Oct 2016 18:29:10 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: maxim.usatov@bcsatellite.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Thu, 13 Oct 2016 18:29:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213444 --- Comment #4 from Maxim Usatov --- Dobry den, Andriy,=20 My FreeBSD installation is totally broken after the upgrade to 11. My chrom= ium segfaults when I try to attach files here, and firefox won't start because = it complains on an undefined symbol in libgiofam (thunderbird and any other gtk based stuff won't start as well, and yes, I did full pkg upgrade -f).=20=20 It appears I will need to spend some time fixing that until I can attach fi= les here.=20 By the way, this time suspend/resume worked fine for probably 8 times in a = row, however, each time it took progressively longer to associate. However, my laptop was unable to associate after reboot. I've had to do "service netif restart" manually after the boot to get it online.=20=20 Max --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Fri Oct 14 00:03:43 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D222EC10F8D; Fri, 14 Oct 2016 00:03:43 +0000 (UTC) (envelope-from andriyvos@gmail.com) Received: from mail-lf0-f43.google.com (mail-lf0-f43.google.com [209.85.215.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5621E102; Fri, 14 Oct 2016 00:03:43 +0000 (UTC) (envelope-from andriyvos@gmail.com) Received: by mail-lf0-f43.google.com with SMTP id l131so122931137lfl.2; Thu, 13 Oct 2016 17:03:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:cc:subject:references:date:mime-version :content-transfer-encoding:from:message-id:in-reply-to:user-agent; bh=58L+1HH41zDqvyFWoQdPw+IatCq9LLZfoKOwmoBNIQA=; b=l36fS3WAHmNvCjdSbbU7QE4iAV/2ZRqDcts8QhQYzsapJLQoZ3bBYML8WnRYVQSuMJ KLOl9uP5h+Tmkul2xn8Iaa7Etir3IUsr7ftxFLhg2VQNT/8///Fy6DDEX0xY/X8OM3Qo lzaML6X8G1k+sDU17hD9QjSC17WblcTxZiKpvDfI/BktCbq0cT4RvutqcDpoEp6DKe7/ nuEqBXHf4KvZqvOp7bkf2kLNLOfkD8KZFVRcp5PD8qpkqKmaxTuEF0+V9uDjrs0WKdxP ZwshWM5FtL5aaLI5IuHuHjLkaBDnvFYE/JbmxZs2IbhiJcjFl+VVTTNbUx/ELG0pJVaA tn1g== X-Gm-Message-State: AA6/9RnssaczCc/6600OEj0AdmbLiEiIu9IBBThkRfsYoGT16QvcgfiXi/KCFSQbOASDaw== X-Received: by 10.25.132.18 with SMTP id g18mr285954lfd.7.1476403420659; Thu, 13 Oct 2016 17:03:40 -0700 (PDT) Received: from localhost (host-176-37-109-22.la.net.ua. [176.37.109.22]) by smtp.gmail.com with ESMTPSA id g5sm4399045lfe.14.2016.10.13.17.03.39 (version=TLS1 cipher=AES128-SHA bits=128/128); Thu, 13 Oct 2016 17:03:40 -0700 (PDT) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Kevin Lo" Cc: "freebsd-wireless@freebsd.org" , "freebsd-current@freebsd.org" , "Adrian Chadd" Subject: Re: urtwn(4) / rtwn(4) drivers are merged - call for review / testing References: <20160923015840.GA77979@ns.kevlo.org> <20160923071830.GA79146@ns.kevlo.org> <20161001150924.GA48641@ns.kevlo.org> <20161003005523.GA57437@ns.kevlo.org> <20161011012702.GA36712@ns.kevlo.org> <20161012043415.GA45653@ns.kevlo.org> Date: Fri, 14 Oct 2016 03:03:41 +0300 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Andriy Voskoboinyk" Message-ID: In-Reply-To: <20161012043415.GA45653@ns.kevlo.org> User-Agent: Opera Mail/12.16 (FreeBSD) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Fri, 14 Oct 2016 00:03:44 -0000 Wed, 12 Oct 2016 07:34:15 +0300 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0=D0= =BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Kevin Lo : Thanks for testing! (I have got another one to simplify the process) Can you approve that current tree (master) works without any (new) = problems? P.S. Known issue (present in the current driver too): - the card ACKs only some frames that were sent using CCK rates (whilst sees all retransmissions - that can be seen in 'rx discard 'cuz = = dup' counter via wlanstats) > I tried to use https://github.com/s3erios/rtwn/tree/pci_modified, > still no luck. BTW, there's a compilation error: = > http://pastebin.com/hCFfYVSj > > To ensure that the adapter is not faulty, I tested with the snapshots = = > image > (FreeBSD-12.0-CURRENT-amd64-20160829-r305028-memstick.img), rtwn(4) = > works fine. > > Kevin > > On Tue, Oct 11, 2016 at 11:21:24PM +0300, Andriy Voskoboinyk wrote: >> >> Tue, 11 Oct 2016 04:27:02 +0300 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0= =D0=BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Kevin Lo = >> : >> >> I have created 'pci_modified' branch to speed-up the process (RTL881*= AU >> will >> not work with it for now); right now it contains (mostly) unmodified >> initialization path from rtwn(4) driver. >> >> If this version will work, I will revert some 'RTWN_PCI_WORKAROUND' >> temporary blocks until the culprit is found. >> >> > On Sat, Oct 08, 2016 at 02:18:54AM +0300, Andriy Voskoboinyk wrote:= >> >> >> >> Mon, 03 Oct 2016 03:55:23 +0300 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0= =B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Kevin Lo >> >> : >> >> >> >> Hi! >> > >> > Hi Andriy, >> > >> >> Can you refresh the tree and retest it (dev.rtwn.0.debug=3D0x829f)= ? >> > >> > I refreshed the tree and retested it, unfortunately it's still the = = >> same. >> > Here's the log: https://people.freebsd.org/~kevlo/rtl8188ce-debuglo= g >> >> >> >> P.S. If Rx is still broken (status is always 0) try to execute >> >> 'ifconfig wlan0 promisc' >> > >> > It doesn't help either :( >> From owner-freebsd-wireless@freebsd.org Fri Oct 14 01:59:06 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7676AC10B59; Fri, 14 Oct 2016 01:59:06 +0000 (UTC) (envelope-from kevlo@ns.kevlo.org) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D6510D8A; Fri, 14 Oct 2016 01:59:05 +0000 (UTC) (envelope-from kevlo@ns.kevlo.org) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.15.2/8.15.2) with ESMTPS id u9E1vnEx069346 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 14 Oct 2016 09:57:49 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.15.2/8.15.2/Submit) id u9E1vmZg069345; Fri, 14 Oct 2016 09:57:49 +0800 (CST) (envelope-from kevlo) Date: Fri, 14 Oct 2016 09:57:48 +0800 From: Kevin Lo To: Andriy Voskoboinyk Cc: "freebsd-wireless@freebsd.org" , "freebsd-current@freebsd.org" , Adrian Chadd Subject: Re: urtwn(4) / rtwn(4) drivers are merged - call for review / testing Message-ID: <20161014015748.GA69328@ns.kevlo.org> References: <20160923071830.GA79146@ns.kevlo.org> <20161001150924.GA48641@ns.kevlo.org> <20161003005523.GA57437@ns.kevlo.org> <20161011012702.GA36712@ns.kevlo.org> <20161012043415.GA45653@ns.kevlo.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Fri, 14 Oct 2016 01:59:06 -0000 On Fri, Oct 14, 2016 at 03:03:41AM +0300, Andriy Voskoboinyk wrote: > > Wed, 12 Oct 2016 07:34:15 +0300 було написано Kevin Lo : > > Thanks for testing! (I have got another one to simplify the process) > Can you approve that current tree (master) works without any (new) > problems? Sure. For usb wireless adapters, they work quite well :) Thanks. > P.S. Known issue (present in the current driver too): > - the card ACKs only some frames that were sent using CCK rates > (whilst sees all retransmissions - that can be seen in 'rx discard 'cuz > dup' > counter via wlanstats) > > > I tried to use https://github.com/s3erios/rtwn/tree/pci_modified, > > still no luck. BTW, there's a compilation error: > > http://pastebin.com/hCFfYVSj > > > > To ensure that the adapter is not faulty, I tested with the snapshots > > image > > (FreeBSD-12.0-CURRENT-amd64-20160829-r305028-memstick.img), rtwn(4) > > works fine. > > > > Kevin > > > > On Tue, Oct 11, 2016 at 11:21:24PM +0300, Andriy Voskoboinyk wrote: > >> > >> Tue, 11 Oct 2016 04:27:02 +0300 було написано Kevin Lo > >> : > >> > >> I have created 'pci_modified' branch to speed-up the process (RTL881*AU > >> will > >> not work with it for now); right now it contains (mostly) unmodified > >> initialization path from rtwn(4) driver. > >> > >> If this version will work, I will revert some 'RTWN_PCI_WORKAROUND' > >> temporary blocks until the culprit is found. > >> > >> > On Sat, Oct 08, 2016 at 02:18:54AM +0300, Andriy Voskoboinyk wrote: > >> >> > >> >> Mon, 03 Oct 2016 03:55:23 +0300 було написано Kevin Lo > >> >> : > >> >> > >> >> Hi! > >> > > >> > Hi Andriy, > >> > > >> >> Can you refresh the tree and retest it (dev.rtwn.0.debug=0x829f) ? > >> > > >> > I refreshed the tree and retested it, unfortunately it's still the > >> same. > >> > Here's the log: https://people.freebsd.org/~kevlo/rtl8188ce-debuglog > >> >> > >> >> P.S. If Rx is still broken (status is always 0) try to execute > >> >> 'ifconfig wlan0 promisc' > >> > > >> > It doesn't help either :( > >> > > From owner-freebsd-wireless@freebsd.org Fri Oct 14 07:06:46 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 446A8C11FEE for ; Fri, 14 Oct 2016 07:06:46 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 31D0D677 for ; Fri, 14 Oct 2016 07:06:45 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yuri.doctorlan.com (c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id u9E76io7022615 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 14 Oct 2016 00:06:44 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190] claimed to be yuri.doctorlan.com Subject: Re: What is the best choice of USB WiFi adapter working on FreeBSD? To: freebsd-wireless References: <96108220-fc4f-8c71-8df1-c683aa8d2406@rawbw.com> From: Yuri Message-ID: <12de97c8-3d81-2142-f759-bdd6654a709e@rawbw.com> Date: Fri, 14 Oct 2016 00:06:43 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <96108220-fc4f-8c71-8df1-c683aa8d2406@rawbw.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Fri, 14 Oct 2016 07:06:46 -0000 On 10/08/2016 23:25, Yuri wrote: > I have Belkin F5D7050 USB WiFI NIC, but zyd driver is faulty and the > card freezes up with the timeout message: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=138292. > > > Can anybody recommend the USB NIC that works well on FreeBSD, is > inexpensive and easily available? Thanks to everybody who recommended USB WiFi cards. I got TP-LINK TL-WDN3200 and it works very well. I think there is a value in having a list of well supported USB WiFi cards. Maybe it makes sense to add such section into the handbook (here https://www.freebsd.org/doc/handbook/network-wireless.html)? For example, create the section "Well-supported devices". Yuri From owner-freebsd-wireless@freebsd.org Fri Oct 14 08:52:56 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 21579C10D5C for ; Fri, 14 Oct 2016 08:52:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 10A3CA6D for ; Fri, 14 Oct 2016 08:52:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9E8qtk7073618 for ; Fri, 14 Oct 2016 08:52:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213456] Problem with iwn firmware on 11-RELEASE Date: Fri, 14 Oct 2016 08:52:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: kpect@protonmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Fri, 14 Oct 2016 08:52:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213456 --- Comment #4 from Sergey --- (In reply to Adrian Chadd from comment #2) Yes it associates as 11n, but it did the same before, on 10.3 without any issues and had good wireless speed. It works as 11n on 11.0 also, but the problem is during the initialization + that 'fatal firmware error'. P.S. the chip is Intel Centrino Advanced-N 6205 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Fri Oct 14 10:01:08 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3076AC0F843 for ; Fri, 14 Oct 2016 10:01:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 20207AB0 for ; Fri, 14 Oct 2016 10:01:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9EA162g075616 for ; Fri, 14 Oct 2016 10:01:08 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213456] Problem with iwn firmware on 11-RELEASE Date: Fri, 14 Oct 2016 10:01:07 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: vbotka@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Fri, 14 Oct 2016 10:01:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213456 Vladimir Botka changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vbotka@gmail.com --- Comment #5 from Vladimir Botka --- Hello! FWIW. Let me share my experience with 6205 in Linux. 1) If there is too many APs arround (~30) the driver doesn't connect. In th= is case it was worth to try and configure wpa_supplicant with: ap_scan=3D0 and limit the scanning for specific SSID scan_freq=3D 2) Disabling fast re-authentication sometimes helped to stop dropping WPA-E= AP. fast_reauth=3D0 I have no 6205 in FreeBSD box atm. Sorry. HTH, Cheers, -vlado --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Fri Oct 14 19:42:37 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3C2A9C11504 for ; Fri, 14 Oct 2016 19:42:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2BA48F96 for ; Fri, 14 Oct 2016 19:42:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9EJgad1084888 for ; Fri, 14 Oct 2016 19:42:37 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213207] ath: Unable to set device MAC in FreeBSD 11 Date: Fri, 14 Oct 2016 19:42:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: fbsd@opal.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Fri, 14 Oct 2016 19:42:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213207 --- Comment #12 from fbsd@opal.com --- I could not get Andriy's patch to work. /etc/rc.conf was: ifconfig_re0=3D"up" ether_re0=3D"`ifconfig re0 ether`" wlans_ath0=3Dwlan0 create_args_wlan0=3D"wlanaddr ${ether_re0##*ether } regdomain FCC country U= S" ifconfig_wlan0=3D"WPA" cloned_interfaces=3D"lagg0" ifconfig_lagg0=3D"laggproto failover laggport re0 laggport wlan0 DHCP" # = WAN_IF ifconfig_lagg0_ipv6=3D"inet6 accept_rtadv" It does show the wlan being created with the re's MAC address (both in dmesg and in subsequent "ifconfig wlan0" output). However, the WPA AUTH is still failing: Oct 14 21:09:36 shibato wpa_supplicant[411]: wlan0: CTRL-EVENT-SSID-REENABL= ED id=3D39 ssid=3D"xxx" Oct 14 21:09:36 shibato wpa_supplicant[411]: wlan0: Trying to associate with 00:26:f2:11:22:33 (SSID=3D'xxx' freq=3D2412 MHz) Oct 14 21:09:46 shibato wpa_supplicant[411]: wlan0: Authentication with 00:26:f2:11:22:33 timed out. Oct 14 21:09:46 shibato wpa_supplicant[411]: wlan0: CTRL-EVENT-DISCONNECTED bssid=3D00:26:f2:11:22:33 reason=3D3 locally_generated=3D1 Oct 14 21:09:46 shibato wpa_supplicant[411]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=3D39 ssid=3D"xxx" auth_failures=3D17 durat= ion=3D120 reason=3DCONN_FAILED --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Fri Oct 14 20:12:23 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CA056C11FEF for ; Fri, 14 Oct 2016 20:12:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B9C9763B for ; Fri, 14 Oct 2016 20:12:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9EKCMRI087539 for ; Fri, 14 Oct 2016 20:12:23 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213456] Problem with iwn firmware on 11-RELEASE Date: Fri, 14 Oct 2016 20:12:23 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: kpect@protonmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Fri, 14 Oct 2016 20:12:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213456 --- Comment #6 from Sergey --- Hi Guys. Had following line in rc.conf: ifconfig_wlan0=3D"WPA DHCP mtu 1480 county RU -bgscan ssid MYSSID" (which w= orks perfectly on my desktop with ath0) changing it to ifconfig_wlan0=3D"WPA DHCP mtu 1480 channel 9 -bgscan ssid MYSSID" seems resolved the issue :) Setting channel number explicitly accelerates raising the interface a bit. Thanx all for comments, closing the ticket. Regards, Sergey. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Fri Oct 14 20:12:54 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3B87EC12036 for ; Fri, 14 Oct 2016 20:12:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2AD546D1 for ; Fri, 14 Oct 2016 20:12:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9EKCr9w088710 for ; Fri, 14 Oct 2016 20:12:54 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213456] Problem with iwn firmware on 11-RELEASE Date: Fri, 14 Oct 2016 20:12:54 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: kpect@protonmail.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Fri, 14 Oct 2016 20:12:54 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213456 Sergey changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|New |Closed --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Fri Oct 14 22:43:01 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DCEAAC12299 for ; Fri, 14 Oct 2016 22:43:01 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id B4452D81 for ; Fri, 14 Oct 2016 22:43:01 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yuri.doctorlan.com (c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id u9EMgtHH040575 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 14 Oct 2016 15:42:55 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190] claimed to be yuri.doctorlan.com Subject: Re: What is the best choice of USB WiFi adapter working on FreeBSD? To: freebsd-wireless References: <96108220-fc4f-8c71-8df1-c683aa8d2406@rawbw.com> From: Yuri Message-ID: <045f4f3d-c848-cc4d-1ba4-eb439d0fabad@rawbw.com> Date: Fri, 14 Oct 2016 15:42:53 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <96108220-fc4f-8c71-8df1-c683aa8d2406@rawbw.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Fri, 14 Oct 2016 22:43:02 -0000 I am trying to compile the list of USB Wi-Fi cards that are well supported to add such section to the handbook. Anybody knows other cards that work well besides RT5370 USB dongles and TP-LINK TL-WDN3200? Thank you, Yuri From owner-freebsd-wireless@freebsd.org Fri Oct 14 23:21:29 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A6922C12AC9 for ; Fri, 14 Oct 2016 23:21:29 +0000 (UTC) (envelope-from gobble.wa@gmail.com) Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 62607CDF for ; Fri, 14 Oct 2016 23:21:29 +0000 (UTC) (envelope-from gobble.wa@gmail.com) Received: by mail-qk0-x229.google.com with SMTP id f128so160267370qkb.1 for ; Fri, 14 Oct 2016 16:21:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=v4g/VMgbMHQhxzYuRTTsHZIEhuTnuM5Dxv1jpuijvWM=; b=aGR2FyPzlsv6TZ9tW9FM7eEDr7X8JqE/OiEOrQGl8Fww2ju8CdiEHuof2dTlWSkzTW BGa73Qh+N+Ui4YIHMG0IaX+cgExUJAr9EDuwuXih8WNoRmU6P0xPZeZh/YfDPp/8UBEr 7P9H2tXopjX/A5hVA5VXNGl706flaXGXq7Af3NM7oKWzriXqG6ykR2VPpCvW6PtB6rqU qSKmTJRbsXM/Z6jZ3ZkeC+stnVPFarj3Mnd2vayPsGr6YhPBRQxbeH5QxM14PAVQ4zxp s8ETGZfC8x4bdVlXAj4DPztcT115TFJpQ2HYfmmErSZAWS2D99cLP2hXiiNIHm2HfzMM /0DA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=v4g/VMgbMHQhxzYuRTTsHZIEhuTnuM5Dxv1jpuijvWM=; b=lHTGIAQTCw75DHvuTgcveQh5iMM6REzV1Xgi7pJ6FR/VGGVBmyaX6DSQcYtouYrcjM vqC5ZQ+KWIhtne1zX2f5L1Yw+ibH2Mbkle7pUSIB55KkX5CVrabyUNCEOStqToFbOeRv lGi1sbt3r0gGiZtvbodp7OHxzeAdvKuzmd1aUdeDNKGeJUkrPbPlR6JD/JiXsKGPTOdq FdtkGXFypNqWISQ2A90NlQlNJ29IDTvJkNpdYJuzD4SnOM/XII/AFkP1QtuwjGDKwlEP lPeyfcSsPQgLJIKjlacjBOGyU7qwlY6gG0w62jYBKUvF6ECJ6MOO74pyP2NwJRMdRbYp dzcw== X-Gm-Message-State: AA6/9RmwgCWFqcRd6Hw38H9k+WS15xiWYrXNgrVREl29cNXA/MbsjrxJcjp2ntKzlScH04D0Y/aTE+Q94pv4Mg== X-Received: by 10.55.72.209 with SMTP id v200mr13355062qka.262.1476487288443; Fri, 14 Oct 2016 16:21:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.200.34.142 with HTTP; Fri, 14 Oct 2016 16:21:27 -0700 (PDT) In-Reply-To: <045f4f3d-c848-cc4d-1ba4-eb439d0fabad@rawbw.com> References: <96108220-fc4f-8c71-8df1-c683aa8d2406@rawbw.com> <045f4f3d-c848-cc4d-1ba4-eb439d0fabad@rawbw.com> From: Waitman Gobble Date: Fri, 14 Oct 2016 16:21:27 -0700 Message-ID: Subject: Re: What is the best choice of USB WiFi adapter working on FreeBSD? To: freebsd-wireless Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Fri, 14 Oct 2016 23:21:29 -0000 On Fri, Oct 14, 2016 at 3:42 PM, Yuri wrote: > I am trying to compile the list of USB Wi-Fi cards that are well supported > to add such section to the handbook. > Anybody knows other cards that work well besides RT5370 USB dongles and > TP-LINK TL-WDN3200? > > Thank you, > > Yuri > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" If compiling a list, please consider listing if card supports hostap mode, AFAIK the RT5370 is the only one. -- Waitman Gobble Los Altos California USA 650-900-8557 From owner-freebsd-wireless@freebsd.org Fri Oct 14 23:26:08 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C6F24C12BF0 for ; Fri, 14 Oct 2016 23:26:08 +0000 (UTC) (envelope-from s3erios@gmail.com) Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 433DAEF6 for ; Fri, 14 Oct 2016 23:26:08 +0000 (UTC) (envelope-from s3erios@gmail.com) Received: by mail-lf0-x231.google.com with SMTP id l131so166102635lfl.2 for ; Fri, 14 Oct 2016 16:26:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=to:subject:references:date:cc:mime-version :content-transfer-encoding:from:message-id:in-reply-to:user-agent; bh=zWTfcwf8WIlD9ruiQ3T+dnzeI8f9VRSAGHx/V6mtmUk=; b=Zb1jTPAIxNqmQGqfG9qbxdL5omU2eMQL/WapNLXXYT2ApfbaGtfd0srC5NpKeZkR+l YpqCT7Tt+x+cfUTKxzwYzVfuhQQ9hdEUhqYrGtwwemCPniUaKyAEU0Rz+S1tMHBFnYZP 6fOARqMnyDkmDVGd1OODs+eiHUCbII8iMRNfGypwYRlCa1x9OoTqBD+tKAIj7A/SVtI1 E6Dc8DcIqt+EQ3PA4uWsw1T5j1plYksihnIMBNrglp18T1zUgkd/cG4FoHZDLl7VRwY/ YtBcp6kUWbfBxKz9ea+p6EdtCN2/ygEs4Wts20h6e4qIcaNZgD0Dy5P89QNDjWLxmpCb UDaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:subject:references:date:cc:mime-version :content-transfer-encoding:from:message-id:in-reply-to:user-agent; bh=zWTfcwf8WIlD9ruiQ3T+dnzeI8f9VRSAGHx/V6mtmUk=; b=fqaR2ay4/MJ+7TBf4NhZ1DU4pg273mPgea+5jFfMnubDh3wTzgcywFYGsN48h80ufz GSyBJT+lYmlmnLR4bvwWo048m4m8CgP+HBtQq2KZZBNimj+yLIrbYlQ5onW5JzFCQUEW DMqkrFQpfA9JR0yl4cufd+3ZvznEHV5wgB109EQJerEtc8fXvqWTKOOgWYTOqqGUVTGq C947sfl7I7S4xsOmZPY9ut+MKceevUp7oDYmYIROtF8FB749dKsfUfSi5DSZuSenI+vg HOzYQ8i9Peq4PHk7AFcOkvXnu1eUfpRvBBJ4BLKmDFMRs6w+/eVp+MiWloYOQgv5k3ov y6Xg== X-Gm-Message-State: AA6/9RkdFxb3X8uOSZ/wOaM1U7rUx3I9BhG5pTJ6VnbRoCOvJ3EQU0D/Z1swE0AbFtkvYA== X-Received: by 10.25.125.4 with SMTP id y4mr4923655lfc.75.1476487566349; Fri, 14 Oct 2016 16:26:06 -0700 (PDT) Received: from localhost (host-176-37-109-22.la.net.ua. [176.37.109.22]) by smtp.gmail.com with ESMTPSA id f198sm5602633lfe.10.2016.10.14.16.26.05 (version=TLS1 cipher=AES128-SHA bits=128/128); Fri, 14 Oct 2016 16:26:05 -0700 (PDT) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: Yuri Subject: Re: What is the best choice of USB WiFi adapter working on FreeBSD? References: <96108220-fc4f-8c71-8df1-c683aa8d2406@rawbw.com> <045f4f3d-c848-cc4d-1ba4-eb439d0fabad@rawbw.com> Date: Sat, 15 Oct 2016 02:26:06 +0300 Cc: freebsd-wireless MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Andriy Voskoboinyk" Message-ID: In-Reply-To: <045f4f3d-c848-cc4d-1ba4-eb439d0fabad@rawbw.com> User-Agent: Opera Mail/12.16 (FreeBSD) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Fri, 14 Oct 2016 23:26:08 -0000 Sat, 15 Oct 2016 01:42:53 +0300 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0=D0= =BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Yuri : https://github.com/s3erios/rtwn ? (I'm going to commit it soon). > I am trying to compile the list of USB Wi-Fi cards that are well = > supported to add such section to the handbook. > Anybody knows other cards that work well besides RT5370 USB dongles an= d = > TP-LINK TL-WDN3200? > > Thank you, > Yuri > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to = > "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@freebsd.org Sat Oct 15 00:13:01 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8B145C1093A for ; Sat, 15 Oct 2016 00:13:01 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 61A8C62B for ; Sat, 15 Oct 2016 00:13:01 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yuri.doctorlan.com (c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id u9F0CwdS049399 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 14 Oct 2016 17:12:58 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190] claimed to be yuri.doctorlan.com Subject: Re: What is the best choice of USB WiFi adapter working on FreeBSD? To: Andriy Voskoboinyk References: <96108220-fc4f-8c71-8df1-c683aa8d2406@rawbw.com> <045f4f3d-c848-cc4d-1ba4-eb439d0fabad@rawbw.com> Cc: freebsd-wireless From: Yuri Message-ID: <6ba0e615-425d-9950-f84c-91205b861b54@rawbw.com> Date: Fri, 14 Oct 2016 17:12:57 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Sat, 15 Oct 2016 00:13:01 -0000 On 10/14/2016 16:26, Andriy Voskoboinyk wrote: > > https://github.com/s3erios/rtwn ? (I'm going to commit it soon). But these are just USB IDs. This doesn't necessarily mean they actually work well? Yuri From owner-freebsd-wireless@freebsd.org Sat Oct 15 14:29:40 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5D879C12E4A for ; Sat, 15 Oct 2016 14:29:40 +0000 (UTC) (envelope-from kevlo@ns.kevlo.org) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C42B36A4 for ; Sat, 15 Oct 2016 14:29:39 +0000 (UTC) (envelope-from kevlo@ns.kevlo.org) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.15.2/8.15.2) with ESMTPS id u9FESAUn010307 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 15 Oct 2016 22:28:11 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.15.2/8.15.2/Submit) id u9FES8Wm010306; Sat, 15 Oct 2016 22:28:08 +0800 (CST) (envelope-from kevlo) Date: Sat, 15 Oct 2016 22:28:08 +0800 From: Kevin Lo To: Yuri Cc: Andriy Voskoboinyk , freebsd-wireless Subject: Re: What is the best choice of USB WiFi adapter working on FreeBSD? Message-ID: <20161015142808.GA10296@ns.kevlo.org> References: <96108220-fc4f-8c71-8df1-c683aa8d2406@rawbw.com> <045f4f3d-c848-cc4d-1ba4-eb439d0fabad@rawbw.com> <6ba0e615-425d-9950-f84c-91205b861b54@rawbw.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6ba0e615-425d-9950-f84c-91205b861b54@rawbw.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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: Sat, 15 Oct 2016 14:29:40 -0000 On Fri, Oct 14, 2016 at 05:12:57PM -0700, Yuri wrote: > > On 10/14/2016 16:26, Andriy Voskoboinyk wrote: > > > > https://github.com/s3erios/rtwn ? (I'm going to commit it soon). > > > But these are just USB IDs. This doesn't necessarily mean they actually > work well? They work well. Please see: https://lists.freebsd.org/pipermail/freebsd-wireless/2016-September/007087.html > Yuri Kevin