From owner-freebsd-current@freebsd.org Tue Jan 19 19:27:08 2016 Return-Path: Delivered-To: freebsd-current@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 0AC89A89C67 for ; Tue, 19 Jan 2016 19:27:08 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (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 CB9261739 for ; Tue, 19 Jan 2016 19:27:07 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-io0-x232.google.com with SMTP id q21so592244925iod.0 for ; Tue, 19 Jan 2016 11:27:07 -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=npRHOTSepdaETZkPcr6XU5OJVDyoVy66grzyjFO2k04=; b=LZF7ElNSKXUHMXtUqFVWx5NkQfnJV9BpB80JcXOvwg67OrpKzw2A0lZai/MZxqtsNZ A+3p/FNtpW5n6E2vGvkL1u3HbY5dhfXaeKwgbRRiHfVzOKfbq4iMkZwtDZqwNpT6sihe qAoZs18+wZirYcrUodnF6P8nOP/MFeWkfuVKJZ90cX9M4BEkALr17vch3ROgbb3YvRVU IMaE7BptojbhgwXwfMTYyJO8doqRSCW+HQSMmwO4XKUn2RSjAIBEo5Bqf20PmlUaN+sO SyKLztwpmIBTNVwkbvyG4yXpLT0LzZ/Zj1kYah76hKy2//oKHHhXLdt3wN17Yyfk1swA QiXQ== 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:date :message-id:subject:from:to:cc:content-type; bh=npRHOTSepdaETZkPcr6XU5OJVDyoVy66grzyjFO2k04=; b=CzqIqtrowp3NRw9G6iDX3xwVu1W7rRg1Nan9id4X3Lk2EuK+TUmG1zAJAtg7teXJGW 8IWPg6HSGqMpadRvFKkKmKrPSUw9eqVEEBk6DyTyIoESlDUzKfdE536He2K5A7GVJdj7 7sZtxisfpyiHTEeNFc9z9z6SlJsirpRBwkJhxGY90Fcgoph49OtJpM/v+eKVEwSKnG7d uB2D46Ug/mt1+t12+A2V72ntjZArizVIKtw41Gwkf8zUK5Y+bBd2w4z21K5tW3nesUJL oQz0ypE+N58zFD6OrLxlJslR3wOKjWbFt/z92Wl4c2C3oqSLZL5eZqzTlYcUamRe5Gc9 zv7g== X-Gm-Message-State: ALoCoQknN/HVqLGpRt6MYM9kdWI1fKs5VIbyxsdeQ71j5h/oH5sMsdgViHMAyqFZgbtCvyIv16c5q8H96yoZjvmR6nF5bDG20A== MIME-Version: 1.0 X-Received: by 10.107.162.146 with SMTP id l140mr26218985ioe.123.1453231627332; Tue, 19 Jan 2016 11:27:07 -0800 (PST) Received: by 10.36.121.16 with HTTP; Tue, 19 Jan 2016 11:27:07 -0800 (PST) In-Reply-To: <20160119201746.13674c54.ohartman@zedat.fu-berlin.de> References: <20160119201746.13674c54.ohartman@zedat.fu-berlin.de> Date: Tue, 19 Jan 2016 11:27:07 -0800 Message-ID: Subject: Re: network/ath: on CURRENT no connections possible on ath-based AP From: Adrian Chadd To: "O. Hartmann" Cc: FreeBSD CURRENT Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jan 2016 19:27:08 -0000 Theres been nothing in the ath code that I can think of that'd do this. Can you get me "works" and "doesn't work" revisions? thanks, -a On 19 January 2016 at 11:17, O. Hartmann wrote: > Running hostapd and a Atheros based AP on recent CURRENT (FreeBSD 11.0-CURRENT #8 > r294329: Tue Jan 19 18:23:20 CET 2016 amd64), clients do not connect anymore to that > specific AP. They did a week or two ago (mobile phones, several notebooks). > > The WiFi adaptor is this one (dmesg): > > [...] > ath0: mem 0xf7e00000-0xf7e1ffff irq 16 at device 0.0 on pci1 > ar9300_attach: calling ar9300_hw_attach > ar9300_hw_attach: calling ar9300_eeprom_attach > ar9300_flash_map: unimplemented for now > Restoring Cal data from DRAM > Restoring Cal data from EEPROM > ar9300_hw_attach: ar9300_eeprom_attach returned 0 > ath0: [HT] enabling HT modes > ath0: [HT] enabling short-GI in 20MHz mode > ath0: [HT] 1 stream STBC receive enabled > ath0: [HT] 1 stream STBC transmit enabled > ath0: [HT] 3 RX streams; 3 TX streams > ath0: AR9380 mac 448.3 RF5110 phy 3276.12 > ath0: 2GHz radio: 0x0000; 5GHz radio: 0x0000 > [...] > > and from ifconfig: > > [...] > wlan0: flags=8943 metric 0 mtu 1500 > ether xx:xx:xx:xx:xx:xx > inet 192.168.2.1 netmask 0xffffff00 broadcast 192.168.2.255 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > status: running > ssid Berghof channel 10 (2457 MHz 11g) bssid xx:xx:xx:xx:xx:xx > regdomain ETSI country DE indoor ecm authmode WPA2/802.11i > privacy MIXED deftxkey 2 AES-CCM 2:128-bit AES-CCM 3:128-bit > txpower 30 scanvalid 60 protmode CTS wme burst dtimperiod 1 -dfs > groups: wlan > [...] > > On some earlier dmesg outputs, I see the line > > ath0: AR9380 mac 448.3 RF5110 phy 2457.9 > > instead of the most recent > > ath0: AR9380 mac 448.3 RF5110 phy 3276.12 > > I do not see any strange behaviour until clients fetch (successfully!) their IP via > isc-dhcp (isc-dhcp43-server-4.3.3P1_1), then they die or can not access the network any > further. > > Has there been a change recently? > > Kind regards, > > Oliver