I've just loaded in SuSE 9.3 Professional on a Toshiba Satellite M35X-S329.

The Intel (R) Pro Wireless 2200BG driver seems to have been installed correctly as it was included with the SuSE 9.3 Distro.

Once I have booted into SuSE 9.3, he problem arises when KInternet is displaying all the stats of the WAP access point. I get a reading status of the decibel level of which the computer is detecting, as well as the name of the network ESSID.

Via KInternet I can actually connect to the WAP as well ( or so it tells me ), yet I cannot access the internet whatsoever.

ifconfig shows that the wireless NIC is on both eth0 and eth1 ( shouldn't this be configured to wlan0 or wlan1? )

iwconfig shows only a connection on eth1 so I am really getting a bit confused here....heh new distro woes.

Does anyone have any suggestions?

A good start to finish command line walkthrough would be great, but I am having trouble finding a good resource being that my wlan knowledge within linux is very limited.

Any suggestions are greatly appreciated !

Make sure your firewall is using wlan/eth. Disable all security/firewall/wep/etc... then start them one at a time.
With 9.2 you have to add a couple extra settings to /etc/sysconfig/network/ifcfg-wlan0

DHCLIENT_MODIFY_RESOLV_CONF='yes'
DHCLIENT_SET_DEFAULT_ROUTE='yes'

this might work for 9.3 also.

I think this may have been just what I was looking for. Thanks, Ran!

This is my experience with Suse and wireless. It works for me; whether or not it will be of any use to anyone else remains to be seen. In any case:

I'm running Suse v9.1 on my laptop, and my wireless interface is also eth1. Because I usually don't use wireless, eth0 is my default interface, and DHCP is automatically started against eth0. After booting, ifconfig shows that eth0 is up and active (although there is no IP address), eth1 has no connection, and iwconfig shows eth1 as running. In order to start surfing wirelessly, all I need to do is
and I'm connected. Note that it sometimes is necessary to run iwlist to find an open access point, and then to manually associate it and eth1 (ie, "iwconfig eth1 essid <whatever>" but the key for me was essentially to just bring down eth0 and restart DHCP on eth1. I'll be honest - I experiment a lot with this machine, and I more or less stumbled across this approach rather than to have operated from a position of deep knowledge. Fortunately it works for me and that's all I care about. Good luck with it in any case -- J.W.

Or just go into Yast and configure eth0 to manual

when running
i got an error saying it couldnt find a file so I think once home from work today I will install the new firmware/drivers just to make sure all librarys are correctly installed.

dhcpcd is DHCP client for getting a IP automatically from your router/dhcp server.

I get an error too but it doesn't matter - if I ping, say, Yahoo, the connection is made and it works. As before, I experiment a lot with this machine so perhaps some of the remnants of those previous experiments have put my machine into a very non-typical state, but bringing down eth0 and restarting DHCP on eth1 works for me. Good luck -- J.W.

J.W. You can have both connections start at boot, and it will use either one, you don't have to bring down one and bring up the other. This will boot LAN if cable is plugged in, and boot wlan if a wireless connection is available.
On LAN you can set time out around 8 seconds, and wireless to 10 seconds. Default is 20 seconds, this will save 10 +/- seconds on boot if one is not available.

My situation is kind of like this.
I was running 9.2 and have now installed 9.3.
the wireless, after a little configuring, worked ok in 9.2. I had it going with netapplet and that worked great, when I had the right SCPM profile up.
9.3 says it sees my wireless router, has signal, can ping the router, can log into the router, but cannot get any sort of dns resolution at all. I see my isp's dns router entered in by dhcp in yast, but i still get no resolution. when the cable is plugged in, it works fine.
I've had this before, but adding the
DHCLIENT_MODIFY_RESOLV_CONF='yes'
DHCLIENT_SET_DEFAULT_ROUTE='yes'
to my /etc/sysconfig/network/ifcfg-wlan0 and it fixed it for some routers, but right now nothing gets my wireless any sort of DNS resolution.

Any Ideas?

STuPiDiCuS did you try setting the default gateway for wlan? (192.168.1.1 or 192.168.1.0 or 192.168.0.0 or 192.168.255.255 or something like that)
Also try my post above, I have found adding those two lines to work on a lot of Suse wlan's.

I am living in an apartment right now, and everyone around here seems to have an AP. When I was running 9.2 I had no problem, but this release seems to want to switch over to another AP.

So, How do I set this to only access my AP?

Every time it does I loose the connection.

Use a patch cable to your router to make sure it's connected to yours.
Go through the setup, and change the default settings to yours (Login passwd, SSID, enable MAC filter, etc...)
Don't enable the security until your sure you got a wireless connection, then enable them one at a time to make it easier to find problems.
You can use "iwlist wlan0 scan" to look for AP's

Robinsr-
you can specify which AP to connect to by entering its mac address into the access point field under the network settings... I'm at work and can't get to a suse box to look at it and tell you, but I do know there is a field for it. that should ensure that you are connecting to that one only.

If that one doesn't work, I would recommend opening the "Network Selector" utility under the kmenu>system>applets in 9.2 you had to enable netdaemon, but in 9.3 it is enabled by default. so just run that and it should fix your problem, as it will let you pick which access point to use. I used SCPM in conjunction with it to switch to the settings I wanted and then netapplet would work, but then again I know ppl who didn't need to do that.

I posted this in a different forum, maybe it should be moved here, maybe not. at any rate, I hope this helps, I've got it working somewhat. It doesn't seem to be "fixed" though. anyway it works.

http://www.linuxquestions.org/questi...hreadid=316969