I must be missing something.

I clicked that little hardware thingy in the tray, picked my wireless card, hit configure, blah blah blah, entered my ESSID (leaving everything else blank), then hit ok.

Is it connected now? How do I connect it if it's not?

If I go to Konquerer, I get http://www.google.com not found error -- as if i'm not connected.

What do I need to do??

Thanks
PulsarSL

edit: no wep, only mac filtering (correctly configured)

Hi.

Could you post the output of the following two commands:
/sbin/ifconfig
and
/sbin/iwconfig

Dave

ifconfig returns nothing useful and iwconfig isn't found.....

my AWESOME first impressions of SuSE are fading... quickly...

What does ifconfig return?

Try doing 'locate iwconfig' to see where it is. If it genuinely is missing, then you may have to install it, as it's normally used as the back-end for graphical wireless tools.

su to become root to run the commands, and please post the actual output of the commands rather than to just say that "nothing useful" is displayed. The ifconfig output will show which network interfaces are recognized, along with other important details, and is highly relevant to what steps may need to be executed in order to resolve the issue. Thanks -- J.W.

i had funky issues connecting to my wireless network as well.. not sure why.. however, easily solved by setting a static IP and the DNS servers. I set that up and now am connecting fine, in fact, it's what I'm typing on right now.

I had all the wireless setting 'correct' and would get an IP address from the router, but for some reason, could not get on the net..

Try setting a static IP, it should work. good luck.

Sorry, I can't post the output of ifconfig because I can't get on the net from my Linux partition... I'll type it out manually in a few minutes

linux:~ # ifconfig
lo link encap:local loopback
inet addr: 127.0.0.1 mask:255.0.0.0
inet6 addr: ::1/128 scope:host
up loopback running mtu:16436 metric:1
rx packets:42 errors:0 dropped:0 overruns:0 frame: 0
tx packets:42 errors:0 dropped:0 overruns:0 frame: 0
collisions:0 txqueuelen:0
rx bytes:2708 (2.6 kb) tx bytes: 2708 (2.6 kb)

linux:~ # iwconfig
lo no wireless extensions.

eth0 IEEE 802.11b ESSID:"upstairs" nickname:"linux"
mode:managed channel:0 access point: 00:00:00:00:00:00
bit rate=0kb/s tx-power=0dbm
retry:on rts thr=2304 b fragment thr:2332 b
encryption key: off

eth1 no wireless extensions.

sit0 no wireless extensions

thanks,
PulsarSL

OK - so one factor that seems clear is that eth0 is not being recognized, and it may be that DHCP is not running. Here's what I'd suggest, and let me just mention that the following is what I typically do if my laptop doesn't connect automatically - it's not a surefire fix. My experience is that wireless can sometimes be pretty tricky, and I'll admit that my bag of tricks is pretty limited, so I can't guarantee that the following will produce the desired results. That being said, I'm hoping that some of this may be useful

1. As root, run This will scan the available wireless connections that your PC can detect, and list them. You should see your access point listed. If not, wait a few seconds and try again. If you run it a few times (over say at least one or two minutes) and it never is listed, then check to see that your wireless router is plugged in, connected, etc, as the problem may with it rather than your PC.
2. While still as root, run Substitute your ESSID in place of the "<your essid>" (obviously). This command will instruct your system to associate eth0 with the connection you've specified.
3. Start DHCP
You should see some kind of output indicating that a connection was established. If you get an error message about it already running, delete the existing .pid file (eg, for Suse it's probably /var/run/dhcpcd-eth0.pid) and rerun dhcpcd.
4. Check to see if any of the above did anything useful
If the above was effective, you should see eth0 listed, with a non-blank IP address. If so, you should have a live connection and you should be able to start surfing. If not, then the only other suggestion I'd have would be to bounce eth0
I still consider myself somewhat of a beginner with wireless under Linux, but the above usually seems to do the trick for me. Good luck with it Pulsar-- J.W.

See first of all if the Wireless card is actually recognising the access point.

Try this command first as root

iwlist interface -scan

your output should appear something like this

redfox:/home/jim # iwlist wlan0 scan
wlan0 Scan completed :
Cell 01 - Address: 00:0F:3D:97:10:00
ESSID:"jimbo"
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:94/94 Signal level:-27 dBm Noise level:-154 dBm
Encryption keyff
Bit Rate:1 Mb/s
Bit Rate:2 Mb/s
Bit Rate:5.5 Mb/s
Bit Rate:11 Mb/s
Bit Rate:22 Mb/s
Bit Rate:6 Mb/s
Bit Rate:9 Mb/s
Bit Rate:12 Mb/s
Bit Rate:18 Mb/s
Bit Rate:24 Mb/s
Bit Rate:36 Mb/s
Bit Rate:48 Mb/s
Bit Rate:54 Mb/s
Extra:bcn_int=200

redfox:/home/jim #


also check that the wireless interface exists (iwconfig)

try and bring it up with the command ifup wlan0 and then run the iwlist command again.

Ensure also that your file in /etc/sysconfig/network is OK -- YAST doesn't always update it correctly (don't know why --maybe a bug)

file should be named something like ifcfg-wlan0 (or whatever you've called your wireless interface)

Here's what's in my file

NAME='Linksys WPC54G'
STARTMODE='auto'
WIRELESS_AUTH_MODE='open'
WIRELESS_ESSID='jimbo'
WIRELESS_MODE='Managed'
DHCLIENT_MODIFY_RESOLV_CONF='yes'
DHCLIENT_SET_DEFAULT_ROUTE='yes'
HWD_DRIVER='hostap_driverloader'
BOOTPROTO='dhcp'
MTU=''
REMOTE_IPADDR=''
USERCONTROL='no'
WIRELESS_AP=''
WIRELESS_BITRATE='auto'
WIRELESS_CHANNEL=''
WIRELESS_DEFAULT_KEY='0'
WIRELESS_FREQUENCY=''
WIRELESS_KEY=''
WIRELESS_KEY_0=''
WIRELESS_KEY_1=''
WIRELESS_KEY_2=''
WIRELESS_KEY_3=''
WIRELESS_KEY_LENGTH='128'
WIRELESS_NICK=''
WIRELESS_NWID=''
WIRELESS_POWER='yes'
WIRELESS_WPA_PSK=''


I'm testing it with NO ENCRYPTION now it's working I'll set all the security but test it first without any security / firewalls etc just to get it running.

I'm using the LINUXANT driver for the Linksys wpc54g wireless card (based on the Broadcom chipset)


Note this line in the file
HWD_DRIVER='hostap_driverloader'

That's the Linuxant driver.

If you go the linuxant route you'll get a file with that line and a simple start line --the file will have just 2 lines in it.

Copy my file above as a template changing your ESSID to whatever you've called it and set the name of your wireless card (it's only text --can be anything you like --"Doggy Card" if you want.


My access point provides the IP addresses and all the routing (via DHCP) so ensure you set Automatic address setup --don't use STATIC IP addresses

set also in Host Name and Name server Update name servers and list servers via DHCP (click the box) and ensure nothing in the Routing box --no IP addresses for Gateway).

If you are not using DHCP then enter IP addresses, IP addresses of the DNS servers from your ISP and the default gateway.

Finally if you are using Firefox enter about:config in the browser address box. Change the Network IPV6 option to TRUE (set it OFF)
this prevents some problems with DNS lookups with Firefox and makes ir run faster in any case.

If your wireless card really won't work even with the NDIS wrapper then consider the solution from LINUXANT --it's only around 18 USD and really does save a lot of messing around --works a treat even on the most obscure wireless cards.
Cheers
-K


Added

BTW when editing the file in etc/sysconfig/network the entries with double quotes are actually two single quotes with no spaces. (Null entries)
I had some syntax errors first time around as I thought they should have been double quotes i.e " rather than '' --so ensure SINGLE QUOTES.

Cheers again
-K

It can find anything when I scan, but my router is correctly configured, in broadcast mode, with no WEP. This reply was posted through it (in windows).

Any more ideas?

thanks
PulsarSL

I guess not. Back to Windows.

Well, did you actually try any of the steps that were suggested? Could you post the output of the various commands that you ran? Just saying that you're still having trouble but without providing any additional information doesn't give people much to go on.... -- J.W.

The only output of anything you've told me to run that you haven't seen is the "No scan results" returned by the network scan.

What would cause it to not find my router??

I appreciate the help, but my hopes are draining....