[Bug 161035] [ieee80211] Incorrect number describing 11ng MCS rate in ifconfig -v?

2019-02-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=161035

--- Comment #3 from commit-h...@freebsd.org ---
A commit references this bug:

Author: avos
Date: Sun Feb  3 03:03:00 UTC 2019
New revision: 343698
URL: https://svnweb.freebsd.org/changeset/base/343698

Log:
  ifconfig(8): display management / multicast wlan(4) rates properly

  For 11n / 11ac we are still using non-11n rates for management and
  multicast traffic by default; check 'MCS rate' bit to determine how
  to print them correctly.

  PR:   161035
  MFC after:1 week

Changes:
  head/sbin/ifconfig/ifieee80211.c

-- 
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 161035] [ieee80211] Incorrect number describing 11ng MCS rate in ifconfig -v?

2019-02-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=161035

Andriy Voskoboinyk  changed:

   What|Removed |Added

 CC||a...@freebsd.org
 Status|Open|In Progress
  Flags||mfc-stable10?,
   ||mfc-stable11?,
   ||mfc-stable12?
   Assignee|wirel...@freebsd.org|a...@freebsd.org

-- 
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"


No association with WPA2 wireless lan sometimes (11.2)

2019-02-02 Thread Christian Barthel
Hello, 

I am using FreeBSD 11.2 on a Thinkpad X230 (dmesg attached).  I am using
a WPA2 wireless lan with iwn and wpa_supplicant.conf. This configuration
works very well - sometimes.  But at other times, I can't associate with
the access point and I don't understand the reason why it fails.

I've tested this with iwn0/wlan0 and attached a verbose log
(wpa.debug.iwn0.txt) while wpa_supplicant tried to authenticate.  I
don't know why the authentication timed out?  Other clients (Android,
Linux) are working.  Attached is also the "ifconfig wlan0 list scan"
listing.

To rule out a damaged iwn chip on the notebook, I tried the same with an
USB dongle (urtwn0) - but the result was the same.  It doesn't associate
and the authentication times out.  Attached is a verbose log of
wpa_supplicant.conf (wpa.debug.urtwn0.txt).  

As mentioned earlier, the Access Point works with other clients
(Android) and even the same configuration runs fine for hours on some
days.  The configuration of wpa_supplicant.debug.conf is attached.

Interestingly enough, when I am turning on the "Wifi Bridge" on an
Android phone, the WPA2 connection to the phone worked always.  On the
other hand, I've seen similar authentication failures on other APs
also.

Has anyone similar issues when using FreeBSD and wifi?

Am I missing something in my wpa_supplicant.conf? 

How can I resolve or debug this further?  Am I missing something in the
wpa_supplicant log? 

Thanks, 
-- 
Christian Barthel

wpa_supplicant v2.5
Successfully initialized wpa_supplicant
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.debug.conf' driver 
'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.debug.conf' -> 
'/etc/wpa_supplicant.debug.conf'
Reading configuration file '/etc/wpa_supplicant.debug.conf'
ctrl_interface='/var/run/wpa_supplicant'
eapol_version=2
ap_scan=1
fast_reauth=1
Line: 6 - start of a new network block
ssid - hexdump_ascii(len=11):
 57 4c 41 4e 2d 31 30 38 38 30 33  WLAN-108803 
scan_ssid=1 (0x1)
PSK (ASCII passphrase) - hexdump_ascii(len=16): [REMOVED]
priority=5 (0x5)
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 5
   id=0 ssid='WLAN-108803'
wpa_driver_bsd_capa: drivercaps=0x0581e201,cryptocaps=0x
Add interface wlan0 to a new radio N/A
wlan0: Own MAC address: 6c:88:14:dd:02:d0
bsd_set_key: alg=0 addr=0x0 key_idx=0 set_tx=0 seq_len=0 key_len=0
bsd_del_key: key_idx=0
bsd_set_key: alg=0 addr=0x0 key_idx=1 set_tx=0 seq_len=0 key_len=0
bsd_del_key: key_idx=1
bsd_set_key: alg=0 addr=0x0 key_idx=2 set_tx=0 seq_len=0 key_len=0
bsd_del_key: key_idx=2
bsd_set_key: alg=0 addr=0x0 key_idx=3 set_tx=0 seq_len=0 key_len=0
bsd_del_key: key_idx=3
wpa_driver_bsd_set_countermeasures: enabled=0
wlan0: RSN: flushing PMKID list in the driver
wlan0: Setting scan request: 0.10 sec
wlan0: WPS: UUID based on MAC address: 10dc295d-49d2-509a-af4c-4f7531c8e3f2
ENGINE: Loading dynamic engine
ENGINE: Loading dynamic engine
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
Using existing control interface directory.
wlan0: Added interface wlan0
wlan0: State: DISCONNECTED -> DISCONNECTED
wlan0: State: DISCONNECTED -> SCANNING
Scan SSID - hexdump_ascii(len=11):
 57 4c 41 4e 2d 31 30 38 38 30 33  WLAN-108803 
wlan0: Starting AP scan for wildcard SSID
wlan0: Add radio work 'scan'@0x801ce7000
wlan0: First radio work item in the queue - schedule start immediately
wlan0: Starting radio work 'scan'@0x801ce7000 after 0.48 second wait
wpa_driver_bsd_set_wpa: enabled=1
wpa_driver_bsd_set_wpa_internal: wpa=3 privacy=1
EAPOL: disable timer tick
wlan0: Event SCAN_RESULTS (3) received
Received 0 bytes of scan results (0 BSSes)
wlan0: BSS: Start scan result update 1
BSS: last_scan_res_used=0/0
wlan0: New scan results available (own=0 ext=0)
wlan0: Radio work 'scan'@0x801ce7000 done in 2.083587 seconds
wlan0: No suitable network found
wlan0: Setting scan request: 5.00 sec
Scan SSID - hexdump_ascii(len=11):
 57 4c 41 4e 2d 31 30 38 38 30 33  WLAN-108803 
wlan0: Starting AP scan for wildcard SSID
wlan0: Add radio work 'scan'@0x801ce7000
wlan0: First radio work item in the queue - schedule start immediately
wlan0: Starting radio work 'scan'@0x801ce7000 after 0.31 second wait
wpa_driver_bsd_set_wpa: enabled=1
wpa_driver_bsd_set_wpa_internal: wpa=3 privacy=1
wlan0: Event SCAN_RESULTS (3) received
Received 672 bytes of scan results (2 BSSes)
Sorted scan results
d4:21:22:3f:50:35 freq=5180 qual=33 noise=-95 level=-79 flags=0x0 age=0 est=1000
IEs - hexdump(len=384): 00 0b 57 4c 41 4e 2d 31 30 38 38 30 33 01 08 8c 12 98 
24 b0 48 60 6c 2a 01 00 00 0b 57 4c 41 4e 2d 31 30 38 38 30 33 01 08 8c 12 98 
24 b0 48 60 6c 07 34 44 45 20 24 01 17 28 01 17 2c 01 17 30 01 17 34 01 17 38 
01 17 3c 01 17 40 01 17 64 

[Bug 206801] iwn(4) page fault on netif restart

2019-02-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206801

--- Comment #2 from Andriy Voskoboinyk  ---
A bit of clarification: it wasn't double free; NULL was passed to
firmware_put() on the second (parallel) iwn_init_locked() run.

-- 
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 195433] iwn(4) crashing when wlan device is brought up, CA-N-6200

2019-02-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195433

Andriy Voskoboinyk  changed:

   What|Removed |Added

 CC||dte...@freebsd.org

--- Comment #3 from Andriy Voskoboinyk  ---
*** Bug 206801 has been marked as a duplicate of this bug. ***

-- 
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 206801] iwn(4) page fault on netif restart

2019-02-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206801

Andriy Voskoboinyk  changed:

   What|Removed |Added

 CC||a...@freebsd.org
 Status|New |Closed
   Keywords||panic
 Resolution|--- |DUPLICATE
  Flags|mfc-stable10?   |mfc-stable10-

--- Comment #1 from Andriy Voskoboinyk  ---
Fixed in base r314234 - iwn_init() was called multiple times and, due to race
during firmware upload, firmware_put() was called on the same pointer few
times.

*** This bug has been marked as a duplicate of bug 195433 ***

-- 
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"