[Bug 207445] net80211 Atheros AR938x: non-working WiFi hostap since ~ January

2016-02-23 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207445

Bug ID: 207445
   Summary: net80211 Atheros AR938x: non-working WiFi hostap since
~ January
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: wireless
  Assignee: freebsd-wireless@FreeBSD.org
  Reporter: ohart...@zedat.fu-berlin.de
CC: freebsd-am...@freebsd.org
CC: freebsd-am...@freebsd.org

Running CURRENT (FreeBSD 11.0-CURRENT #15 r295926: Tue Feb 23 17:20:59 CET
2016) with a TP-Link PCIe WiFi adaptor TP-Link TL-WDN4800 N900 based on
Qualcomm Atheros AR938x chipset. I used this adaptor as AccessPoint with
CURRENT successfully over Christmas 2015 using both laptops and smartphone
WiFi. This doesn't work anymore since ~ mid-January after updating the system's
world and kernel.

I haven't found out what the exact reason is, but as far as I can describe is
that the client still receives its IP via DHCP (isc-dhcp43-server-4.3.3P1_1   
net/isc-dhcp43-server). Then authetication (via hostapd) fails.

root@gkommadoluch [~] dmesg|grep ath0
ath0:  mem 0xf7e0-0xf7e1 irq 16 at device 0.0 on pci1
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 0.0
ath0: 2GHz radio: 0x; 5GHz radio: 0x
ath0: stuck beacon; resetting (bmiss count 4)


pciconf -lvbce
[...]
ath0@pci0:1:0:0:class=0x028000 card=0x3112168c chip=0x0030168c rev=0x01
hdr=0x00
vendor = 'Qualcomm Atheros'
device = 'AR93xx Wireless Network Adapter'
class  = network
bar   [10] = type Memory, range 64, base 0xf7e0, size 131072, enabled
cap 01[40] = powerspec 3  supports D0 D1 D3  current D0
cap 05[50] = MSI supports 4 messages, 64 bit, vector masks 
cap 10[70] = PCI-Express 2 endpoint max data 128(128) link x1(x1)
 speed 2.5(2.5) ASPM disabled(L0s/L1)
ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected
ecap 0002[140] = VC 1 max VC0
ecap 0003[300] = Serial 1 

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 165146] [net80211] Net802.11 Fragment number is assigned 1 (should be 0) when fragmenting a frame

2016-02-23 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165146

Andriy Voskoboinyk  changed:

   What|Removed |Added

 CC||a...@freebsd.org
 Resolution|--- |Unable to Reproduce
 Status|In Progress |Closed

--- Comment #2 from Andriy Voskoboinyk  ---
(In reply to monthadar from comment #0)
> I found that in FreeBSD current the first fragment will have a
> fragment number = 1 in function ieee80211_fragment.

Sequence/fragment number for the first fragment (m0) is left unmodified;
fragno (1+) is applied for subsequent fragments only.

Tested with Intel 3945BG (fragthreshold 300 + some printf() code for
sequence/fragment number monitoring) - everything works as intended.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 207445] net80211 Atheros AR938x: non-working WiFi hostap since ~ January

2016-02-23 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207445

Adrian Chadd  changed:

   What|Removed |Added

 CC||adr...@freebsd.org

--- Comment #1 from Adrian Chadd  ---
hi,

can you narrow down when it happened? A bunch of wifi infrastructure changed
then and i have been too preoccupied with life(tm) lately to be able to keep on
top of things and regularly test things.

(Which will change Very Soon Now, thankfully..)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"