Thanks Moinak for the reply which evidently hasn't shown up here yet?? The link you gave me shows the output of 'wificonfig' when not run with any following syntax!
Hence again, a profile was created by using: 'wificonfig createprofile Cisco essid=Cisco encryption=wep wepkey1=abcd......' Then initiating a connect sequence: 'wificonfig connect Cisco' Bring up the wireless interface: 'ifconfig iwi0 up' Finally use dhcp to obtain IP information: 'ifconfig iwi0 dhcp' Before the upgrades it connected but as soon as 'ifconfig [...] dhcp' was run it disassociated. Now I can't even connect. Using Sun literature I found a was to do this using 'dladm connect-wifi' which also didn't work. As it is the syntax I am using to create the profile is the SAME as using SXCE which theoretically should have the same wificonfig version and same ipw driver version. Only now I cannot connect at all :-( Using SXCE I had to always plumb the interface first then bring down the rtls0 wired interface before it would allow me to obtain IP information using dhcp. That was ok as I could at least connect but now I cannot at all!! I have read that wificonfig v0.2 is needed in order to use wep. With the updates that probably is what is being run or a later version but why won't it even associate? ---------------- P.s. for my other post about multimedia I will post the information soon, currently I am booted into Linux as where the laptop is has no wired connection making it impossible if I reboot to send or receive anything. Also there seems to be really strange delay with these forums?? Is it being cached somewhere along the way I wonder as I am receiving emails acknowledgments of new posts but nothing showing..... oh well teething problems I guess
