Gosh, over six weeks old and nor reply? Or maybe someone replied to
Sender (samankaya?) ? Anyway...
Sabi ni Kaya noong Sat, Jun 13, 2009 at 4:06 AM:
> I couldn't seem to login to my wireless network though?? I used the same
> syntax as with SXCE and I manage to connect to my access point briefly, after
> trying to get an IP address with DHCP the machine seems to disassociate
> itself. This may just be a case of updating the packages but for reference
> sake:
>
> #ifconfig -a {list all interfaces - IP addresses at 0.0.0.0 for rtls0 and
> iwi0}
> #wificonfig createprofile Cisco essid=SSID wepkey1=WEP_KEY_HEX_40_BIT
> wepkeyindex=1 authmode=opensystem encryption=wep
> {create a profile called Cisco with 40 bit wep key and open system
> authentication as opposed to shared wep key}
> #ifconfig rtls0 down {take the wired ethernet interface down}
> #ifconfig iwi0 up {bring my wireless NIC up}
> #ifocnfig iwi0 dhcp {tell the wireless card to use dhcp for acquiring layer 3
> information}
> #ifconfig -a {should show IP given by dhcp but is still 0.0.0.0}
>
> I used:
> #wificonfig -i iwi0 showstatus
> to verify the wireless was connected initially and it was but after running
> ifconfig iwi0 dhcp it disassociated from the access-point??
I *may* have been in a similar situation. From my blog:
http://descasa.i.ph/blogs/descasa/2009/01/08/wifi-opensolaris-and-the-thinkpad-sl400/
<quote>
One issue I was having with my WiFi was that on bootup, it connected
to my NETGEAR wireless access point (AP) but I wasn?t connecting to
any Internet sites. When I noticed this, the first thing I did on
startup was open up a terminal window and ping google.com. I?d get an
unknown host error, which means something with the DNS. I?d then bring
up inetmenu and apply DHCP on iwh0, my wireless interface. That
worked, but it was a pain because my wireless should go up without
manual intervention.
So, I moved around the lines in my /etc/driver_aliases so that iwh
?pciex8086,4237? would be the first line, and so far that seems to
have done it.
</quote>
You might look into that and see if that solves your problem.
> Ah one other thing is that there is a non-standard implementation of GRUB on
> this machine for the bootloader. I can't find /boot/grub/menu.lst as I need
> to chain load KUbuntu Linux of which I've created a 10GB partition just while
> I sort out the teething problems with Solaris.
It's in /rpool/boot/grub -- of course, you have to pfexec in order to
edit this, because the entire directory belongs to root. But you knew
that :)
--
Daniel O. Escasa
independent IT consultant and writer
contributor, Free Software Magazine (http://www.freesoftwaremagazine.com)
personal blog at http://descasa.i.ph
Twitter page at http://www.twitter.com/silverlokk
If we choose being kind over being right, we will be right every time.
