great! glad it helped.

if you could post the contents of your (/etc/sysconfig/network/ifcfg-wlan0) file i could compare it against mine and see where the problem is, thats causing me to have to rerun YAst each time.


oh wait a minute, you have the centrino wifi set up , so its all built in. i have a pcmcia linksys card, so i think the way the services load up, where it brings up the network 1st and then probes for pcmcia later, is the reason i have to rerun YAST again once it boots up.

I'll have to try re numbering the services as suggested in an earlier post and see if that helps. You would think these sorts of issues would be simple enough for a compnay like SuSE to figure out!! i guess not.

Although i have to commend linuxant support for their suggestion and rather quick response.

I bet you're right about the bootup sequence of services.
Just in case here's the content of icfg-wlan0:

BOOTPROTO='dhcp'
BROADCAST='10.0.1.255'
IPADDR='10.0.1.239'
MTU=''
NETMASK='255.255.255.0'
NETWORK='10.0.1.0'
REMOTE_IPADDR=''
STARTMODE='onboot'
UNIQUE=''
WIRELESS_ESSID='yourESSIDhere'
WIRELESS_KEY='yourkeyhere'
WIRELESS_MODE='Managed'
WIRELESS_NICK=''
WIRELESS_NWID=''
DHCLIENT_MODIFY_RESOLV_CONF='yes'
DHCLIENT_SET_DEFAULT_ROUTE='yes'
~

BTW, the IPADDR is what I previously had the adapter set to. DHCP is enabled now in YaST, and in fact I get a different, dynamic address than the one listed. It just must enter it the file in case DHCP is disabled.

cool thanks.

I have SuSE 9 running flawlessly, have used both a Lynksis card and a Netgear card with equal success with very little work. My wireless adapter, was recognised and configured by Yast. However I could not for the life of me get it to get outside my router, even with the proper settings in Yast.

In the console as root, I did a simple route add default gw 192.168.0.1 wlan0 then opened a browser and whala I was on the net.

Now that it worked, I simply added that line to my /etc/initd.d/rc file so it would be active at boot with the card plugged in. Alls good for me now. I don't know why the yast settings wouldn't do this for me, all I know is this worked for me.

It may or may not help you guys with your problems but it certainly wouldn't hurt to try. Of course you will want to substitute your gateway address in place of my 192.168.0.1.

:Pengy: Your trick solved my problem but I couldn't put it inmy rc file.
I tried it but without succes. It doesn't work. Can you help me?

I've successfully got my broadcom wireless g working the the ndiswrapper over at www.sourceforge.net.

Wes