DLINK
"Mundo Movil" <[email protected]>
| Newsgroups | gmane.linux.drivers.at76c503a.user |
|---|---|
| Message-ID | <[email protected]> |
Hi, I have been using a MA101 adapter until now. It has been working swell on my Mandrake 9.1 Linux box. I just purchased a DLink dwl120+ (FCCID: 07J-GL2422MU-MT H/W Ver:A1 F/W Ver:1.00). I tried to use the same driver but it just does not work can you give me some pointers on what to do? Thanks, Mundo Movil >From: [email protected] >Reply-To: [email protected] >To: [email protected] >Subject: at76c503a-user digest, Vol 1 #265 - 6 msgs >Date: Thu, 29 Jan 2004 12:00:05 +0100 > >Send at76c503a-user mailing list submissions to > [email protected] > >To subscribe or unsubscribe via the World Wide Web, visit > http://lists.berlios.de/mailman/listinfo/at76c503a-user >or, via email, send a message with subject or body 'help' to > [email protected] > >You can reach the person managing the list at > [email protected] > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of at76c503a-user digest..." > > >Today's Topics: > > 1. Re: error to load driver (Derek Jennings) > 2. Re: error to load driver (Joerg Albert) > 3. How about new firmware ? (Alex Orlov) > 4. Any reported anomalies in 2.6.1 and /proc/net/wireless? (Mark >Fetterolf) > 5. Re: error to load driver (Luke Shen) > 6. Re: How about new firmware ? (Alex Orlov) > >--__--__-- > >Message: 1 >From: Derek Jennings <[email protected]> >To: [email protected] >Subject: Re: [at76c503a-user] error to load driver >Date: Wed, 28 Jan 2004 13:03:59 +0000 >Reply-To: [email protected] > >On Wednesday 28 Jan 2004 4:46 am, Luke Shen wrote: > > >Reply-To: [email protected] > > >To: [email protected] > > >Subject: Re: [at76c503a-user] error to load driver > > >Date: Tue, 27 Jan 2004 14:39:41 +0100 (CET) > > > > > >Hi, > > > > > >On Mon, 26 Jan 2004, Luke Shen wrote: > > > > Joerg, thank you very much for your tip. I got through the driver > > > > > >loading > > > > > > > problem by replug the USB adapter or do a cold boot. > > > > > >Guess you left the device plugged after a Windows run. The Windows >drivers > > >uses a different firmware version, which remained in the device causing > > >the previous problem (firmware version 0). > > > > > > > However, I was still not able to make through the whole process, >though > > > > > >I am > > > > > > > getting closer. Here is the new problem: > > > > > > > > After I loaded the driver and configured it with <iwconfig>, I was >able > > > > > >to > > > > > > > ping my Linksys USB11 ver. 2.6 with the following command: <ping > > > > 192.168.1.1>. All the packets are received. However, when I tried to > > > > > >ping an > > > > > > > outside address <ping 64.68.82.204>, I got error message: > > > > > > > > connect:network is unreachable > > > > > > > > That IP address is actually where google is, and it worked when I >tried > > > > > >to > > > > > > > ping it on Windows. > > > > > >Looks like you miss a default route to your router. > > > > > > > Here is background info: > > > > ... > > > > Link Quality:0 Signal Level:27 Noise Level:0 > > > > Rx invalid nwid:8 Rx invalid crypt:0 Rx invalid frag: 0 > > > > Tx execssive retries: 0 Invalid misc: 0 Missed beacon: 0 > > > > > > > > ("Link Quality:0" makes me suspicious, though I am not exactly sure > > > > what > > > > > >it > > > > > > > means.) > > > > > >no need to worry. The firmware in the device does not report link >quality > > >nor noise level (except on Intersil radios). > > > > > > > 3. <dmesg> return the following lines after I set <iwpriv wlan0 > > > > > >set_debug > > > > > > > 0x180003>: > > > > > > > > at76c503.c: wlan0:PRIV_IOCTL_SET_DEBUG input 9: )x180003 -> x180003 > > > > at76c503.c: wlan0:PRIV_IOCTL_SET_DEBUG, old 0x0 new 0x180003 > > > > at76c503.c: wlan0: netif running 1 queue_stopped 0 carrier_ok 1 > > > > > > > > (somewhere in the mail archive I learned that I should expect keylen > > > > and index displayed here in some "param:" line and they must be 13 >and > > > > 0. So something is wrong in my case.) > > > > > >no, looks fine as well - keylen/index is only displayed when the ioctl >are > > >debugged and a new key is set. > > > > > > > 4. <route -n> returns following: > > > > > > > > Kernel IP routing table > > > > Destination Gateway Genmask Flags Metric Ref > > > > Use Iface > > > > 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 > 0 > > > > wlan0 > > > > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 > > > > > >0 > > > > > > > l0 > > > > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 > 0 > > > > > > 0 > > > > > > > l0 > > > > > >That's your problem, you have no default route. How should the > > >network stack know where to send a packet with destination, > > >e.g. 64.68.82.204? I don't understand your network setup, what's the > > >169.254.0.0/16 network for (on the l0 device)? > > >Try to add a default route with > > > route add default gw <your router ip address> > > > > > > > 5. In order to verify that my configuration is correct, I did the > > > > > >following > > > > > > > experimentation: > > > > > > > > (1) replace "faosjtu" with a wrong string for "essid", <dmesg> >reports > > > > "essid didn't match". > > > > (2) use "faosjtu" for "essid", but set "key" to "off", <dmesg> >reports > > > > "requires encryption". > > > > (3) use "faosjtu" for "essid", but set "key" to some wrong value, > > > > > ><dmesg> > > > > > > > reports: > > > > "state 6->2 (AUTHENTICATING) > > > > state 2->3 (ASSOCIATING) > > > > state 3->7 (CONNECTED) > > > > connected to BSSID 00:06:25:b6:0b:41" > > > > (4) use "faosjtu" for "essid" and set "key" to the correct value, > > > > > ><dmesg> > > > > > > > reports exactly the same thing as in step (3). (This seems odd to >me.) > > > > > >As long as you use "open system" authentication, you will be able to > > >connect to an AP, but the data packets (IP etc.) exchanged later will >not > > >be correctly decoded. > > > > > > > I also tried to ping the router and yahoo during the above 4 steps. >In > > > > > >ALL > > > > > > > steps, I was able to ping the router correctly, but got the same > > > > > >"network > > > > > > > unreachable" error in the latter. (this also seems to be odd to me.) > > > > > >Strange indeed. You are sure to have pinged your _router_ , > > >not your own IP address (you've never mentioned these values)?? > > >Or you pinged it on a wrong interface, not on wlan. > > > > > >Ping times should be several milliseconds for 802.11b WLAN. > > >ping should succeed in case (4) only. > > > > > >Be aware, that you've posted your WEP key to the public! > > > > > >/Jörg > > > > > _______________________________________________ > > at76c503a-user mailing list > > [email protected] > > http://lists.berlios.de/mailman/listinfo/at76c503a-user > > Hi, I defined the default gateway with the following command"route add > > default gw 192.168.1.1". Now "route -n" returns the following: > > Kernel IP routing table > > Destination Gateway Genmask Flags Metric Ref Use Iface > > 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 > > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 l0 > > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 >l0 > > 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 > > wlan0 > > > > But still, I am not able to ping 64.68.82.204, got error like the > > following: "PING 64.68.82.204 (64.68.82.204) 56 (84) bytes of data > > From 192.168.1.1 icmp-seq=1 Destination Host Unreachable" > > > > But when I ping my router "ping 192.168.1.1", all the packets are >received. > > > > Any further advice? Thanks in advance. > > > > Luke > >Sorry I was too hasty posting. > >If you have a router or some other gateway then you need to define that as >the >gateway device > >route add default gw 192.168.1.xxx > >where xxx is the gateway device. > >derek >-- >veni, vidi, velcro >I came, I saw, I stuck around > > >--__--__-- > >Message: 2 >Date: Wed, 28 Jan 2004 15:48:35 +0100 (CET) >From: Joerg Albert <[email protected]> >To: [email protected] >Subject: Re: [at76c503a-user] error to load driver >Reply-To: [email protected] > >Hi, > >On Tue, 27 Jan 2004, Luke Shen wrote: > > > Hi, I defined the default gateway with the following command"route add > > default gw 192.168.1.1". Now "route -n" returns the following: > > Kernel IP routing table > > Destination Gateway Genmask Flags Metric Ref Use Iface > > 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 > > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 l0 > > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 >l0 > > 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 >wlan0 > > > > But still, I am not able to ping 64.68.82.204, got error like the >following: > > "PING 64.68.82.204 (64.68.82.204) 56 (84) bytes of data > > >From 192.168.1.1 icmp-seq=1 Destination Host Unreachable" > > > > But when I ping my router "ping 192.168.1.1", all the packets are >received. > >IMHO the problem now lies in your router's configuration (any firewall >rules there, any logfile to look into?). > >Try http access to some numeric ip address in the internet, >maybe ICMP (aka the ping requests/replies) is blocked by your router. > >/Jörg > >--__--__-- > >Message: 3 >From: Alex Orlov <[email protected]> >To: [email protected] >Date: Wed, 28 Jan 2004 18:42:39 +0300 >Subject: [at76c503a-user] How about new firmware ? >Reply-To: [email protected] > >Hi, > >Jan 28 18:33:10 fergus kernel: at76c503.c: wlan0: state 0 -> 1 (SCANNING) >Jan 28 18:33:12 fergus kernel: at76c503.c: wlan0 BSS table (curr=00000000, >new=00000000): >Jan 28 18:33:12 fergus kernel: at76c503.c: wlan0: state 1 -> 6 (JOINING) >Jan 28 18:33:12 fergus kernel: at76c503.c: wlan0 find_matching_bss: >returned cb0c47a0 >Jan 28 18:33:12 fergus kernel: at76c503.c: wlan0: state 6 -> 2 >(AUTHENTICATING) >Jan 28 18:33:12 fergus kernel: at76c503.c: wlan0: state 2 -> 6 (JOINING) >Jan 28 18:33:12 fergus kernel: at76c503.c: wlan0 find_matching_bss: >returned 00000000 >Jan 28 18:33:12 fergus kernel: at76c503.c: wlan0: state 6 -> 1 (SCANNING) >Jan 28 18:33:23 fergus kernel: at76c503.c: wlan0 BSS table (curr=00000000, >new=00000000): >Jan 28 18:33:24 fergus kernel: at76c503.c: wlan0: state 1 -> 6 (JOINING) >Jan 28 18:33:24 fergus kernel: at76c503.c: wlan0 find_matching_bss: >returned cb0c41a0 >Jan 28 18:33:24 fergus kernel: at76c503.c: wlan0: state 6 -> 2 >(AUTHENTICATING) >Jan 28 18:33:24 fergus kernel: at76c503.c: wlan0: state 2 -> 6 (JOINING) >Jan 28 18:33:24 fergus kernel: at76c503.c: wlan0 find_matching_bss: >returned 00000000 >Jan 28 18:33:24 fergus kernel: at76c503.c: wlan0: state 6 -> 1 (SCANNING) > >in cisco logs: >Station 00804820a0fd Failed Authentication, status "Unsupported >Authentication Algorithm" > >i use AP Cisco 350 (FW 11.03) and can not connect to it. If i use driver >from atmelwlandriver.sourceforge.net all fork fine! >In atmelwlandriver distrubution: firmware 1.103.2.164... > >at76c503.c: firmware version 1.101.2 #84 (fcs_len 4) > > >--__--__-- > >Message: 4 >From: Mark Fetterolf <[email protected]> >To: [email protected] >Organization: >Date: 28 Jan 2004 07:57:06 -0800 >Subject: [at76c503a-user] Any reported anomalies in 2.6.1 and >/proc/net/wireless? >Reply-To: [email protected] > >Hello everyone, > >I am using the WUSB linksys NIC version 2.6 on a 2.6.1 kernel. Very >nice job on the driver. The only thing I am seeing wierd is >/proc/net/wireless reports strangely/nothing at all. > >Here is my current output. > >Inter-| sta-| Quality | Discarded packets | Missed | WE >face | tus |link level noise|nwid crypt frag retry misc| beacon | 16 >wlan0: 0000 0. 20 0. 0 0 0 0 0 0 > > >Note that the Quality level is the only field that shows a value. In >2.4.* if I remeber correcttttly it showed some information. Is this a >kernel or driver issue? > >Thanks in advance! >Mark > > >--__--__-- > >Message: 5 >From: "Luke Shen" <[email protected]> >To: [email protected] >Subject: Re: [at76c503a-user] error to load driver >Date: Wed, 28 Jan 2004 22:56:06 -0500 >Reply-To: [email protected] > >Yeah, my intuition is that the gateway is added to the routing table >correctly, but there is still something wrong with my configuration. But I >am too illiterate in networking/linux to figure this out. > >So here is a piece of additional information I got tonight and hope someone >can provide me better diagnosis. I have mentioned in my previous email that >I am able to ping my router, ie, 192.168.1.1, but I am not able to ping >google, ie, 64.68.82.204. Joerg suggested me to try to http to some numeric >ip address. So I tried it out on Mozilla. > >First of all, Mozilla showed my status as online (which is sort of good >news). When I tried to "http://64.68.82.204", I immediately got "The >connection was refulsed when attempting to contact 64.68.82.204". I thought >it was normal because I was not able to http to that ip addres on Windows >either (probably there is not http server at that address, I guess). >However, the next thing became really strange/interesting. My router has >its >own homepage for configuration and I can access it with >"http://192.168.1.1" >on Windows Internet Explorer. However, when I tried the same address on >Mozilla, I instantly got the same error message "The connection was refused >when attempting to contact 192.168.1.1". This seems to be very weird to me, >because I was able to ping the same ip address successfully. > >In my previous post, I have also mentioned another problem. When I use >"iwconfig" and provide a wrong "essid" value and set "key off" (my router >has WEP enabled), I was still able to ping my router without any error. So >far I have not got any good explanation on this weird behavior. Would those >two problems somehow related? > >Again, any help will be greatly appreciated. > >Luke > > > >From: Joerg Albert <[email protected]> > >Reply-To: [email protected] > >To: [email protected] > >Subject: Re: [at76c503a-user] error to load driver > >Date: Wed, 28 Jan 2004 15:48:35 +0100 (CET) > > > >Hi, > > > >On Tue, 27 Jan 2004, Luke Shen wrote: > > > > > Hi, I defined the default gateway with the following command"route add > > > default gw 192.168.1.1". Now "route -n" returns the following: > > > Kernel IP routing table > > > Destination Gateway Genmask Flags Metric Ref Use Iface > > > 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 >wlan0 > > > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 >l0 > > > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 > >l0 > > > 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 > >wlan0 > > > > > > But still, I am not able to ping 64.68.82.204, got error like the > >following: > > > "PING 64.68.82.204 (64.68.82.204) 56 (84) bytes of data > > > >From 192.168.1.1 icmp-seq=1 Destination Host Unreachable" > > > > > > But when I ping my router "ping 192.168.1.1", all the packets are > >received. > > > >IMHO the problem now lies in your router's configuration (any firewall > >rules there, any logfile to look into?). > > > >Try http access to some numeric ip address in the internet, > >maybe ICMP (aka the ping requests/replies) is blocked by your router. > > > >/Jörg > >_______________________________________________ > >at76c503a-user mailing list > >[email protected] > >http://lists.berlios.de/mailman/listinfo/at76c503a-user > >_________________________________________________________________ >Let the new MSN Premium Internet Software make the most of your high-speed >experience. http://join.msn.com/?pgmarket=en-us&page=byoa/prem&ST=1 > > >--__--__-- > >Message: 6 >From: Alex Orlov <[email protected]> >To: [email protected] >Subject: Re: [at76c503a-user] How about new firmware ? >Date: Thu, 29 Jan 2004 09:47:16 +0300 >Reply-To: [email protected] > >It work! i use >#iwpriv wlan0 auth_mode 1 >and can connect to cisco ;) > > >--__--__-- > >_______________________________________________ >at76c503a-user mailing list >[email protected] >http://lists.berlios.de/mailman/listinfo/at76c503a-user > > >End of at76c503a-user Digest _________________________________________________________________ Charla con tus amigos en línea mediante MSN Messenger. http://messenger.microsoft.com/es