DWA-552 won't access internet

English Network/Internet
#1

To Whom It May Concern:

I am trying to use a D-Link wireless PCI card (model: DWA-552) with SuSE 10.3; however, I cannot get the card to connect to the internet.

I tried using MadWiFi drivers first–installing them via YaST–but I couldn’t get the card to work. I uninstalled MadWiFi using YaST.

Next I tried using ndiswrapper, following the instructions at
Ndiswrapper - openSUSE
After completing the instructions I started Firefox, but the browser could not connect. It appears as if I’m able to connect to the access point but not to the internet.

Details:

The card works under Windows XP (I dual boot.)

YaST=>Hardware=>Hardware Information=>Wireless LAN=>AR5416 802.11 a/b/g/n Wireless PCI Adapter (wlan0)=>Kernal Driver: ndiswrapper

“lspci -v” outputs
02:0a.0 Network Controller: Atheros Communications, Inc. AR5416 802.11a/b/g/n Wireless PCI Adapter (rev 01)
Subsystem: D-Link System Inc Unknown device 3a6d
Flags: bus master, fast Back2Back, 66MHz, medium devsel, latency 128, IRQ 22
Memory at feae0000 (32-bit, non-prefetchable) [size=64]
Capabilities: [40] #80 [0000]

“lspci -n” lists “02:0a.0 Class 0280: 168c:0023 (rev 01)”

“dmesg | grep firmware” only outputs an error message about intel_rng (nothing about my wireless card)

“iwlist scan” outputs present wireless networks

I turned of encryption and turned on SSID broadcasting to make connecting easier.

“iwconfig” lists the ESSID and MAC address of my access point (plus other info.)

“ifconfig” lists my IP as 192.168.1.103, which makes sense

I pinged my access point with “ping -c 5 192.168.1.1”. Pings were successful.

I pinged an external address using “ping -c 5 66.70.73.150”. This fails with “connnect: Network is unreachable”

Does anyone have any ideas to get my card working?

Thanks in advance,
Caleb[/size]

#2

Remove that ndiswrapper crap and install recent madwifi from the “driver:wireless” repository.


/lib/modules/2.6.27.29-0.1-default/updates/ath/ath_pci.ko
alias:          pci:v0000**168C**d0000**0023**sv*sd*bc*sc*i*
#3

Akoellh wrote:
> Remove that ndiswrapper crap and install recent madwifi from the
> “driver:wireless” repository.

Removing ndiswrapper is always good advice. Remember that with it, you
are exposing the Linux kernel to an unconstrained Windows driver. All
the errors that cause Blue Screens of Death (BSOD) in Windows now can
cause kernel oopses. It is the quickest way to convert a system that
is stable into something that needs rebooting regularly, just the way
Windows does!

The rule is “Use ndiswrapper ONLY when you must!”.

#4

Thanks for your suggestion. I uninstalled ndiswrapper and installed MadWiFi using YaST. I followed the instructions at
Atheros madwifi - openSUSE

Unfortunately, my card is still not working. Here is the result of some tests:

Checked YaST=>Hardware=>Hardware Information=>Wireless LAN=>AR5416 802.11 a/b/g/n Wireless PCI Adapter (wlan0):
no kernal driver listed

“lspci -v” outputs:
02:0a.0 Network controller: Atheros Communications, Inc. AR5416 802.11a/b/g/n Wireless PCI Adapter (rev 01)
Subsystem: D-Link System Inc Unknown device 3a6d
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 11
Memory at feae0000 (32-bit, non-prefetchable) [size=64]
Capabilities: [40] #80 [0000]
Capabilities: [80] #00 [0000]

“lspci -n” outputs:
02:0a.0 Class 0280: 168c:0023 (rev 01)

“dmesg | grep firmware” only outputs an error message about intel_rng (nothing about my wireless card)

“iwlist scan” does not mention any wireless networks

“ifconfig” does not mention any wireless networks

Does anyone have anymore ideas? I’m not sure what to do next.

Thanks for your help,
Caleb[/size]

#5

Just do what I told you:

driver:wireless

#6

I installed MadWiFi from
Index of /repositories/driver:/wireless/openSUSE_10.3_update

Things look better. Thanks for the clarification. Unfortunately I’m still not able to connect to the internet.

Details:

YaST>Hardware>Hardware Information>Wireless LAN>AR5416 802.11 a/b/g/n Wireless PCI Adapter (wlan0)>Kernel Driver: madwifi

“lspci -v” outputs

02:0a.0 Network controller: Atheros Communications, Inc. AR5416 802.11a/b/g/n Wireless PCI Adapter (rev 01)
        Subsystem: D-Link System Inc Unknown device 3a6d
        Flags: bus master, 66MHz, medium devsel, latency 96, IRQ 22
        Memory at feae0000 (32-bit, non-prefetchable) [size=64]
        Capabilities: [40] #80 [0000]

“lspci -n” outputs

02:0a.0 Class 0280: 168c:0023 (rev 01)

“dmesg | grep firmware” only outputs an error message about intel_rng (nothing about my wireless card)

“iwlist scan” outputs present wireless networks

“iwconfig” lists

lo        no wireless extensions.
eth0      no wireless extensions.
wifi0     no wireless extensions.
wlan0     IEEE 802.11g  ESSID:"omitted"  Nickname:""
          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:1C:10:BF:05:B3   
          Bit Rate:6 Mb/s   Tx-Power:19 dBm   Sensitivity=1/1  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=37/70  Signal level=-59 dBm  Noise level=-96 dBm
          Rx invalid nwid:35522  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

“ifconfig” outputs, in part

wifi0     Link encap:UNSPEC  HWaddr 00-22-B0-BC-83-0E-30-30-00-00-00-00-00-00-00-00  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:69728 errors:0 dropped:0 overruns:0 frame:7085
          TX packets:8671 errors:2484 dropped:1 overruns:0 carrier:0
          collisions:0 txqueuelen:280 
          RX bytes:8782664 (8.3 Mb)  TX bytes:585474 (571.7 Kb)
          Interrupt:22 
wlan0     Link encap:Ethernet  HWaddr 00:22:B0:BC:83:0E  
          inet addr:192.168.1.103  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::222:b0ff:febc:830e/64 Scope:Link
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:74 errors:0 dropped:0 overruns:0 frame:0
          TX packets:75 errors:1 dropped:1 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:8480 (8.2 Kb)  TX bytes:13670 (13.3 Kb)

I pinged my access point with “ping -c 5 192.168.1.1”. Pings were successful.

I pinged an external address using “ping -c 5 66.70.73.150”. This fails with “connnect: Network is unreachable”

Where do I go from here?

Thanks again,
Caleb[/size]

#7

To Whom It May Concern:

I still haven’t been able to connect to the internet using my wireless card. Does it mean anything that with both ndiswrapper and MadWiFi I was able to ping the router but not able to ping an external IP address?

There are several threads that mention installing bleeding edge MadWiFi to get their networks to work. Might this work in my case? If I install a bleeding edge version of MadWiFi and it messes my computer up, is there a way to uninstall it?

I’ve been using GNU/Linux almost exclusively for the past several years, and I’d hate to have to go back to using MS Windows because of this networking issue.

If it makes a difference, I’m using a 32-bit version of OpenSuSE 10.3.

Thanks again to anyone who can help, and thanks to those who already have helped me out,
Caleb

#8

Then your problem is not the driver but the network setup.

Also remove ndiswrapper completely, this is a proven way to get in trouble with Atheros cards being actually supported by madwifi (the above outputs also indicate, that this is the case, wlan0 and wifi0 is NOT what should be seen on using ONLY madwifi OR on using ONLY ndiswrapper).

The outputs of your posting before confirm actually that the driver is working.

You already do use the “bleeding edge” madwifi drivers (believe me, I am the guy who built the madwifi packages you are using at the moment).

Well, then setting up your network correctly shouldn’t be a problem (I guess your routing is hosed).

It does not make a difference for madwifi, but for your future planning maybe.

SUSE Linux Lifetime - openSUSE

#9

Thanks for your response. It’s good news that the driver is working; that narrows down what could be wrong.

I thought it was odd that wifi0 and wlan0 were both showing up. YaST shows ndiswrapper and ndiswrapper-kmp-default as being uninstalled. How do I make sure ndiswrapper is completely uninstalled?

Sorry if this is a silly question, but what kind of things should I check with my network setup?

I apologize if I’m being dense, and I appreciate you help!

#10

Find and grep are your friends (and /etc is the place to search).

No, the odd thing is, that there is not “ath0” and “wifi0” with madwifi, “wlan0” was set by ndiswrapper, again find and grep are your friends (and /etc/udev/ the place to search).

But if your network setup is still incorrect, even that won’t help, so correct your setup also, it must be faulty.

#11

It looks like ndiswrapper isn’t completely gone:

find . -type f -exec grep -l 'ndiswrapper' {} \;
./sysconfig/network/scripts/ifup-wireless
./udev/rules.d/70-persistent-net.rules

How do I rid myself of ndiswrapper?

The following commands don’t produce any output:

find . -type f -exec grep -l 'ath0' {} \;
find . -type f -exec grep -l 'wifi0' {} \;

But this does:

find . -type f -exec grep -l 'wlan0' {} \;
./rules.d/70-persistent-net.rules

I’m not sure what to do with this information.

I can connect to a wired network using SuSE, and Windows connects to the network wirelessly, so I think the network’s configured correctly. What am I missing?

Thanks for your help.

#12

I still haven’t been able to figure out how to get my computer to connect to the internet, and I’m not really sure what to do next. I’m pretty new to “looking under the hood” of my Linux system, so if anyone could do a little hand holding and tell me what to do next–even if it seems really obvious–I would be very grateful.

Sorry to be a bother, and thank you for your time,
Caleb

#13 

su 

password

mv /etc/udev/rules.d/70-persistent.net.rules /root/ # backup for safety

udevadm trigger 

rcnetwork restart
#14 
# mv 70-persistent-net.rules /root/
# udevtrigger
# rcnetwork restart
Shutting down network interfaces:
    eth0      device: Intel Corporation 82801BA/BAM/CA/CAM Ethernet Controller (rev 03)
    eth0                                                             done
    wlan0     device: Atheros Communications, Inc. AR5416 802.11a/b/g/n Wireless PCI Adapter (rev 01)
    wlan0                                                            done
Shutting down service network  .  .  .  .  .  .  .  .  .  .  .  .  . done.
Hint: you may set mandatory devices in /etc/sysconfig/network/config
Setting up network interfaces:
    lo        
    lo        IP address: 127.0.0.1/8   
Checking for network time protocol daemon (NTPD):                    unused
    lo                                                               done
    eth0      device: Intel Corporation 82801BA/BAM/CA/CAM Ethernet Controller (rev 03)
    eth0      (DHCP) . . . . . no IP address yet... backgrounding. 
    eth0                                                             waiting
    wlan0     device: Atheros Communications, Inc. AR5416 802.11a/b/g/n Wireless PCI Adapter (rev 01)
    wlan0     warning: using NO encryption
    wlan0     (DHCP) . . . . . no IP address yet... backgrounding. 
    wlan0                                                            waiting
Setting up service network  .  .  .  .  .  .  .  .  .  .  .  .  .  . done.
SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
SuSEfirewall2: Warning: no default firewall zone defined, assuming 'ext'
SuSEfirewall2: using default zone 'ext' for interface eth0
SuSEfirewall2: using default zone 'ext' for interface wifi0
SuSEfirewall2: batch committing...
SuSEfirewall2: Firewall rules successfully set
# ping -c 5 66.70.73.150
connect: Network is unreachable