Networking Forums

Networking Forums > Computer Networking > Linux Networking > WLAN won't work with Netgear MA101/SuSE 9.0

Reply
Thread Tools Display Modes

WLAN won't work with Netgear MA101/SuSE 9.0

 
 
Bogislav Wilmers
Guest
Posts: n/a

 
      08-24-2004, 08:06 AM
I was using an analog modem on my SuSE 9.0 Prof. desktop right now but
recently installed a Netgear MA101 rev. B DSL adapter. It works fine under
Windows 2000, but I cannot get it working with Linux. I tried the
sourceforge drivers (without success) and the alternative Atmel at76c503
(RFMD) Wireless LAN Driver v0.11. After installing the driver and loading
the modules, I can ping 192.168.0.1 (see below). But I cannot get any
browser working. I do not know the problem, may be it is only the
DNS-Server (I do not know where to set up the DNS-Server and I do not know
anything about DHCP - do I have to install anything here???).

Below are the outputs of iwconfig, ifconfig, ping, lsmod and dmesg.

Thanks for any help!!!

Bogislav


linux:/home/bogi # iwconfig
lo no wireless extensions.

sit0 no wireless extensions.

wlan0 IEEE 802.11-DS ESSID:"SAL" Nickname:"okuwlan"
Mode:Managed Channel:1 Access Point: 00:30:AB:1E:3E:4B
Bit Rate:11Mb/s
RTS thr=1536 B Fragment thr=1536 B
Encryption key:ABCD-ABCD-ABCD-ABCD-ABCD-ABCD-AB Security
mode:restricted
Power Managementff
Link Quality:0 Signal level:5 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

linux:/home/bogi # ifconfig
lo Protokoll:Lokale Schleife
inet Adresse:127.0.0.1 Maske:255.0.0.0
inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:284 errors:0 dropped:0 overruns:0 frame:0
TX packets:284 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:23733 (23.1 Kb) TX bytes:23733 (23.1 Kb)

wlan0 Protokoll:Ethernet Hardware Adresse 00:09:5B:30:F4:51
inet Adresse:192.168.0.1 Bcast:192.168.0.255 Maske:255.255.255.0
inet6 Adresse: fe80::209:5bff:fe30:f451/64
Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MTU:1500 Metric:1
RX packets:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:100
RX bytes:1547 (1.5 Kb) TX bytes:711 (711.0 b)

linux:/home/bogi # ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.113 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.107 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.104 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.105 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=0.104 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=0.103 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=0.104 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=0.101 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=0.081 ms

--- 192.168.0.1 ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 7999ms
rtt min/avg/max/mdev = 0.081/0.102/0.113/0.012 ms
linux:/home/bogi #

dmesg:
(...)
at76c503.c: Generic Atmel at76c503/at76c505 routines v0.11
usbdfu.c: USB Device Firmware Upgrade (DFU) handler v0.11
usb.c: registered new driver usbdfu
at76c503-rfmd.c: Atmel at76c503 (RFMD) Wireless LAN Driver v0.11
usb.c: registered new driver at76c503-rfmd
SiS router pirq escape (99)
SiS router pirq escape (99)
usb-ohci.c: USB OHCI at membase 0xd1977000, IRQ 5
usb-ohci.c: usb-00:02.3, Silicon Integrated Systems [SiS] 7001 (#2)
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 3 ports detected
PCI: Found IRQ 11 for device 00:02.2
usb-ohci.c: USB OHCI at membase 0xd1979000, IRQ 11
usb-ohci.c: usb-00:02.2, Silicon Integrated Systems [SiS] 7001
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 3 ports detected
hub.c: new USB device 00:02.3-1, assigned address 2
usb.c: USB device 2 (vend/prod 0x7cc/0x204) is not claimed by any active
driver.
hub.c: new USB device 00:02.2-1, assigned address 2
usbdfu.c: Downloading firmware for USB device 2...
at76c503.c: $Id: at76c503.c,v 1.35 2003/07/30 06:31:51 jal2 Exp $ compiled
Jun 9 2004 20:31:42
at76c503.c: firmware version 1.101.2 #84 (fcs_len 4)
at76c503.c: device's MAC 00:09:5b:30:f4:51, regulatory domain ETSI (Europe -
(Spain+France) (id 48)
at76c503.c: registered wlan0
at76c503.c: using BSSID 02:00:2c:62:15:00
wlan0: no IPv6 routers present
at76c503.c: using BSSID 02:00:3b:f8:ce:15
at76c503.c: using BSSID 02:00:5f:07:11:18

linux:/home/bogi # lsmod
Module Size Used by Tainted: P
usb-ohci 19848 0 (unused)
at76c503-rfmd 39424 1
usbdfu 7852 0 [at76c503-rfmd]
at76c503 52544 0 [at76c503-rfmd]
(...)
 
Reply With Quote
 
 
 
 
Kevin Boergens
Guest
Posts: n/a

 
      08-24-2004, 04:23 PM
Hi!

> Below are the outputs of iwconfig, ifconfig, ping, lsmod and dmesg.


To help you, we need the output of the command "route"

HAND,
Kevin
--
http://www.boergens.de
 
Reply With Quote
 
Peter F
Guest
Posts: n/a

 
      08-24-2004, 11:18 PM
Bogislav Wilmers wrote:

> I was using an analog modem on my SuSE 9.0 Prof. desktop right now but
> recently installed a Netgear MA101 rev. B DSL adapter. It works fine under
> Windows 2000, but I cannot get it working with Linux. I tried the
> sourceforge drivers (without success) and the alternative Atmel at76c503
> (RFMD) Wireless LAN Driver v0.11. After installing the driver and loading
> the modules, I can ping 192.168.0.1 (see below). But I cannot get any
> browser working. I do not know the problem, may be it is only the
> DNS-Server (I do not know where to set up the DNS-Server and I do not know
> anything about DHCP - do I have to install anything here???).
>
> Below are the outputs of iwconfig, ifconfig, ping, lsmod and dmesg.
>
> Thanks for any help!!!
>
> Bogislav
>
>
> linux:/home/bogi # iwconfig
> lo no wireless extensions.
>
> sit0 no wireless extensions.
>
> wlan0 IEEE 802.11-DS ESSID:"SAL" Nickname:"okuwlan"
> Mode:Managed Channel:1 Access Point: 00:30:AB:1E:3E:4B
> Bit Rate:11Mb/s
> RTS thr=1536 B Fragment thr=1536 B
> Encryption key:ABCD-ABCD-ABCD-ABCD-ABCD-ABCD-AB Security
> mode:restricted
> Power Managementff
> Link Quality:0 Signal level:5 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> linux:/home/bogi # ifconfig
> lo Protokoll:Lokale Schleife
> inet Adresse:127.0.0.1 Maske:255.0.0.0
> inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:284 errors:0 dropped:0 overruns:0 frame:0
> TX packets:284 errors:0 dropped:0 overruns:0 carrier:0
> Kollisionen:0 Sendewarteschlangenlänge:0
> RX bytes:23733 (23.1 Kb) TX bytes:23733 (23.1 Kb)
>
> wlan0 Protokoll:Ethernet Hardware Adresse 00:09:5B:30:F4:51
> inet Adresse:192.168.0.1 Bcast:192.168.0.255
> Maske:255.255.255.0 inet6 Adresse: fe80::209:5bff:fe30:f451/64
> Gültigkeitsbereich:Verbindung
> UP BROADCAST RUNNING MTU:1500 Metric:1
> RX packets:16 errors:0 dropped:0 overruns:0 frame:0
> TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
> Kollisionen:0 Sendewarteschlangenlänge:100
> RX bytes:1547 (1.5 Kb) TX bytes:711 (711.0 b)
>
> linux:/home/bogi # ping 192.168.0.1
> PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
> 64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.113 ms
> 64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.107 ms
> 64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.104 ms
> 64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.105 ms
> 64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=0.104 ms
> 64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=0.103 ms
> 64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=0.104 ms
> 64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=0.101 ms
> 64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=0.081 ms
>
> --- 192.168.0.1 ping statistics ---
> 9 packets transmitted, 9 received, 0% packet loss, time 7999ms
> rtt min/avg/max/mdev = 0.081/0.102/0.113/0.012 ms
> linux:/home/bogi #
>
> (...)


You are NOT doing a ping to your router. You have assigned 192.168.0.1 to
your card.

Use Yast to configure your network device. There you can set up DHCP with
just a couple of clicks. It looks like your card is working to the AP but
you need to get a proper IP address.

Peter F

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Netgear ME102 & Netgear MA101 ? Tazmanian Devil Home Networking 0 01-13-2005 06:18 PM
Netgear MA101 on SuSE 8.2 and printing T i m Linux Networking 0 10-11-2003 07:56 AM
Netgear MA101 and WinXP SP1? Baddel Zwen Wireless Internet 2 09-05-2003 09:18 PM
Netgear MA101 dropouts JuNi Wireless Internet 1 09-01-2003 05:10 PM
Problem with SuSE 8.2 and NetGear MA401 wlan pcmcia card. Ola Theander Linux Networking 1 08-25-2003 01:49 PM



1 2 3 4 5 6 7 8 9 10 11