From owner-freebsd-wireless@freebsd.org Sun Dec 20 03:12:17 2015 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 80D3CA4C60F for ; Sun, 20 Dec 2015 03:12: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 670E71786 for ; Sun, 20 Dec 2015 03:12: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 tBK3CHCP040694 for ; Sun, 20 Dec 2015 03:12:17 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 203271] Wi-Fi no longer driven on some hardware with 11.0-CURRENT Date: Sun, 20 Dec 2015 03:12:17 +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-CURRENT X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: grahamperrin@gmail.com X-Bugzilla-Status: Closed X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- 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: 7bit 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.20 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, 20 Dec 2015 03:12:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203271 Graham Perrin changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|New |Closed --- Comment #12 from Graham Perrin --- At Kris confirms that the 2015-11-16 commit (thanks) was a fix for what was reported here. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@freebsd.org Tue Dec 22 13:07:31 2015 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 83016A4C528 for ; Tue, 22 Dec 2015 13:07:31 +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 6A15E1576 for ; Tue, 22 Dec 2015 13:07:31 +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 tBMD7VNc017888 for ; Tue, 22 Dec 2015 13:07:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 194336] AR9300 pci wireless card not working Date: Tue, 22 Dec 2015 13:07:31 +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: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: greg@codeconcepts.com X-Bugzilla-Status: New X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.20 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, 22 Dec 2015 13:07:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194336 Greg Becker changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |greg@codeconcepts.com --- Comment #12 from Greg Becker --- I am seeing this problem (i.e., "unable to collect...") with a TP-LINK TL-WDN4800 I picked up from from Frys the other day in Austin, TX. After getting nowhere searching the web, I crafted the following patch and low and behold the card now appears to work just fine: Index: sys/dev/ath/if_ath.c =================================================================== --- sys/dev/ath/if_ath.c (revision 292515) +++ sys/dev/ath/if_ath.c (working copy) @@ -5631,11 +5631,11 @@ struct ath_hal *ah = sc->sc_ah; DPRINTF(sc, ATH_DEBUG_REGDOMAIN, "%s: use rd %u cc %d\n", - __func__, SKU_DEBUG, CTRY_DEFAULT); + __func__, SKU_DEBUG, CTRY_UNITED_STATES); /* XXX check return */ (void) ath_hal_getchannels(ah, chans, maxchans, nchans, - HAL_MODE_ALL, CTRY_DEFAULT, SKU_DEBUG, AH_TRUE); + HAL_MODE_ALL, CTRY_UNITED_STATES, SKU_DEBUG, AH_TRUE); } @@ -5651,7 +5651,7 @@ * Collect channel set based on EEPROM contents. */ status = ath_hal_init_channels(ah, ic->ic_channels, IEEE80211_CHAN_MAX, - &ic->ic_nchans, HAL_MODE_ALL, CTRY_DEFAULT, SKU_NONE, AH_TRUE); + &ic->ic_nchans, HAL_MODE_ALL, CTRY_UNITED_STATES, SKU_NONE, AH_TRUE); if (status != HAL_OK) { if_printf(ifp, "%s: unable to collect channel list from hal, " "status %d\n", __func__, status); Dec 21 07:41:09 harper kernel: ath0: mem 0xfb500000-0xfb51ffff irq 32 at device 0.0 on pci3 Dec 21 07:41:09 harper kernel: ar9300_set_stub_functions: setting stub functions Dec 21 07:41:09 harper kernel: ar9300_set_stub_functions: setting stub functions Dec 21 07:41:09 harper kernel: ar9300_attach: calling ar9300_hw_attach Dec 21 07:41:09 harper kernel: ar9300_hw_attach: calling ar9300_eeprom_attach Dec 21 07:41:09 harper kernel: ar9300_flash_map: unimplemented for now Dec 21 07:41:09 harper kernel: Restoring Cal data from DRAM Dec 21 07:41:09 harper kernel: Restoring Cal data from EEPROM Dec 21 07:41:09 harper kernel: ar9300_hw_attach: ar9300_eeprom_attach returned 0 Dec 21 07:41:09 harper kernel: ath0: RX status length: 48 Dec 21 07:41:09 harper kernel: ath0: RX buffer size: 4096 Dec 21 07:41:09 harper kernel: ath0: TX descriptor length: 128 Dec 21 07:41:09 harper kernel: ath0: TX status length: 36 Dec 21 07:41:09 harper kernel: ath0: TX buffers per descriptor: 4 Dec 21 07:41:09 harper kernel: ar9300_freebsd_setup_x_tx_desc: called, 0x0/0, 0x0/0, 0x0/0 Dec 21 07:41:09 harper kernel: ath0: ath_edma_setup_rxfifo: type=0, FIFO depth = 16 entries Dec 21 07:41:09 harper kernel: ath0: ath_edma_setup_rxfifo: type=1, FIFO depth = 128 entries Dec 21 07:41:09 harper kernel: ath0: [HT] enabling HT modes Dec 21 07:41:09 harper kernel: ath0: [HT] enabling short-GI in 20MHz mode Dec 21 07:41:09 harper kernel: ath0: [HT] 1 stream STBC receive enabled Dec 21 07:41:09 harper kernel: ath0: [HT] 1 stream STBC transmit enabled Dec 21 07:41:09 harper kernel: ath0: [HT] 3 RX streams; 3 TX streams Dec 21 07:41:09 harper kernel: ath0: AR9380 mac 448.3 RF5110 phy 0.0 Dec 21 07:41:09 harper kernel: ath0: 2GHz radio: 0x0000; 5GHz radio: 0x0000 Dec 21 07:41:09 harper devd: Executing '/etc/pccard_ether ath0 start' Dec 21 07:41:10 harper kernel: wlan0: Ethernet address: f4:f2:6d:b5:42:25 Dec 21 07:41:10 harper devd: Executing '/etc/pccard_ether ath0 start' Dec 21 07:41:10 harper devd: Executing '/etc/pccard_ether wlan0 start' -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@freebsd.org Tue Dec 22 14:40:15 2015 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 C4111A4E48A for ; Tue, 22 Dec 2015 14:40: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 B0A7610BB for ; Tue, 22 Dec 2015 14:40: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 tBMEeFwf023096 for ; Tue, 22 Dec 2015 14:40:15 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 194336] AR9300 pci wireless card not working Date: Tue, 22 Dec 2015 14:40: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: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.20 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, 22 Dec 2015 14:40:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194336 --- Comment #13 from Adrian Chadd --- sorry, keep pestering me until I figure out which country code to put this NIC in. :) -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@freebsd.org Tue Dec 22 22:57:49 2015 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 5CCDAA50F53 for ; Tue, 22 Dec 2015 22:57:49 +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 4DBCB113D for ; Tue, 22 Dec 2015 22:57:49 +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 tBMMvn1a092555 for ; Tue, 22 Dec 2015 22:57:49 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 203745] A2DP Support for Bluetooth Headphone Audio Date: Tue, 22 Dec 2015 22:57:48 +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-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hselasky@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.20 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, 22 Dec 2015 22:57:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203745 --- Comment #25 from Hans Petter Selasky --- Hi Tone, Can you SVN up and try the latest version of virtual_oss? I've tried to add support for MPEG-2 AAC-LC which some audio headsets use. Some RTP framing bits are missing, so at least mine doesn't produce sound, but does transfer the payload data. Maybe someone wants to help out? --HPS -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@freebsd.org Tue Dec 22 23:13:44 2015 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 E710FA4F52E for ; Tue, 22 Dec 2015 23:13:44 +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 D8AC51024 for ; Tue, 22 Dec 2015 23:13:44 +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 tBMNDiug058941 for ; Tue, 22 Dec 2015 23:13:44 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 203745] A2DP Support for Bluetooth Headphone Audio Date: Tue, 22 Dec 2015 23:13:44 +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-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hselasky@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.20 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, 22 Dec 2015 23:13:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203745 --- Comment #26 from Hans Petter Selasky --- Forgot to say: You'll need to install libsamplerate and libfaac . --HPS -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@freebsd.org Wed Dec 23 10:32:20 2015 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 9C146A4FC28; Wed, 23 Dec 2015 10:32:20 +0000 (UTC) (envelope-from cochard@gmail.com) Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::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 1168317C8; Wed, 23 Dec 2015 10:32:20 +0000 (UTC) (envelope-from cochard@gmail.com) Received: by mail-lb0-x22b.google.com with SMTP id sv6so37472444lbb.0; Wed, 23 Dec 2015 02:32:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to:content-type; bh=UaMrUq246YYzdUdt3KOtQzfHESEUs8aMpG/DFi4I0yQ=; b=QlXHLRmJnZa+YvhBMS2KhU4Uuwjl989oIfMH2cGPOTuTkxu5v5ex7HJi1CkGyKBnAL GFNYKaYE2DU5U8uad+Zk9anz9Fw8YVJRIYpyC/9ES9Xh/pPn6FspvMLtp0eLYlFdHoXk z6CicKaPaf4jUZLfLET+wCbt43zLSoNruB+GStyKHHbQvqjZdlR8cQx4IdzXOtDVgY5X /E6w5tZixw4bDVxJsflOEKvtGagFFVLUQbH6G+uhGK0A3V0Y2iRqMC/NHOFLVlPuPCYN 6i0difQaoqZ+gbCU/FSiQy7MUBQws2mHipn9J09HWDm+fTRVs4WTJQEQn/8BwsxsXIMi gByA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cochard-me.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:from:date:message-id:subject:to:content-type; bh=UaMrUq246YYzdUdt3KOtQzfHESEUs8aMpG/DFi4I0yQ=; b=VMXcbNw21QG5+wTnDYyRG3M/z1VY9EhZKt8T1cRXkByy3mhl8I4/4u//5r2EbqltMN amBgOXAE0T7RL+TK238RCcy+bF2Ptk0D4mVA1EjqpYyLmUevTx/g0OvlI+GZYnqs5B0k HMkA0sc5Qe7FSlLHlFg0v3HXjYhfN6bkJjiuF5ogovzQuYCqYVf04wgjU0/Ep0hkOkDz x7cFWpkAoMURUz2XhFMVHgTEHd40hN+JABtbN6du/3irg2e7dAevcwnUUa/cZD/MesI+ 8l9Nuq0MU9itVDaGmSe1nJXa6hfdabRXgDQLGEiw/a+YTyZWhYVH1aJm1/7Me74gvalI z4zQ== X-Received: by 10.112.132.6 with SMTP id oq6mr5835032lbb.38.1450866737590; Wed, 23 Dec 2015 02:32:17 -0800 (PST) MIME-Version: 1.0 Sender: cochard@gmail.com Received: by 10.25.147.78 with HTTP; Wed, 23 Dec 2015 02:31:58 -0800 (PST) From: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= Date: Wed, 23 Dec 2015 11:31:58 +0100 X-Google-Sender-Auth: W5DKbrfSsF8ZFa8daXTGGYS6rbY Message-ID: Subject: forwarding didn't work if wlan0 is member of a bridge To: "freebsd-current@freebsd.org" , "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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, 23 Dec 2015 10:32:20 -0000 Hi, If wlan0 interface is member of a bridge, FreeBSD didn't reach to forward-back packets to wireless client My setup is this one: internet gateway <--> [net0] fbsd router [net1 + wifi-hostap in bridge0] <--> wireless client and the problem description: - wireless clients didn't receive any packet back: the fbsd-router blocks answers because it thinks wireless clients are "unreachable". - But wireless clients can reach all IP of the fbsd-router hitself without problem, and fbsd-router can ping them too. - Ethernet clients connected to the same bridge0 didn't have problem A tcpdump on the outgoing interface shows the fbsd-router correctly receiving/NATing/forwarding the wireless-client packet (10.239.142.104 natted to 192.168.100.70) toward the Internet-gateway (192.168.100.254), but once received the response from the internet-gateway it is not able to reach the wireless-client (unreachable): [fbsd-router]~> sudo tcpdump -pni net0 icmp tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on net0, link-type EN10MB (Ethernet), capture size 262144 bytes 07:35:24.869560 IP 192.168.100.70 > 192.168.100.254: ICMP echo request, id 1, seq 375, length 40 07:35:24.869772 IP 192.168.100.254 > 192.168.100.70: ICMP echo reply, id 1, seq 375, length 40 07:35:24.870314 IP 192.168.100.70 > 192.168.100.254: ICMP host 10.239.142.104 unreachable, length 36 But directly from the fbsd-router, there is no problem for reaching the wireless-client: [fbsd-router]~> ping wireless-client PING 10.239.142.104 (10.239.142.104): 56 data bytes 64 bytes from 10.239.142.104: icmp_seq=0 ttl=128 time=2.633 ms 64 bytes from 10.239.142.104: icmp_seq=1 ttl=128 time=1.614 ms I'm using a bridge because I need to use only one subnet for all my clients (ethernet and wifi): [fbsd-router]~> ifconfig bridge0 bridge0: flags=8843 metric 0 mtu 1500 ether 02:82:9f:45:81:00 inet 10.239.142.126 netmask 0xffffffe0 broadcast 10.239.142.127 nd6 options=49 groups: bridge id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: wlan0 flags=143 ifmaxaddr 0 port 6 priority 128 path cost 33333 member: net1 flags=143 ifmaxaddr 0 port 2 priority 128 path cost 55 And this "unreacheable" problem is related to the bridge, if I remove the wlan0 from the bridge, there is no more problem. What problem can cause FreeBSD to answer back "unreachable" when wlan0 is member of a bridge ? Head versions tested: r290522, r291362, r292613. Thanks, From owner-freebsd-wireless@freebsd.org Wed Dec 23 14:24:10 2015 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 AD0B5A50096 for ; Wed, 23 Dec 2015 14:24: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 9D1171102 for ; Wed, 23 Dec 2015 14:24: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 tBNEOAXV010439 for ; Wed, 23 Dec 2015 14:24:10 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 203745] A2DP Support for Bluetooth Headphone Audio Date: Wed, 23 Dec 2015 14:24: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-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hselasky@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.20 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, 23 Dec 2015 14:24:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203745 --- Comment #27 from Hans Petter Selasky --- A closer look reveals that the codec is called aac_latm and is supported by ffmpeg. Looks like lib faac won't produce the correct data. Will look more at this after x-mas. Feel free to send me patches. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@freebsd.org Wed Dec 23 14:40:18 2015 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 18C20A50494 for ; Wed, 23 Dec 2015 14:40:18 +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 F10711878 for ; Wed, 23 Dec 2015 14:40: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 tBNEeHux036345 for ; Wed, 23 Dec 2015 14:40:17 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 194336] AR9300 pci wireless card not working Date: Wed, 23 Dec 2015 14:40:18 +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: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: greg@codeconcepts.com X-Bugzilla-Status: New X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.20 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, 23 Dec 2015 14:40:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194336 --- Comment #14 from Greg Becker --- Thanks Adrian! For what it's worth, here's the ATH_DEBUG output when it fails, hope this helps! FreeBSD harper.cc.codeconcepts.com 10.2-STABLE FreeBSD 10.2-STABLE #13 r292515M: Mon Dec 21 07:20:01 CST 2015 root@harper.cc.codeconcepts.com:/usr/obj/usr/src/sys/HARPER amd64 I should note, this log output is from the time I built directly from the sys/modules/ath directory, which with my patch allowed the device to attach, but I then ran into the "rxfifo alloc" issue and had to rebuild from /usr/src in the usual way in order to get a working device. Dec 21 06:36:08 harper kernel: ath0: mem 0xfb500000-0xfb51ffff irq 32 at device 0.0 on pci3 Dec 21 06:36:08 harper kernel: ar9300_set_stub_functions: setting stub functions Dec 21 06:36:08 harper kernel: ar9300_set_stub_functions: setting stub functions Dec 21 06:36:08 harper kernel: ar9300_set_power_mode: AWAKE -> AWAKE (set chip ) Dec 21 06:36:08 harper kernel: ar9300_attach: ah_serialise_reg_war is 0 Dec 21 06:36:08 harper kernel: ar9300_attach: This Mac Chip Rev 0x1c0.3 is Dec 21 06:36:08 harper kernel: ar9300_attach: calling ar9300_hw_attach Dec 21 06:36:08 harper kernel: ar9300_hw_attach: calling ar9300_eeprom_attach Dec 21 06:36:08 harper kernel: ar9300_flash_map: unimplemented for now Dec 21 06:36:08 harper kernel: Restoring Cal data from DRAM Dec 21 06:36:08 harper kernel: Restoring Cal data from EEPROM Dec 21 06:36:08 harper kernel: ar9300_eeprom_restore_internal_address: Found block at 3ff: code=3 ref=5 length=564 major=2 minor=20 Dec 21 06:36:08 harper kernel: ar9300_eeprom_restore_internal_address: checksum a9ff a9ff Dec 21 06:36:08 harper kernel: ar9300_eeprom_restore_internal_address: restore eeprom 0: block, reference 5, length 564 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 0: spot=2 offset=2 length=6 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 8: spot=24 offset=16 length=5 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 15: spot=43 offset=14 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 18: spot=61 offset=17 length=12 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 32: spot=94 offset=21 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 35: spot=102 offset=7 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 38: spot=136 offset=33 length=2 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 42: spot=141 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 47: spot=147 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 52: spot=153 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 57: spot=159 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 62: spot=165 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 67: spot=171 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 72: spot=177 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 77: spot=183 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 82: spot=189 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 87: spot=198 offset=6 length=8 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 97: spot=273 offset=67 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 100: spot=287 offset=13 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 103: spot=294 offset=6 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 106: spot=301 offset=6 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 109: spot=324 offset=22 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 112: spot=328 offset=3 length=9 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 123: spot=344 offset=7 length=9 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 134: spot=356 offset=3 length=62 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 198: spot=432 offset=14 length=10 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 210: spot=459 offset=17 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 213: spot=489 offset=29 length=25 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 240: spot=517 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 245: spot=523 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 250: spot=529 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 255: spot=535 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 260: spot=541 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 265: spot=547 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 270: spot=553 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 275: spot=559 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 280: spot=565 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 285: spot=571 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 290: spot=577 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 295: spot=583 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 300: spot=589 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 305: spot=595 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 310: spot=601 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 315: spot=607 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 320: spot=613 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 325: spot=619 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 330: spot=625 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 335: spot=631 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 340: spot=637 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 345: spot=643 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 350: spot=649 offset=3 length=3 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 355: spot=656 offset=4 length=23 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 380: spot=716 offset=37 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 383: spot=730 offset=13 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 386: spot=744 offset=13 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 389: spot=758 offset=13 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 392: spot=772 offset=13 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 395: spot=786 offset=13 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 398: spot=800 offset=13 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 401: spot=814 offset=13 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 404: spot=828 offset=13 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 407: spot=842 offset=13 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 410: spot=856 offset=13 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 413: spot=870 offset=13 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 416: spot=884 offset=13 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 419: spot=898 offset=13 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 422: spot=912 offset=13 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 425: spot=926 offset=13 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 428: spot=945 offset=18 length=10 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 440: spot=959 offset=4 length=1 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 443: spot=967 offset=7 length=25 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 470: spot=995 offset=3 length=13 Dec 21 06:36:08 harper kernel: ar9300_uncompress_block: Restore at 485: spot=1011 offset=3 length=77 Dec 21 06:36:08 harper kernel: ar9300_hw_attach: ar9300_eeprom_attach returned 0 Dec 21 06:36:08 harper kernel: ar9300_enable_mib_counters: Enable MIB counters Dec 21 06:36:08 harper kernel: ath0: RX status length: 48 Dec 21 06:36:08 harper kernel: ath0: RX buffer size: 4096 Dec 21 06:36:08 harper kernel: ath0: TX descriptor length: 128 Dec 21 06:36:08 harper kernel: ath0: TX status length: 36 Dec 21 06:36:08 harper kernel: ath0: TX buffers per descriptor: 4 Dec 21 06:36:08 harper kernel: ar9300_freebsd_setup_x_tx_desc: called, 0x0/0, 0x0/0, 0x0/0 Dec 21 06:36:08 harper kernel: getchannels: cc 0 regDmn 0xf0 mode 0xffffff ecm Dec 21 06:36:08 harper kernel: isEepromValid: invalid regulatory domain/country code 0x14 Dec 21 06:36:08 harper kernel: getregstate: invalid EEPROM contents Dec 21 06:36:08 harper kernel: ath0: ath_getchannels: unable to collect channel list from hal, status 12 Dec 21 06:36:08 harper kernel: ar9300_set_power_mode: AWAKE -> AWAKE (set chip ) Dec 21 06:36:08 harper kernel: ar9300_ani_detach: Detaching Ani Dec 21 06:36:08 harper kernel: ar9300_disable_mib_counters: Disabling MIB counters Dec 21 06:36:08 harper kernel: ar9300_set_power_mode: AWAKE -> FULL-SLEEP (set chip ) Dec 21 06:36:08 harper kernel: device_attach: ath0 attach returned 22 -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@freebsd.org Wed Dec 23 15:08:33 2015 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 65648A50C8B for ; Wed, 23 Dec 2015 15:08:33 +0000 (UTC) (envelope-from sm@ara-ler.com) Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (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 3259E14E5 for ; Wed, 23 Dec 2015 15:08:32 +0000 (UTC) (envelope-from sm@ara-ler.com) Received: by mail-oi0-x22c.google.com with SMTP id o62so119722587oif.3 for ; Wed, 23 Dec 2015 07:08:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ara-ler-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=oxsy3lRe/sQYWIaps7d6+I33CNmH2hVTxXAFFBL5ALY=; b=bEyCPSxRuhkhK1ol2tWhwhQl8UaAah2uhhlwbYLHwafe6eEr6RvNN4tnrTXDWqlObi Z4lOV429nqkMRNVv7gizds89qKZK6f+R7k/P3mQw+0dIs8VZaMDdzSSm/v1QVKZTfgIx brRFP9846rLHupqCJIehrOglE9xxjoZGq0KrUdXmCBx9yvNsG6FxfKm+X/SP7oWMfUBj DT3fxA8jZMnjw70mVHs9779+oFqCcww6k9Y1tuVq/AUcgUUjpAmnK+Gb/rNBcWjbPF3J Z8dDYO8kEINpUQKclScgmknLQq2lk2BX8+XdAhIbe36jaTVteHR+HXTvcMwcwUDVmiYm /nNw== 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:references :mime-version:content-type:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=oxsy3lRe/sQYWIaps7d6+I33CNmH2hVTxXAFFBL5ALY=; b=OtqwB+nk0rPzXiWXz4wY20BlWLk5Xb3szemXthZBVIZz9hl2wHjmghgnY69YaZy1cv Y0YRnmBLEkVZo4U5nQZoNmA0r2yBfDW4pr2DbOXq3MrPJ1R8QDoJA8uJZ4uaAuBiO81z klkeDApY3JzQYwuYVujuXmytVBKjbRdHHFmJ4SIgnBfokIzUWVweUiTEWLujDOgc0p7n 4PmbRKys5PPVNUquSff+JuN2ab2WgVvGqG946gmPWkJIw5yIO9Wm8Zf2CgIN2VAoOq9g u9kFVdrxV99AJwj6Boq2mXAIAjSV8HbndZTq3cGazWQKQlREitAyT81Ty7Vb7kbqzXdZ j+zQ== X-Gm-Message-State: ALoCoQkeT93/CIqTq2K/Elu+mtQ+E468is5GvM3OmX7FxLoOBcF1kJxQV2r4yueSuysjQp0fuV9bmw5QDukRgtcK2Ipj3xRhtQ== X-Received: by 10.202.176.66 with SMTP id z63mr14184554oie.61.1450883312228; Wed, 23 Dec 2015 07:08:32 -0800 (PST) Received: from debian.ara-ler.com ([50.243.135.133]) by smtp.gmail.com with ESMTPSA id sd7sm4917398oec.13.2015.12.23.07.08.31 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 23 Dec 2015 07:08:31 -0800 (PST) Date: Wed, 23 Dec 2015 08:08:29 -0700 From: Sergey Manucharian To: "freebsd-current@freebsd.org" , "freebsd-wireless@freebsd.org" Subject: Re: forwarding didn't work if wlan0 is member of a bridge Message-ID: <20151223150829.GO3487@debian.ara-ler.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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, 23 Dec 2015 15:08:33 -0000 Excerpts from Olivier Cochard-Labbé's message from Wed 23-Dec-15 11:31: > If wlan0 interface is member of a bridge, FreeBSD didn't reach to > forward-back packets to wireless client > > My setup is this one: > > internet gateway <--> [net0] fbsd router [net1 + wifi-hostap in bridge0] > <--> wireless client > > and the problem description: > - wireless clients didn't receive any packet back: the fbsd-router blocks > answers because it thinks wireless clients are "unreachable". > - But wireless clients can reach all IP of the fbsd-router hitself without > problem, and fbsd-router can ping them too. > - Ethernet clients connected to the same bridge0 didn't have problem I believe this is related to the fact that wifi adapter cannot have more that one MAC address. And that becomes true when it's a member of a bridge. There exist some tricky ways to overcome that though. S. From owner-freebsd-wireless@freebsd.org Wed Dec 23 15:45:01 2015 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 13950A4F93E for ; Wed, 23 Dec 2015 15:45:01 +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 DDEF11DCF for ; Wed, 23 Dec 2015 15:45:00 +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 tBNFj0lw042495 for ; Wed, 23 Dec 2015 15:45:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 205542] FreeBSD 11.0-CURRENT r292413 on Dell Inspiron 13 7352 (with Intel AC 7265) not creating iwm0 Date: Wed, 23 Dec 2015 15:45:00 +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-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: neel@neelc.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- 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 attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.20 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, 23 Dec 2015 15:45:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205542 Bug ID: 205542 Summary: FreeBSD 11.0-CURRENT r292413 on Dell Inspiron 13 7352 (with Intel AC 7265) not creating iwm0 Product: Base System Version: 11.0-CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: wireless Assignee: freebsd-wireless@FreeBSD.org Reporter: neel@neelc.org Created attachment 164553 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=164553&action=edit dmesg log (not dmesg.boot) for Dell Inspiron 13 7352 Hi, My laptop, a Dell Inspiron 13 7352 has the Intel AC 7265 wireless card. If I try to run 'kldload iwm', I get this in the dmesg: iwm0: mem 0xc1000000-0xc1001fff irq 18 at device 0.0 on pci1 iwm0: revision: 0x210, firmware 25.228 (API ver. 9) But if I check ifconfig, iwm0 does not appear. root@:/ # ifconfig lo0: flags=8049 metric 0 mtu 16384 options=600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff000000 nd6 options=21 groups: lo ue0: flags=8843 metric 0 mtu 1500 ether 00:e0:4c:b8:1f:54 inet 192.168.1.61 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=29 root@:/ Is there a solution to this issue? Thanks, Neel Chauhan === http://www.neelc.org/ -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@freebsd.org Wed Dec 23 15:45:45 2015 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 18108A4F95A for ; Wed, 23 Dec 2015 15:45:45 +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 07CAE1E07 for ; Wed, 23 Dec 2015 15:45:45 +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 tBNFjire043490 for ; Wed, 23 Dec 2015 15:45:44 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 205542] FreeBSD 11.0-CURRENT r292413 on Dell Inspiron 13 7352 (with Intel AC 7265) not creating iwm0 Date: Wed, 23 Dec 2015 15:45:44 +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-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: neel@neelc.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- 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: 7bit 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.20 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, 23 Dec 2015 15:45:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205542 --- Comment #1 from Neel Chauhan --- Created attachment 164554 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=164554&action=edit ifconfig output after loading ifconfig -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@freebsd.org Wed Dec 23 19:37:40 2015 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 4A029A508FB; Wed, 23 Dec 2015 19:37:40 +0000 (UTC) (envelope-from kp@vega.codepro.be) Received: from venus.codepro.be (venus.codepro.be [IPv6:2a01:4f8:162:1127::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.codepro.be", Issuer "Gandi Standard SSL CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0C7D015AD; Wed, 23 Dec 2015 19:37:39 +0000 (UTC) (envelope-from kp@vega.codepro.be) Received: from vega.codepro.be (unknown [172.16.1.3]) by venus.codepro.be (Postfix) with ESMTP id 0DAB28101; Wed, 23 Dec 2015 20:37:36 +0100 (CET) Received: by vega.codepro.be (Postfix, from userid 1001) id 082011EF3E; Wed, 23 Dec 2015 20:37:36 +0100 (CET) Date: Wed, 23 Dec 2015 20:37:36 +0100 From: Kristof Provost To: Sergey Manucharian Cc: "freebsd-current@freebsd.org" , "freebsd-wireless@freebsd.org" , Olivier =?utf-8?Q?Cochard-Labb=C3=A9?= Subject: Re: forwarding didn't work if wlan0 is member of a bridge Message-ID: <20151223193735.GC2928@vega.codepro.be> References: <20151223150829.GO3487@debian.ara-ler.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20151223150829.GO3487@debian.ara-ler.com> X-Checked-By-NSA: Probably User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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, 23 Dec 2015 19:37:40 -0000 On 2015-12-23 08:08:29 (-0700), Sergey Manucharian wrote: > I believe this is related to the fact that wifi adapter cannot have more > that one MAC address. And that becomes true when it's a member of a > bridge. There exist some tricky ways to overcome that though. > That's true, but that only applies in station mode (i.e. as a wifi client). If I'm reading the report right Olivier is using wifi0 as an access point here. Regards, Kristof From owner-freebsd-wireless@freebsd.org Wed Dec 23 19:39:33 2015 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 61FFAA509CB; Wed, 23 Dec 2015 19:39:33 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::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 3472217CF; Wed, 23 Dec 2015 19:39:33 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-io0-x22a.google.com with SMTP id 186so227857647iow.0; Wed, 23 Dec 2015 11:39:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=GHPnGC866XFjnjK9+292WZlKfoq+KaLCVdaJCcF6KI0=; b=YfDKfuRkH900vrNoF6ADvW/yYki1L7U6CWfMXJegx9FAcWpYGS6MbIvy0ZSPio4kWH GJb41iQBWGqzeGp/T4YdrbNSZ10cubXAuVDI+CeJG9EjQv8OaVdBNKyHwtFsadWiQGwO 3m/290T20NYIE4h0uMLjMxQ07ToVn/4ajvsj0Xx2WsNH09L7p7aOw42jTJx25o0mOh3o D7Flet98NP4mN6A01yeQKdcXMOscw2wbXofG5ImuQiy/imHwwavByEMMsiBal8lrUMlr DTi0ckHYmV437riD8O8Est60qq0R2rw4mcKvIkkS2/rPajTgGF/NsQKNnfSfNwkR4Afr BCng== MIME-Version: 1.0 X-Received: by 10.107.162.21 with SMTP id l21mr31043143ioe.123.1450899572620; Wed, 23 Dec 2015 11:39:32 -0800 (PST) Received: by 10.36.121.202 with HTTP; Wed, 23 Dec 2015 11:39:32 -0800 (PST) In-Reply-To: References: Date: Wed, 23 Dec 2015 11:39:32 -0800 Message-ID: Subject: Re: forwarding didn't work if wlan0 is member of a bridge From: Adrian Chadd To: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= Cc: "freebsd-current@freebsd.org" , "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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, 23 Dec 2015 19:39:33 -0000 Hi, inet 10.239.142.126 netmask 0xffffffe0 broadcast 10.239.142.127 This looks like a problem with your addressing. That netmask !=3D that broa= dcast. Please recheck your networking setup! -a On 23 December 2015 at 02:31, Olivier Cochard-Labb=C3=A9 wrote: > Hi, > > If wlan0 interface is member of a bridge, FreeBSD didn't reach to > forward-back packets to wireless client > > My setup is this one: > > internet gateway <--> [net0] fbsd router [net1 + wifi-hostap in bridge0] > <--> wireless client > > and the problem description: > - wireless clients didn't receive any packet back: the fbsd-router block= s > answers because it thinks wireless clients are "unreachable". > - But wireless clients can reach all IP of the fbsd-router hitself witho= ut > problem, and fbsd-router can ping them too. > - Ethernet clients connected to the same bridge0 didn't have problem > > A tcpdump on the outgoing interface shows the fbsd-router correctly > receiving/NATing/forwarding the wireless-client packet (10.239.142.104 > natted to 192.168.100.70) toward the Internet-gateway (192.168.100.254), > but once received the response from the internet-gateway it is not able t= o > reach the wireless-client (unreachable): > [fbsd-router]~> sudo tcpdump -pni net0 icmp > tcpdump: verbose output suppressed, use -v or -vv for full protocol decod= e > listening on net0, link-type EN10MB (Ethernet), capture size 262144 bytes > 07:35:24.869560 IP 192.168.100.70 > 192.168.100.254: ICMP echo request, i= d > 1, seq 375, length 40 > 07:35:24.869772 IP 192.168.100.254 > 192.168.100.70: ICMP echo reply, id = 1, > seq 375, length 40 > 07:35:24.870314 IP 192.168.100.70 > 192.168.100.254: ICMP host > 10.239.142.104 unreachable, length 36 > > But directly from the fbsd-router, there is no problem for reaching the > wireless-client: > [fbsd-router]~> ping wireless-client > PING 10.239.142.104 (10.239.142.104): 56 data bytes > 64 bytes from 10.239.142.104: icmp_seq=3D0 ttl=3D128 time=3D2.633 ms > 64 bytes from 10.239.142.104: icmp_seq=3D1 ttl=3D128 time=3D1.614 ms > > I'm using a bridge because I need to use only one subnet for all my clien= ts > (ethernet and wifi): > [fbsd-router]~> ifconfig bridge0 > bridge0: flags=3D8843 metric 0 mt= u > 1500 > ether 02:82:9f:45:81:00 > inet 10.239.142.126 netmask 0xffffffe0 broadcast 10.239.142.127 > nd6 options=3D49 > groups: bridge > id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 > maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 > root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 > member: wlan0 flags=3D143 > ifmaxaddr 0 port 6 priority 128 path cost 33333 > member: net1 flags=3D143 > ifmaxaddr 0 port 2 priority 128 path cost 55 > > And this "unreacheable" problem is related to the bridge, if I remove the > wlan0 from the bridge, there is no more problem. > > What problem can cause FreeBSD to answer back "unreachable" when wlan0 is > member of a bridge ? > > Head versions tested: r290522, r291362, r292613. > > Thanks, > _______________________________________________ > 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= " From owner-freebsd-wireless@freebsd.org Wed Dec 23 20:53:26 2015 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 CA367A5039A for ; Wed, 23 Dec 2015 20:53:26 +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 BB0701284 for ; Wed, 23 Dec 2015 20:53:26 +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 tBNKrQL8078286 for ; Wed, 23 Dec 2015 20:53:26 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 205542] FreeBSD 11.0-CURRENT r292413 on Dell Inspiron 13 7352 (with Intel AC 7265) not creating iwm0 Date: Wed, 23 Dec 2015 20:53:26 +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-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: woodsb02@gmail.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.20 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, 23 Dec 2015 20:53:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205542 Ben Woods changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |woodsb02@gmail.com --- Comment #2 from Ben Woods --- Hi Neel, A few months ago a change was commuted to FreeBSD 11 current that meant the "parent" wifi devices would not show in ifconfig output. To see the list of wireless devices available on your FreeBSD 11 machine, type: $ sysctl net.wlan.devices Once you know what devices are available, you must create a wlan clone device, exactly the same as you have previously (follow instructions in the handbook and man pages as per normal). If you confirm this is your only problem, and everything else is working ok, please respond and also close this bug report. Good luck! -Ben -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@freebsd.org Wed Dec 23 23:10:40 2015 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 617AFA50044 for ; Wed, 23 Dec 2015 23:10:40 +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 5272B1439 for ; Wed, 23 Dec 2015 23:10:40 +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 tBNNAefp003443 for ; Wed, 23 Dec 2015 23:10:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 205542] FreeBSD 11.0-CURRENT r292413 on Dell Inspiron 13 7352 (with Intel AC 7265) not creating iwm0 Date: Wed, 23 Dec 2015 23:10: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-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: neel@neelc.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.20 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, 23 Dec 2015 23:10:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205542 --- Comment #3 from Neel Chauhan --- (In reply to Ben Woods from comment #2) Thank You! I got the WiFI working now. The only thing I need is Broadwell kernel mode setting now, but I could live without accelerated graphics support (at least I have a good CPU). -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@freebsd.org Thu Dec 24 08:08:50 2015 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 638B0A50DF5 for ; Thu, 24 Dec 2015 08:08:50 +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 54BD312ED for ; Thu, 24 Dec 2015 08:08:50 +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 tBO88omO025922 for ; Thu, 24 Dec 2015 08:08:50 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 205542] FreeBSD 11.0-CURRENT r292413 on Dell Inspiron 13 7352 (with Intel AC 7265) not creating iwm0 Date: Thu, 24 Dec 2015 08:08:50 +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-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: woodsb02@gmail.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.20 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, 24 Dec 2015 08:08:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205542 --- Comment #4 from Ben Woods --- That's good news - glad to hear it is all working for you. Can you please close this bug report by changing the status to CLOSED and selection an appropriate reason? -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@freebsd.org Thu Dec 24 08:37:57 2015 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 3BDFCA515D1; Thu, 24 Dec 2015 08:37:57 +0000 (UTC) (envelope-from woodsb02@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 D84981E8A; Thu, 24 Dec 2015 08:37:56 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: by mail-lf0-x231.google.com with SMTP id z124so154787458lfa.3; Thu, 24 Dec 2015 00:37:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=05xLhGdnJf/wSh9fekCEnLPf2qOIyTZdiPK2EPPJ+P0=; b=FbAaNyll/yJU4c1CQ9Th5G4KLvY6RNd1RRE/nKtJ7uT5qzUSL4YNsGfM6R6z0kCaC/ VOOyHJpJDTLgOGbza3k1lNkyqJZ0CyaG7sHTuvHmKyounsj2vOjary9yq+y5vXMK73R8 E0BcTYyXb2J2pb0vw4hiitS42mkimpDOX2CYrfkt8kJ+2DEfiyQU6ZaDRxbhXO3a4KY9 BEd5lrTIftkwBXpEKmobzRZaWnyHLFu7MSZWJM3VHl/shSnuP/MCvlZkXhC1trw08mtA 7paBO4tQRChjtsiShWf32rz4xv78yuWXsVEpEWE8g/laEz3r6kOPjRFSeccxz4uftqxB ojOg== MIME-Version: 1.0 X-Received: by 10.25.143.143 with SMTP id r137mr6627361lfd.93.1450946274762; Thu, 24 Dec 2015 00:37:54 -0800 (PST) Received: by 10.25.141.129 with HTTP; Thu, 24 Dec 2015 00:37:54 -0800 (PST) In-Reply-To: References: Date: Thu, 24 Dec 2015 09:37:54 +0100 Message-ID: Subject: Re: forwarding didn't work if wlan0 is member of a bridge From: Ben Woods To: Adrian Chadd Cc: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= , "freebsd-current@freebsd.org" , "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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, 24 Dec 2015 08:37:57 -0000 On Wednesday, 23 December 2015, Adrian Chadd wrote: > Hi, > > inet 10.239.142.126 netmask 0xffffffe0 broadcast 10.239.142.127 > > This looks like a problem with your addressing. That netmask != that > broadcast. > > Please recheck your networking setup! > > > -a > That broadcast looks correct for me for a bet mask of 0xffffffe0 (/27). http://jodies.de/ipcalc?host=10.239.142.126&mask1=27&mask2= Regards, Ben -- -- From: Benjamin Woods woodsb02@gmail.com From owner-freebsd-wireless@freebsd.org Thu Dec 24 13:47:25 2015 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 3D04EA50ECE for ; Thu, 24 Dec 2015 13:47:25 +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 2D49C1EA3 for ; Thu, 24 Dec 2015 13:47:25 +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 tBODlPEh077674 for ; Thu, 24 Dec 2015 13:47:25 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 205542] FreeBSD 11.0-CURRENT r292413 on Dell Inspiron 13 7352 (with Intel AC 7265) not creating iwm0 Date: Thu, 24 Dec 2015 13:47:25 +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-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: neel@neelc.org X-Bugzilla-Status: Closed X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.20 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, 24 Dec 2015 13:47:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205542 Neel Chauhan changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.