Karun Gahlawat wrote:
> sweet! now it says connected!
:-D
> if only i can set up my dsn / dhcp now.. i can start exploring the beast!
>
> any pointers where I can see instructions  on setting up the ip / 
> dhcp? browser is unable to connect and complains about missing ip and 
> dns status.
>
> also, is it possible to add a script or binary to the start up so that 
> it scans and connect automatically? just like the 2008.05 installer 
> picks it up (in the non wpa mode)!!
You can use nwam, which will do all these for you magicly, it's the way 
2008.05 intaller do.
# svcadm disable svc:/network/physical:default
# svcadm enable svc:/network/physical:nwam

Now, nwam will do everything for you, including connection, get IP, and 
setup your DNS, cool, ha!
Note that you need do nothing, including manual dladm command, ;-)

--
Quaker
>
> appreciate your help!
>
>
> On Tue, Sep 2, 2008 at 9:20 PM, Quaker Fang <Quaker.Fang at sun.com 
> <mailto:Quaker.Fang at sun.com>> wrote:
>
>     Karun Gahlawat wrote:
>     > Thanks Quaker!
>     > AP is set to WPA2-PSK (WPA2 Personal) and encryption is TKIP OR AES.
>     > wificonfig is scanning the essid as WEP encryption.
>     wificonfig only works with ath v0.5 on the laptop community, can't
>     support other drivers, including iwk.
>     Please use dladm, it's very easy:
>
>     # dladm create-secobj -c mykey
>     -----> input your PSK same as AP <---------
>
>     # dladm connect-wifi -e ESSID -k mykey iwk0
>
>     Note that if you use WPA2-PSK, OpenSolaris 2008.05 is not enough, you
>     need upgrade to OpenSolaris build 93+.
>     If you use WPA-PSk, OpenSolaris 2008.05 is okay.
>     > Creating a profile with encryption set to TKIP and key_mgmt as
>     WPA-PSK
>     > fails on operation not poermitted.
>     > Also, while shutting down, I saw iwk0 driver init failure messages.
>     > How can I / if possible, get involved in this driver interface? I
>     > would like to contribute if possible!
>     See above, wificonfig is not supported, please use dladm. ;-)
>
>     --
>     Quaker
>     >
>     > On Mon, Sep 1, 2008 at 10:59 PM, Quaker Fang
>     <Quaker.Fang at sun.com <mailto:Quaker.Fang at sun.com>
>     > <mailto:Quaker.Fang at sun.com <mailto:Quaker.Fang at sun.com>>> wrote:
>     >
>     >     Hi Karun,
>     >
>     >     Karun Gahlawat wrote:
>     >     > All!
>     >     >
>     >     > trying to set iwk0 for my intel 4965 agn card. The card is
>     >     recognized
>     >     > but not with the same pci # (4429, 4430 ?) stated on the
>     driver
>     >     page.
>     >     > this interface is always down. although no issues plumbing
>     it in.
>     >     >
>     >     >
>     >     > Running on hp pavillion dv9700t with 4G ram. router is linksys
>     >     wrt300n.
>     >     > On initial install of this router, the wireless security
>     >     settings were
>     >     > on the legacy WPA PSK with TKIP encryption only mode. This
>     >     worked and
>     >     > 2008.05 installer picked it up right away.
>     >     >
>     >     > I changed the router to WPA2 mode to support both TKIP and
>     EAP mode
>     >     > with encryption still on TKIP (Have an old pc that does
>     not support
>     >     > key refreshes).
>     >     Solaris WiFi drivers (including iwk) don't support WPA-EAP
>     mode, you
>     >     need change the AP to WPA[2]-PSK mode.
>     >
>     >     --
>     >     Quaker
>     >     >
>     >     > Now, I am on solaris Express build 96 but this interface
>     (iwk0)
>     >     would
>     >     > not come up. One this I noticed that the encryption is ALWAYS
>     >     > identified as WEP. I guess this is the problem and the
>     driver /
>     >     kernel
>     >     > is unable to identify the right chipset.
>     >     > I tried installing wpa supplicant but it fails on some ld
>     library
>     >     > error ( yes.. i do have the greater version.. it still
>     fails but
>     >     that
>     >     > is another issue)
>     >     >
>     >     > I don't have the dev env set up yet (waiting for a wireless
>     >     > connection!) so can't really contribute to the new
>     specifications (N
>     >     > and WPA2). The driver page mentions it supports TKIP which is
>     >     what the
>     >     > router is set to.
>     >     > I am not sure what's wrong here! Tired of sticking to a
>     corner with
>     >     > the ethernet :(
>     >     >
>     >     > Dump of outputs from wificonfig and prtconf.
>     >     >
>     >     > # wificonfig showprofile
>     >     > [home]
>     >     > essid=innovresearch
>     >     > key_mgmt=WPA-EAP
>     >     > pairwise=TKIP
>     >     > group=TKIP
>     >     > encryption=none
>     >     > psk=*****
>     >     >
>     >     >
>     >     > # wificonfig scan
>     >     >
>     >     > essid bssid type encryption signallevel
>     >     >
>     >     > innovresearch 00:1d:7e:e4:fe:db access point wep 15
>     >     >
>     >     >
>     >     > # wificonfig connect home
>     >     >
>     >     > wificonfig: failed to set 'psk' for Operation not supported
>     >     >
>     >     > wificonfig: failed to set 'key_mgmt' for Operation not
>     supported
>     >     >
>     >     >
>     >     > wificonfig: failed to connect to profile 'home'
>     >     >
>     >     >
>     >     >
>     >     >
>     >     >
>     >     > -----------prtconf output
>     >     >
>     >     >
>     >     >
>     >     > System Configuration:
>     >     > Sun Microsystems i86pc
>     >     >
>     >     > Memory size: 4095 Megabytes
>     >     >
>     >     > System Peripherals
>     >     > (Software Nodes):
>     >     >
>     >     > i86pc
>     >     > scsi_vhci, instance #0
>     >     > isa, instance #0
>     >     > motherboard (driver not attached)
>     >     > i8042
>     >     > , instance #0
>     >     > keyboard , instance #0
>     >     > mouse, instance #0
>     >     > pit_beep, instance #0
>     >     > pci, instance #0
>     >     > pci103c,30cc, instance #0
>     >     > pci8086,2a01, instance #0
>     >     > display, instance #0
>     >     > pci103c,30cc, instance #0
>     >     > pci103c,30cc, instance #1
>     >     > pci103c,30cc, instance #0
>     >     > pci103c,30cc (driver not attached)
>     >     > pci8086,283f, instance #1
>     >     > pci8086,1100, instance #0
>     >     > pci8086,2841, instance #2
>     >     > pci8086,2849, instance #3
>     >     > pci103c,30cc, instance #0
>     >     > pci103c,30cc, instance #2
>     >     > pci103c,30cc, instance #3
>     >     > device, instance #1
>     >     > pci103c,30cc, instance #4
>     >     > device, instance #2
>     >     > pci103c,30cc, instance #1
>     >     > miscellaneous, instance #0
>     >     > video, instance #0
>     >     > pci8086,2448, instance #0
>     >     > pci103c,30cc, instance #0
>     >     > pci103c,30cc (driver not attached)
>     >     > pci103c,30cc (driver not attached)
>     >     > pci103c,30cc (driver not attached)
>     >     > pci103c,30cc (driver not attached)
>     >     > pci103c,30cc (driver not attached)
>     >     > pci-ide, instance #0
>     >     > ide, instance #0
>     >     > sd, instance #2
>     >     > ide (driver not attached)
>     >     > pci103c,30cc, instance #0
>     >     > disk, instance #0
>     >     > disk, instance #1
>     >     > pci103c,30cc (driver not attached)
>     >     > iscsi, instance #0
>     >     > pseudo, instance #0
>     >     > options, instance #0
>     >     >
>     >     > agpgart, instance #0
>     >     > xsvc, instance #0
>     >     > used-resources (driver not attached)
>     >     > cpus, instance #0
>     >     > cpu, instance #0
>     >     > cpu, instance #1
>     >     >
>     >     >
>     >     >
>     >     >
>     >    
>     ------------------------------------------------------------------------
>     >     >
>     >     > _______________________________________________
>     >     > laptop-discuss mailing list
>     >     > laptop-discuss at opensolaris.org
>     <mailto:laptop-discuss at opensolaris.org>
>     >     <mailto:laptop-discuss at opensolaris.org
>     <mailto:laptop-discuss at opensolaris.org>>
>     >     >
>     >
>     >
>
>


Reply via email to