Bernd Markgraf ??: > I see the same symptoms on snv106 and snv107 with the iwh driver. > dmesg gives > Feb 8 21:55:19 akuma genunix: [ID 256460 kern.warning] WARNING: > aes_ccm_encrypt failed (1d) > Please use command `cryptoadm list` to see if aes is in the output. It seems the driver is in disorder, so I wonder what the driver was doing when the symptoms happened. And have you found the same symptoms on snv105 or other builds? Thanks. > Feb 8 21:55:19 akuma mac: [ID 486395 kern.info] NOTICE: iwh0 link down > Feb 8 21:55:19 akuma in.routed[501]: [ID 238047 daemon.warning] interface > iwh0 to 192.168.2.23 turned off > Feb 8 21:55:20 akuma wpad[2868]: [ID 702911 daemon.notice] Failed to disable > WPA in the driver. > Feb 8 21:55:20 akuma nwamd[2858]: [ID 459249 daemon.error] > connect_chosen_lan: connect to 'BERNY' failed on 'iwh0': operation failed > Feb 8 21:55:20 akuma nwamd[2858]: [ID 200354 daemon.warning] could not > connect to chosen WLAN BERNY on iwh0, going to auto-conf > Feb 8 21:55:27 akuma genunix: [ID 634369 kern.warning] WARNING: > ieee80211_event: door_ki_open(/var/run/wpa_door_iwh0) failed > > > when issuing a dladm connect-wifi (nwam doesn't come back by itself for > whatever reason) you dtrace script gives me > ====================authentication request frame > begin========================= > da = 00:1a:4f:93:1b:74. sa = 00:21:5d:af:cc:42 > bssid = 00:1a:4f:93:1b:74 > essid = BERNY > auth mode = open > auth seq No = 0x1 > ====================authentication request frame end==================== > ====================authentication response frame begin================= > da = 00:21:5d:af:cc:42. sa = 00:1a:4f:93:1b:74 > bssid = 00:1a:4f:93:1b:74 > auth seq No = 0x2 > status code = 0x0 > ====================authentication request frame end==================== > ====================association request frame begin===================== > da = 00:1a:4f:93:1b:74. sa = 00:21:5d:af:cc:42 > bssid = 00:1a:4f:93:1b:74 > essid = BERNY > capability info = 0x411 > bit 0: AP > bit 4: wep > bit 10: short slot time > ====================association request frame end======================= > ====================association response frame begin==================== > da = 00:21:5d:af:cc:42. sa = 00:1a:4f:93:1b:74 > bssid = 00:1a:4f:93:1b:74 > status code = 0x0 > association ID = 0x2 > capability info = 0x451 > bit 0: AP > bit 4: wep > bit 6: PBCC > bit 10: short slot time > ====================association response frame end====================== > ====================authentication request frame > begin========================= > da = 00:1a:4f:93:1b:74. sa = 00:21:5d:af:cc:42 > bssid = 00:1a:4f:93:1b:74 > essid = BERNY > auth mode = open > auth seq No = 0x1 > ====================authentication request frame end==================== > ====================authentication response frame begin================= > da = 00:21:5d:af:cc:42. sa = 00:1a:4f:93:1b:74 > bssid = 00:1a:4f:93:1b:74 > auth seq No = 0x2 > status code = 0x0 > ====================authentication request frame end==================== > ====================association request frame begin===================== > da = 00:1a:4f:93:1b:74. sa = 00:21:5d:af:cc:42 > bssid = 00:1a:4f:93:1b:74 > essid = BERNY > capability info = 0x411 > bit 0: AP > bit 4: wep > bit 10: short slot time > ====================association request frame end======================= > ====================association response frame begin==================== > da = 00:21:5d:af:cc:42. sa = 00:1a:4f:93:1b:74 > bssid = 00:1a:4f:93:1b:74 > status code = 0x0 > association ID = 0x2 > capability info = 0x451 > bit 0: AP > bit 4: wep > bit 6: PBCC > bit 10: short slot time > ====================association response frame end====================== > > > btw why does it give bit 4 as wep when I run wpa? > It is just a mark which means the AP is a encrypted.
------ Thanks, Felix > bernd >
