Hi Sean, The root cause of the problem is the lacking of SUNWcry package, but the package you download/install is not the correct one, which is for solaris 10 and solaris nevada(lower build version) using openssl 0.9.7.
Your nevada version is b66, it uses the openssl 0.9.8, so you should download the corresponding SUNWcry package; you can ask this in security-discuss alias. -- Quaker Sean Liu wrote: >Downloaded and installed the encryption package. Still no luck. > >bash-3.00# pkginfo -l SUNWcry > PKGINST: SUNWcry > NAME: Crypt Utilities > CATEGORY: system > ARCH: i386 > VERSION: 11.10.0,REV=2005.01.21.16.34 > BASEDIR: / > VENDOR: Sun Microsystems, Inc. > DESC: utilities for software encryption and decryption > PSTAMP: gauthier20050121164632 > INSTDATE: Aug 15 2007 10:04 > HOTLINE: Please contact your local service provider > STATUS: completely installed > FILES: 25 installed pathnames > 16 shared pathnames > 11 directories > 9 executables > 2408 blocks used (approx) > >bash-3.00# pkginfo -l SUNWcryr > PKGINST: SUNWcryr > NAME: Solaris Root Crypto > CATEGORY: system > ARCH: i386 > VERSION: 11.10.0,REV=2005.01.21.16.34 > BASEDIR: / > VENDOR: Sun Microsystems, Inc. > DESC: Solaris kernel root software encryption and decryption > PSTAMP: gauthier20050121164633 > INSTDATE: Aug 15 2007 10:04 > HOTLINE: Please contact your local service provider > STATUS: completely installed > FILES: 9 installed pathnames > 3 shared pathnames > 3 directories > 6 executables > 260 blocks used (approx) > >Here's the connect.d output: >bash-3.00# ./connect.d |tee connect.d.out >====================authentication request frame begin========================= >da = 00:03:2f:39:fa:94. sa = 00:14:a4:85:71:80 >bssid = 00:03:2f:39:fa:94 >essid = sean >auth mode = open >auth seq No = 0x1 >====================authentication request frame end==================== >====================authentication response frame begin================= >da = 00:14:a4:85:71:80. sa = 00:03:2f:39:fa:94 >bssid = 00:03:2f:39:fa:94 >auth seq No = 0x2 >status code = 0x0 >====================authentication request frame end==================== >====================association request frame begin===================== >da = 00:03:2f:39:fa:94. sa = 00:14:a4:85:71:80 >bssid = 00:03:2f:39:fa:94 >essid = sean >capability info = 0x431 > bit 0: AP > bit 4: wep > bit 5: short preamble > bit 10: short slot time >====================association request frame end======================= >====================association response frame begin==================== >da = 00:14:a4:85:71:80. sa = 00:03:2f:39:fa:94 >bssid = 00:03:2f:39:fa:94 >status code = 0x0 >association ID = 0x2 >capability info = 0x431 > bit 0: AP > bit 4: wep > bit 5: short preamble > bit 10: short slot time >====================association response frame end====================== > > >bash-3.00# dladm connect-wifi -e sean -k sean ath0 >bash-3.00# dladm show-wifi >LINK STATUS ESSID SEC STRENGTH MODE SPEED >ath0 connected sean wpa very good g 36Mb > >However DHCP still can't get the IP address, but I can manually set the IP >address and get on the network, the connect is kinda flaky though. It fails >from time to time. >I'll have to do following to reactivate the connection: >bash-3.00# ifconfig ath0 down >bash-3.00# dladm disconnect-wifi ath0 >bash-3.00# dladm connect-wifi -e sean -k sean ath0 >bash-3.00# ifconfig ath0 192.168.0.200/24 up >bash-3.00# >bash-3.00# ping 192.168.0.1 >192.168.0.1 is alive > > >Any idea? > >Tia, > >Sean > > >This message posted from opensolaris.org >_______________________________________________ >laptop-discuss mailing list >laptop-discuss at opensolaris.org > >
