Help with WiFi and SuSE....
 

Recently installed SuSE on my Dell laptop. Have an Orinoco Gold 802.11b card, and a D-Link DI-514 AP. Laptop seems to be receiving a signal, it receives the AP's MAC address, yet I cannot ping anything much less the AP, and I can't access the internet at all. Running Windows 2000 on my old desktop, and my ISP is Road Runner through a cable modem. Everything as far as WEP and SSID checks as correct. Drivers loaded apparently correctly. Again, laptop receives correct IP and MAC addresses from AP yet no other communication. Any ideas?

...moved to the Linux - Networking -> Wireless subforum

I'd like to see the output from
ifconfig
netstat -rn

and your /etc/resolv.conf file

Well the original poster might be reluctant, but I am having a similar problem. SuSE 9, Orinoco Gold Classic. The card is detected and the links show solid and blinking as though they are working, but I can get no confirmation that there is a connection. I have supplied the info you asked the original poster for below. The ap is set to not beacon, mac filtering, wep enabled. I have the ssid, my mac is on the allow list, and I have the wep key.

raistlin:/home/sekel # netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
raistlin:/home/sekel # ifconfig
eth0 Link encap:Ethernet HWaddr 00:40:45:1B:84:22
inet6 addr: fe80::240:45ff:fe1b:8422/64 Scope:Link
UP BROADCAST NOTRAILERS MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:4418 (4.3 Kb)
Interrupt:11 Base address:0xd800

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:40 errors:0 dropped:0 overruns:0 frame:0
TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2608 (2.5 Kb) TX bytes:2608 (2.5 Kb)

wlan0 Link encap:Ethernet HWaddr 00:02:2D:93:82:8C
inet6 addr: fe80::202:2dff:fe93:828c/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:9 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:3 Base address:0x100

raistlin:/home/sekel # cat /etc/resolv.conf
nameserver 216.180.99.2
nameserver 216.180.122.2
search hiwaay.net hiwaay.net
raistlin:/home/sekel #

Any help or suggestions you might have would be greatly appreciated. I have search google and tried many of the suggestions to no avail. I will provide anything else that may be needed.

hmm, no routing table. Are you using IPv6?
If so, then maybe try default IPv4 addressing for simplicity's sake.

you can remove the search line from /etc/resolv.conf

check /etc/sysconfig/network/ifcfg-<Interface-Name> and make sure that
you have gateway set correctly and other values look ok.

Also recheck your iwconfig and make sure that you set the WEP key alright, the syntax for setting the WEP key is a little funky.

iwconfig <intf> key restricted [1] <key>


I would first try to get routing table to look ok, then WEP, then DHCP (if using). DNS looks ok without the search line in /etc/resolv.conf

Also just a side note: if you choose to use eth0 and wlan0 at the same time then they must be on different networks (looks like they are on different networks from the output).

Also check dmesg output to see if the driver appears to initialize ok, etc.

slightly off-thread...

I am still looking for configuration instructions to set up a linux (suse9.0) computer to be an access point. Presently have 2 wireless cards operating correctly, one as infrastructure (surfs fine) and one as ad-hoc, ip forwarding enabled. Basically want to do it in reverse, ad-hoc in on one card, and access point out on the other card. The unit will then be a remote access point, not needing wired connection to the internet and still be an access point.

Thanks!

Man I appreciate your help, but I found the problem. I checked with a different AP and put in the WEP key and the ssid and it picked it up right away which means the problem is the crappy wireless connection at work. I feel extremely bad for wasting your time, but I am tweaking my settings for the wireless that works.

cool, no time wasted. It is interesting to see different problems on different platforms for me, hopefully learning more and helping on the way.