Kanwaljit Singh Wrote:
> Hi,
>
> "/way to verify whether this driver works is to set up your AP to none 
> or wep encryption firstly/..."  How do I do this ?
>
> On wpi, Only at home I cannot connect to my broadband modem.  :-(
>
>   
Because your home broadcom AP is WPA enabled, and it's possible WPA2. As 
I mentioned, it's not supported by snv_77. If you can access your home 
AP, you can change its configuration. Or, you can upgrade your system to 
the latest build.
-Cecilia
> ========================
> wpi & solaris build version....
> ========================
> bash-3.2#uname -a
> SunOS mysolaris 5.11 snv_79a i86pc i386 i86pc
>
>
> bash-3.2# pkginfo -i SUNWwpi
> system      SUNWwpi Intel(R) PRO/Wireless 3945ABG driver
> bash-3.2# pkginfo -l SUNWwpi
>    PKGINST:  SUNWwpi
>       NAME:  Intel(R) PRO/Wireless 3945ABG driver
>   CATEGORY:  system
>       ARCH:  i386
>    VERSION:  11.11,REV=2008.01.05.16.07
>    BASEDIR:  /
>     VENDOR:  Sun Microsystems, Inc.
>       DESC:  Intel(R) PRO/Wireless 3945ABG driver
>     PSTAMP:  elpaso20080105161015
>   INSTDATE:  Jul 31 2008 21:01
>    HOTLINE:  Please contact your local service provider
>     STATUS:  completely installed
>      FILES:        5 installed pathnames
>                    3 shared pathnames
>                    3 directories
>                    2 executables
>                  649 blocks used (approx)
>
>
>
>
> /Regards
> Kanwaljit Singh
>
>
>
>
> cecilia wrote:
>   
>> Kanwaljit Singh Wrote:
>>     
>>> Hi,
>>>
>>> bash-3.2# dladm create-secobj -c wpa sec_obj_name                  
>>> provide value for 'sec_obj_name': **********
>>> confirm value for 'sec_obj_name': **********
>>>
>>> bash-3.2# dladm connect-wifi -e Broadcom -k sec_obj_name
>>> dladm: cannot connect link 'wpi0': operation timed out
>>>
>>>       
>> which version wpi and which build of solaris are you using now. If it 
>> is early build(earlier then 77),  wpi doesn't support wpa yet. If it's 
>> snv77 - snv94, it supports WPA/PSK only, if it's snv_94+, it support 
>> WPA2.
>>
>> So, please also check the correct build and version. Another simple 
>> way to verify whether this driver works is to set up your AP to none 
>> or wep encryption firstly.
>>
>> -Cecilia
>>     
>>> /Regards
>>> Kanwaljit
>>>
>>> cecilia wrote:
>>>       
>>>> To use dladm, you don't need to create any profile..
>>>> Just try to connect this broadcom ap then. Following:
>>>> #dladm create-secobj -c wpa <security object name - anyone you like>
>>>> ...input your wpa key here
>>>> #dladm connect-wifi -e Broadcom -k <security object name>
>>>> then, you just need get a dhcp address or assign a static IP.
>>>>
>>>> -Cecilia
>>>>
>>>> Kanwaljit Singh wrote:
>>>>         
>>>>> OK.. I deleted the profile "Broadcom' and created it again... This 
>>>>> time /*scan-config*/ is giving some output....
>>>>>
>>>>> bash-3.2# dladm scan-wifi
>>>>> LINK       ESSID               BSSID/IBSSID      SEC    STRENGTH   
>>>>> MODE   SPEED
>>>>> wpi0       Broadcom            0:8:5c:ef:2f:34   wpa    excellent  
>>>>> g      54Mb
>>>>>
>>>>>
>>>>> /Cheers
>>>>> Kanwaljit
>>>>>
>>>>>
>>>>>
>>>>> Kanwaljit Singh wrote:
>>>>>  
>>>>>           
>>>>>> *<Kanwaljit>*The command just comes back without any results !
>>>>>> ==================
>>>>>> /*bash-3.2# dladm scan-wifi  bash-3.2#
>>>>>> */==========================================
>>>>>>
>>>>>> *<Kanwaljit>*/ The I tried inetmenu/ and the output is as follows:
>>>>>> =========================
>>>>>> /*bash-3.2# inetmenu &/usr/sbin/wificonfig: failed to connect to 
>>>>>> profile 'Broadcom'
>>>>>> ifconfig: wpi0: wait timed out, operation still pending...
>>>>>> */=========================
>>>>>>
>>>>>>
>>>>>> *<Kanwaljit>*/ After this, "ifconfig -a" shows that interface is 
>>>>>> there, but no ip address is assigned
>>>>>>
>>>>>> /=========================
>>>>>>
>>>>>> /*bash-3.2# ifconfig -a
>>>>>> lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> 
>>>>>> mtu 8232 index 1
>>>>>>        inet 127.0.0.1 netmask ff000000
>>>>>> wpi0: flags=201004803<UP,BROADCAST,MULTICAST,DHCP,IPv4,CoS> mtu 
>>>>>> 1500 index 4
>>>>>>        inet 0.0.0.0 netmask ff000000
>>>>>>        ether 0:1b:77:94:3a:15
>>>>>> lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> 
>>>>>> mtu 8252 index 1
>>>>>>        inet6 ::1/128*/
>>>>>>
>>>>>>
>>>>>>
>>>>>> /Regards
>>>>>> Kanwaljit Singh
>>>>>>
>>>>>>
>>>>>>
>>>>>> Cecilia Hu wrote:
>>>>>>  
>>>>>>             
>>>>>>> Kanwaljit Singh Gujral Wrote:
>>>>>>>    
>>>>>>>               
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> In my laptop, I have two interfaces in my laptop...  ethernet 
>>>>>>>> (myk) and wireless (wpi)
>>>>>>>>
>>>>>>>> With help from this forum I am now successful in configuring myk 
>>>>>>>> (see attached mails).  But for wpi, I am still having SOME 
>>>>>>>> issues...    The card is : /*Intel/R -  PRO/Wireless 3945 
>>>>>>>> Network Controller_ card.
>>>>>>>>
>>>>>>>> */Using this /*wpi*/ interface, I can connect from sun office & 
>>>>>>>> some of other places. Actually, I was able to connect during my 
>>>>>>>> stay in a hotel as well !!!   But when I am at home, I cannot 
>>>>>>>> connect to my broadband modem.
>>>>>>>>         
>>>>>>>>                 
>>>>>>> What's the wpi scan result output? can it find the AP at your 
>>>>>>> home?  by
>>>>>>> command "dladm scan-wifi"
>>>>>>>
>>>>>>> -Cecilia
>>>>>>>
>>>>>>>    
>>>>>>>               
>>>>>>>> I am in India & I am using Airtel broadband connection.
>>>>>>>> _______________________________________________
>>>>>>>> laptop-discuss mailing list
>>>>>>>> laptop-discuss at opensolaris.org
>>>>>>>>         
>>>>>>>>                 
>>>>>>>       
>>>>>>>               
>>>>>>     
>>>>>>             
>>>>> _______________________________________________
>>>>> laptop-discuss mailing list
>>>>> laptop-discuss at opensolaris.org
>>>>>   
>>>>>           
>
> _______________________________________________
> laptop-discuss mailing list
> laptop-discuss at opensolaris.org
>   


Reply via email to