Hi,
> Please use command `cryptoadm list` to see if aes is in the output.
bernd.akuma ~ > cryptoadm list
User-level providers:
Provider: /usr/lib/security/$ISA/pkcs11_kernel.so
Provider: /usr/lib/security/$ISA/pkcs11_softtoken.so
Kernel software providers:
des
aes
arcfour
blowfish
ecc
sha1
sha2
md4
md5
rsa
swrand
Kernel hardware providers:
So yes aes is there and seems to work most of the time (as I'm running the
access point with WPA2 with AES encryption).
> It seems the driver is in disorder, so I wonder what the
> driver was doing when the symptoms happened.
That I do not know (yet). I can trigger the failure by bursts of network
activity, like starting firefox with ~15tabs opened on startup. Streaming or
continuous downloads (sxce iso) work most of the time. sometimes it drops the
connection rather randomly.
What I noticed is that the nwam applett in Gnome notifies me of new available
wifi networks shortly after the disconnect, but doesn't reconnect by itself.
Could it be the code scanning for available networks steps on the toes of the
current active connection in whatever way?
> And have you found the same symptoms on
> snv105 or other builds? Thanks.
I've seen it on SXCE 106 and 107. I think I started with 106 on this (new)
notebook.
> > 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.
ok. just a little misleading.
bernd
--
This message posted from opensolaris.org
