Thread: [Madwifi-users] (no subject)
Status: Beta
Brought to you by:
otaku
From: Thomas M. H. <Tho...@al...> - 2003-09-10 00:34:39
Attachments:
dmesg_output.txt
|
Hello all -- I hope it is appropriate to ask for support of the madwifi driver on this list. I am having trouble getting this driver up and running. Because I don't know what's going on, I'll give as much info as possible in this e-mail and hope for some help. I have my system configured so that when pcmcia sees my card it tries to load the ath_pci module of the kernel. This part works successfully -- inserting the card gets me a high happy beep followed by a sad low beep. /var/log/messages shows that the driver can't seem to find the device: Sep 9 20:16:47 lacky kernel: cs: cb_free(bus 2) Sep 9 20:16:47 lacky cardmgr[312]: executing: 'modprobe -r ath_pci' Sep 9 20:16:49 lacky kernel: cs: cb_alloc(bus 2): vendor 0x168c, device 0x0012 Sep 9 20:16:49 lacky cardmgr[312]: socket 0: Atheros Communications, Inc. Sep 9 20:16:49 lacky cardmgr[312]: executing: 'modprobe ath_pci' Sep 9 20:16:49 lacky cardmgr[312]: + Warning: loading /lib/modules/2.4.20-lac8/net/ath_hal.o will taint the kernel: non-GPL license - Proprietary Sep 9 20:16:49 lacky cardmgr[312]: + See http://www.tux.org/lkml/#export-tainted for information about tainted modules Sep 9 20:16:49 lacky kernel: ath_hal: 0.9.5.3 BETA (Sam Leffler <sa...@er...>) Sep 9 20:16:49 lacky cardmgr[312]: + Module ath_hal loaded, with warnings Sep 9 20:16:49 lacky kernel: wlan: 0.7.1.1 BETA (Sam Leffler <sa...@er...>) Sep 9 20:16:49 lacky cardmgr[312]: + Module wlan loaded, with warnings Sep 9 20:16:49 lacky kernel: ath_pci: 0.8.3.2 BETA (Sam Leffler <sa...@er...>) Sep 9 20:16:49 lacky kernel: ath_pci: cache line size not set; forcing 32 Sep 9 20:16:49 lacky kernel: ath_pci: cannot reserve PCI memory region Sep 9 20:16:49 lacky kernel: ath_pci: No devices found, driver not installed. Sep 9 20:16:49 lacky cardmgr[312]: + /lib/modules/2.4.20-lac8/net/ath_pci.o: init_module: No such device Sep 9 20:16:49 lacky cardmgr[312]: + /lib/modules/2.4.20-lac8/net/ath_pci.o: insmod /lib/modules/2.4.20-lac8/net/ath_pci.o failed Sep 9 20:16:49 lacky kernel: wlan: driver unloaded Sep 9 20:16:49 lacky kernel: ath_hal: driver unloaded Sep 9 20:16:49 lacky cardmgr[312]: + /lib/modules/2.4.20-lac8/net/ath_pci.o: insmod ath_pci failed Sep 9 20:16:49 lacky cardmgr[312]: + Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ paramete rs. Sep 9 20:16:49 lacky cardmgr[312]: + You may find more information in syslog or the output from dmesg Sep 9 20:16:49 lacky cardmgr[312]: modprobe exited with status 255 Sep 9 20:16:49 lacky cardmgr[312]: module /lib/modules/2.4.20-lac8/pcmcia/ath_pci.o not available Sep 9 20:16:50 lacky cardmgr[312]: get dev info on socket 0 failed: Resource temporarily unavailable I have been told this likely means I have the wrong driver for my card. So, to clarify what this thing is... lacky:/home/tom# cardctl ident Socket 0: product info: "Atheros Communications, Inc.", "AR5001-0000-0000", "Wireless LAN Reference Card", "00" manfid: 0x0271, 0x0012 function: 6 (network) PCI id: 0x168c, 0x0012 lacky:/home/tom# cardctl info PRODID_1="Atheros Communications, Inc." PRODID_2="AR5001-0000-0000" PRODID_3="Wireless LAN Reference Card" PRODID_4="00" MANFID=0271,0012 FUNCID=6 Note that MANFID=0271, which seems strange -- I thought the manufacturer code for this chip ought to be 168c (the PCI id). Could this be the source of my problem? If so is there any hope? It seems clear that the chip identifies itself as atheros (i.e. this driver). The physical card has the following identifying information: Proxim 802.11a/b ComboCard Model 8461-05 Orinoco Wireless Networks Silver PCCARD 3.3V 32 The one other piece of strange behavior is that when I insert the card, lspci no longer properly lists my pci devices. Instead, I get the following error: lacky:/home/tom# lspci pcilib: Cannot open /proc/bus/pci/02/00.0 lspci: Unable to read 64 bytes of configuration space. Please let me know if you can make any sense of this. I bought the card labelled "Orinoco" because I thought it would be straightforward to get it running on linux (it was near the top of the Wireless-HOWTO list). Now I've moved past the orinoco drivers (orinoco_cs, wavelan, etc.) and gotten to this madwifi driver based on the card's own reported information. At this point, I'm afraid I'm stuck so any further help would be greatly appreciated. I'll attach the output from dmesg in case it is helpful. Thank you, Tom Hinkle |
From: <ell...@gr...> - 2003-09-13 18:07:03
|
I am trying to use the madwifi drivers (20030802, downloaded freshly) with a custom-built 2.4.22-ac2 kernel(debian mixed) on a T40 with the 802.11a/b mini-pci card. I can successfully build the drivers with no errors, but I do not get the ath_hal.o module as it says in the README. Instead, I get ah_osdep.o, which spews unresolved symbols when I try to insmod it. Do I have a bad tar? Is there something else I need to do, and the README just hasn't been updated? Further, is there any way to search the mailing list archives? insmod screen dump: elliotf@frog /hm/lltf/wrkng/mdwf-20030802 $ sudo insmod wlan/wlan.o elliotf@frog /hm/lltf/wrkng/mdwf-20030802 $ sudo insmod ath_hal/ah_osdep.o ath_hal/ah_osdep.o: unresolved symbol ath_hal_attach ath_hal/ah_osdep.o: unresolved symbol ath_hal_ieee2mhz ath_hal/ah_osdep.o: unresolved symbol ath_hal_mhz2ieee ath_hal/ah_osdep.o: unresolved symbol ath_hal_init_channels ath_hal/ah_osdep.o: unresolved symbol ath_hal_probe ath_hal/ah_osdep.o: unresolved symbol ath_hal_getwirelessmodes ath_hal/ah_osdep.o: unresolved symbol ath_hal_computetxtime ath_hal/ah_osdep.o: Hint: You are trying to load a module without a GPL compatible license and it has unresolved symbols. Contact the module supplier for assistance, only they can help you. file list: elliotf@frog /hm/lltf/wrkng/mdwf-20030802 $ find . /ath_hal /ath_hal/Makefile /ath_hal/opt_ah.h /ath_hal/.depend /ath_hal/ah_osdep.o /COPYRIGHT /Makefile /Makefile.inc /README /release.h /driver /driver/Makefile /driver/if_ath.c /driver/if_ath_pci.c /driver/if_athvar.h /driver/version.h /driver/.depend /driver/if_ath.o /driver/if_ath_pci.o /driver/ath_pci.o /include /include/sys /include/sys/queue.h /include/compat.h /wlan /wlan/Makefile /wlan/if_ethersubr.h /wlan/if_ieee80211.h /wlan/if_ieee80211ioctl.h /wlan/if_ieee80211subr.c /wlan/if_ieee80211wireless.c /wlan/if_llc.h /wlan/if_media.c /wlan/if_media.h /wlan/if_wavelan_ieee.h /wlan/rc4.c /wlan/rc4.h /wlan/version.h /wlan/if_ieee80211.ver /wlan/if_media.ver /wlan/.depend /wlan/if_ieee80211subr.o /wlan/if_ieee80211wireless.o /wlan/if_media.o /wlan/rc4.o /wlan/wlan.o /hal /hal/COPYRIGHT /hal/README /hal/ah.h /hal/ah_desc.h /hal/ah_devid.h /hal/version.h /hal/linux /hal/linux/ah_osdep.c /hal/linux/ah_osdep.h /hal/linux/i386-elf.hal.o.uu /hal/linux/opt_ah.h |
From: <dh...@id...> - 2003-12-11 12:05:37
|
I am very close to getting this to work I think. I am not able to make the connection to the wireless access point(WAP). Here is some data: [root@ntclap4 root]# iwlist ath0 scan ath0 No scan results [root@ntclap4 root]# iwconfig lo no wireless extensions. eth0 no wireless extensions. ath0 IEEE 802.11b ESSID:"NTCOIS" Mode:Managed Frequency:2.412GHz Access Point: FF:FF:FF:FF:FF:FF Bit Rate:0kb/s Tx-Power:off Sensitivity=0/3 Retry:off RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0/94 Signal level:-95 dBm Noise level:-95 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 I have the ESSID set to NTCOIS on the WAP. I have the WAP ESSID set to NTCOIS. I am running my wireless card in 802.11b mode only. The readme file indicates that I need to "bring the interface up". How is that done? Do you have any suggestions as to things to try? I am able to connect to the WAP using Windows XP and a Netgear card. Dan Also getting this message many times in dmesg: D-Link DE-620 pocket adapter not identified in the printer port divert: no divert_blk to free, eth1 not ethernet divert: not allocating divert_blk for non-ethernet device eth1 -------------------------------------------- ath_hal: 0.9.6.3 wlan: 0.7.2.0 BETA ath_pci: 0.8.4.0 BETA ath_pci: cache line size not set; forcing 32 divert: allocating divert_blk for ath0 ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps ath0: turbo rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ath0: 802.11 address: 00:20:a6:4c:c1:f3 ath0: Atheros 5211: mem=0x21000000, irq=11 |
From: Terry S. <gal...@ma...> - 2003-12-11 17:21:52
|
Dan, Use "ifconfig" to bring the interface up: "ifconfig ath0 up" should work. - Terry On Dec 11, 2003, at 5:06 AM, dh...@id... wrote: > > I am very close to getting this to work I think. I am not able to make > the connection to the wireless access point(WAP). Here is some data: > > [root@ntclap4 root]# iwlist ath0 scan > ath0 No scan results > > [root@ntclap4 root]# iwconfig > lo no wireless extensions. > > eth0 no wireless extensions. > > ath0 IEEE 802.11b ESSID:"NTCOIS" > Mode:Managed Frequency:2.412GHz Access Point: > FF:FF:FF:FF:FF:FF Bit Rate:0kb/s Tx-Power:off > Sensitivity=0/3 > Retry:off RTS thr:off Fragment thr:off > Encryption key:off > Power Management:off > Link Quality:0/94 Signal level:-95 dBm Noise level:-95 dBm > Rx > invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx > excessive retries:0 Invalid misc:0 Missed beacon:0 > > I have the ESSID set to NTCOIS on the WAP. I have the WAP ESSID set to > NTCOIS. I am running my wireless card in 802.11b mode only. > > The readme file indicates that I need to "bring the interface up". How > is > that done? Do you have any suggestions as to things to try? > > I am able to connect to the WAP using Windows XP and a Netgear card. > > Dan > > Also getting this message many times in dmesg: > > D-Link DE-620 pocket adapter not identified in the printer port > divert: no divert_blk to free, eth1 not ethernet > divert: not allocating divert_blk for non-ethernet device eth1 > -------------------------------------------- > ath_hal: 0.9.6.3 > wlan: 0.7.2.0 BETA > ath_pci: 0.8.4.0 BETA > ath_pci: cache line size not set; forcing 32 > divert: allocating divert_blk for ath0 > ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps > ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > ath0: turbo rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps > 54Mbps > ath0: 802.11 address: 00:20:a6:4c:c1:f3 > ath0: Atheros 5211: mem=0x21000000, irq=11 > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for > IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys > admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Madwifi-users mailing list > Mad...@li... > https://lists.sourceforge.net/lists/listinfo/madwifi-users |
From: <dh...@id...> - 2003-12-11 17:45:26
|
It seems my wireless card is making a connection to the access point based on the results of iwlist. How do I get my applications (browser,etc) to use ath0 rather than my wired eth0 connection? Here is my data. I am not sure if the output of ifconfig is applicable but I included it anyway. [root@ntclap4 root]# ifconfig ath0 192.168.200.44 up [root@ntclap4 root]# iwconfig ath0 essid "NTCOIS1" [root@ntclap4 root]# iwlist ath0 ap ath0 Peers/Access-Points in range: 00:09:5B:51:46:B2 : Quality:43/94 Signal level:-52 dBm Noise level:-95 dBm (updated) [root@ntclap4 root]# iwconfig ath0 ath0 IEEE 802.11 ESSID:"NTCOIS1" Mode:Managed Frequency:5.24GHz Access Point: FF:FF:FF:FF:FF:FF Bit Rate:6Mb/s Tx-Power:off Sensitivity=0/3 Retry:off RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0/94 Signal level:-95 dBm Noise level:-95 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 [root@ntclap4 root]# ifconfig atho atho: error fetching interface information: Device not found [root@ntclap4 root]# ifconfig ath0 ath0 Link encap:Ethernet HWaddr 00:20:A6:4C:C1:F3 inet addr:192.168.200.44 Bcast:192.168.200.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:666 errors:26 dropped:0 overruns:0 frame:26 TX packets:59 errors:1 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:199 RX bytes:32955 (32.1 Kb) TX bytes:2469 (2.4 Kb) Interrupt:11 Memory:e1b91000-e1ba1000 > Dan, > > Use "ifconfig" to bring the interface up: > > "ifconfig ath0 up" should work. > > - Terry > > On Dec 11, 2003, at 5:06 AM, dh...@id... wrote: > >> >> I am very close to getting this to work I think. I am not able to make >> the connection to the wireless access point(WAP). Here is some data: >> >> [root@ntclap4 root]# iwlist ath0 scan >> ath0 No scan results >> >> [root@ntclap4 root]# iwconfig >> lo no wireless extensions. >> >> eth0 no wireless extensions. >> >> ath0 IEEE 802.11b ESSID:"NTCOIS" >> Mode:Managed Frequency:2.412GHz Access Point: >> FF:FF:FF:FF:FF:FF Bit Rate:0kb/s Tx-Power:off >> Sensitivity=0/3 >> Retry:off RTS thr:off Fragment thr:off >> Encryption key:off >> Power Management:off >> Link Quality:0/94 Signal level:-95 dBm Noise level:-95 dBm >> Rx >> invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx >> excessive retries:0 Invalid misc:0 Missed beacon:0 >> >> I have the ESSID set to NTCOIS on the WAP. I have the WAP ESSID set to >> NTCOIS. I am running my wireless card in 802.11b mode only. >> >> The readme file indicates that I need to "bring the interface up". How >> is >> that done? Do you have any suggestions as to things to try? >> >> I am able to connect to the WAP using Windows XP and a Netgear card. >> >> Dan >> >> Also getting this message many times in dmesg: >> >> D-Link DE-620 pocket adapter not identified in the printer port >> divert: no divert_blk to free, eth1 not ethernet >> divert: not allocating divert_blk for non-ethernet device eth1 >> -------------------------------------------- >> ath_hal: 0.9.6.3 >> wlan: 0.7.2.0 BETA >> ath_pci: 0.8.4.0 BETA >> ath_pci: cache line size not set; forcing 32 >> divert: allocating divert_blk for ath0 >> ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps >> ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps >> ath0: turbo rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps >> 54Mbps >> ath0: 802.11 address: 00:20:a6:4c:c1:f3 >> ath0: Atheros 5211: mem=0x21000000, irq=11 >> >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: IBM Linux Tutorials. >> Become an expert in LINUX or just sharpen your skills. Sign up for >> IBM's >> Free Linux Tutorials. Learn everything from the bash shell to sys >> admin. >> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click >> _______________________________________________ >> Madwifi-users mailing list >> Mad...@li... >> https://lists.sourceforge.net/lists/listinfo/madwifi-users > > |
From: Terry S. <gal...@ma...> - 2003-12-11 18:17:29
|
You'll need to change your default route to get that to work. Another way to do it would be to disconnect both interfaces, and then only reconnect ath0. That should take care of the gateway stuff for you, assuming you're using DHCP on your wireless interface, and that your DHCP server is handing out a default gateway. Otherwise you'll have to do it by hand. - Terry On Dec 11, 2003, at 10:46 AM, dh...@id... wrote: > It seems my wireless card is making a connection to the access point > based > on the results of iwlist. How do I get my applications (browser,etc) > to > use ath0 rather than my wired eth0 connection? Here is my data. I am > not > sure if the output of ifconfig is applicable but I included it anyway. > > [root@ntclap4 root]# ifconfig ath0 192.168.200.44 up > [root@ntclap4 root]# iwconfig ath0 essid "NTCOIS1" > [root@ntclap4 root]# iwlist ath0 ap > ath0 Peers/Access-Points in range: > 00:09:5B:51:46:B2 : Quality:43/94 Signal level:-52 dBm Noise > level:-95 dBm (updated) > > [root@ntclap4 root]# iwconfig ath0 > ath0 IEEE 802.11 ESSID:"NTCOIS1" > Mode:Managed Frequency:5.24GHz Access Point: > FF:FF:FF:FF:FF:FF > Bit Rate:6Mb/s Tx-Power:off Sensitivity=0/3 > Retry:off RTS thr:off Fragment thr:off > Encryption key:off > Power Management:off > Link Quality:0/94 Signal level:-95 dBm Noise level:-95 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > [root@ntclap4 root]# ifconfig atho > atho: error fetching interface information: Device not found > [root@ntclap4 root]# ifconfig ath0 > ath0 Link encap:Ethernet HWaddr 00:20:A6:4C:C1:F3 > inet addr:192.168.200.44 Bcast:192.168.200.255 > Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:666 errors:26 dropped:0 overruns:0 frame:26 > TX packets:59 errors:1 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:199 > RX bytes:32955 (32.1 Kb) TX bytes:2469 (2.4 Kb) > Interrupt:11 Memory:e1b91000-e1ba1000 > > > >> Dan, >> >> Use "ifconfig" to bring the interface up: >> >> "ifconfig ath0 up" should work. >> >> - Terry >> >> On Dec 11, 2003, at 5:06 AM, dh...@id... wrote: >> >>> >>> I am very close to getting this to work I think. I am not able to >>> make >>> the connection to the wireless access point(WAP). Here is some data: >>> >>> [root@ntclap4 root]# iwlist ath0 scan >>> ath0 No scan results >>> >>> [root@ntclap4 root]# iwconfig >>> lo no wireless extensions. >>> >>> eth0 no wireless extensions. >>> >>> ath0 IEEE 802.11b ESSID:"NTCOIS" >>> Mode:Managed Frequency:2.412GHz Access Point: >>> FF:FF:FF:FF:FF:FF Bit Rate:0kb/s Tx-Power:off >>> Sensitivity=0/3 >>> Retry:off RTS thr:off Fragment thr:off >>> Encryption key:off >>> Power Management:off >>> Link Quality:0/94 Signal level:-95 dBm Noise level:-95 >>> dBm >>> Rx >>> invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx >>> excessive retries:0 Invalid misc:0 Missed beacon:0 >>> >>> I have the ESSID set to NTCOIS on the WAP. I have the WAP ESSID set >>> to >>> NTCOIS. I am running my wireless card in 802.11b mode only. >>> >>> The readme file indicates that I need to "bring the interface up". >>> How >>> is >>> that done? Do you have any suggestions as to things to try? >>> >>> I am able to connect to the WAP using Windows XP and a Netgear card. >>> >>> Dan >>> >>> Also getting this message many times in dmesg: >>> >>> D-Link DE-620 pocket adapter not identified in the printer port >>> divert: no divert_blk to free, eth1 not ethernet >>> divert: not allocating divert_blk for non-ethernet device eth1 >>> -------------------------------------------- >>> ath_hal: 0.9.6.3 >>> wlan: 0.7.2.0 BETA >>> ath_pci: 0.8.4.0 BETA >>> ath_pci: cache line size not set; forcing 32 >>> divert: allocating divert_blk for ath0 >>> ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps >>> 54Mbps >>> ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps >>> ath0: turbo rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps >>> 54Mbps >>> ath0: 802.11 address: 00:20:a6:4c:c1:f3 >>> ath0: Atheros 5211: mem=0x21000000, irq=11 >>> >>> >>> >>> >>> ------------------------------------------------------- >>> This SF.net email is sponsored by: IBM Linux Tutorials. >>> Become an expert in LINUX or just sharpen your skills. Sign up for >>> IBM's >>> Free Linux Tutorials. Learn everything from the bash shell to sys >>> admin. >>> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click >>> _______________________________________________ >>> Madwifi-users mailing list >>> Mad...@li... >>> https://lists.sourceforge.net/lists/listinfo/madwifi-users >> >> > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for > IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys > admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Madwifi-users mailing list > Mad...@li... > https://lists.sourceforge.net/lists/listinfo/madwifi-users |
From: <dh...@id...> - 2003-12-11 21:31:47
|
These are the steps I am performing: 1) ifconfig eth0 down 2) ifconfig lo down 3) [root@ntclap4 root]# iwconfig lo no wireless extensions. eth0 no wireless extensions. 4) Push the wireless card into its slot. 5) [root@ntclap4 root]# iwconfig ath0 ath0 IEEE 802.11 ESSID:"" Mode:Managed Frequency:2.412GHz Access Point: 00:00:00:00:00:00 Bit Rate:0kb/s Tx-Power:off Sensitivity=0/3 Retry:off RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0/94 Signal level:-95 dBm Noise level:-95 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 6) [root@ntclap4 root]# iwconfig ath0 essid "NTCOIS1" 7) [root@ntclap4 root]# iwconfig ath0 ath0 IEEE 802.11 ESSID:"NTCOIS1" Mode:Managed Frequency:5.805GHz Access Point: FF:FF:FF:FF:FF:FF Bit Rate:6Mb/s Tx-Power:off Sensitivity=0/3 Retry:off RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0/94 Signal level:-95 dBm Noise level:-95 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 8) [root@ntclap4 root]# ifconfig ath0 up 9) [root@ntclap4 root]# ifconfig ath0 Link encap:Ethernet HWaddr 00:20:A6:4C:C1:F3 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:24 errors:0 dropped:0 overruns:0 frame:0 TX packets:41 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:199 RX bytes:1677 (1.6 Kb) TX bytes:1847 (1.8 Kb) Interrupt:11 Memory:e1bc5000-e1bd5000 A minute later: 10)[root@ntclap4 root]# ifconfig ath0 Link encap:Ethernet HWaddr 00:20:A6:4C:C1:F3 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:201 errors:4 dropped:0 overruns:0 frame:4 TX packets:58 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:199 RX bytes:13910 (13.5 Kb) TX bytes:2638 (2.5 Kb) Interrupt:11 Memory:e1bc5000-e1bd5000 [root@ntclap4 root]# iwlist ath0 ap ath0 Peers/Access-Points in range: 00:09:5B:51:46:B2 : Quality:43/94 Signal level:-52 dBm Noise level:-95 dBm (updated) 11) root@localhost root]# dhclient ath0 Internet Software Consortium DHCP Client V3.0pl2 Copyright 1995-2001 Internet Software Consortium. All rights reserved. For info, please visit http://www.isc.org/products/DHCP Listening on LPF/ath0/00:20:a6:4c:c1:f3 Sending on LPF/ath0/00:20:a6:4c:c1:f3 Sending on Socket/fallback DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 3 DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 3 DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6 DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 14 DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 18 No DHCPOFFERS received. No working leases in persistent database - sleeping. Seems to be the access poing DHCP server is not responding or possibly not getting the DHCPDISCOVER. Why is the Tx-Power off in the iwconfig ath0 response? 12) Here is the contents of ifcfg-ath0 [root@localhost network-scripts]# cat ifcfg-ath0 # Please read /usr/share/doc/initscripts-*/sysconfig.txt # for the documentation of these parameters. ONBOOT=yes USERCTL=no PEERDNS=no GATEWAY= TYPE=Wireless DHCP_HOSTNAME= IPADDR= DEVICE=ath0 HWADDR=00:20:a6:4c:c1:f3 BOOTPROTO=dhcp DOMAIN= NETMASK= ESSID=NTCOIS1 CHANNEL=1 MODE=Managed RATE=Auto Does this look ok? 13) Again I believe the access point DHCP server is working fine since it works with the Windows XP wireless configuration. 14) Why are all of the TX/RX errors occuring? > You'll need to change your default route to get that to work. > > Another way to do it would be to disconnect both interfaces, and then > only reconnect ath0. > > That should take care of the gateway stuff for you, assuming you're > using DHCP on your wireless interface, and that your DHCP server is > handing out a default gateway. > > Otherwise you'll have to do it by hand. > > - Terry > > > On Dec 11, 2003, at 10:46 AM, dh...@id... wrote: > >> It seems my wireless card is making a connection to the access point >> based >> on the results of iwlist. How do I get my applications (browser,etc) >> to >> use ath0 rather than my wired eth0 connection? Here is my data. I am >> not >> sure if the output of ifconfig is applicable but I included it anyway. >> >> [root@ntclap4 root]# ifconfig ath0 192.168.200.44 up >> [root@ntclap4 root]# iwconfig ath0 essid "NTCOIS1" >> [root@ntclap4 root]# iwlist ath0 ap >> ath0 Peers/Access-Points in range: >> 00:09:5B:51:46:B2 : Quality:43/94 Signal level:-52 dBm Noise >> level:-95 dBm (updated) >> >> [root@ntclap4 root]# iwconfig ath0 >> ath0 IEEE 802.11 ESSID:"NTCOIS1" >> Mode:Managed Frequency:5.24GHz Access Point: >> FF:FF:FF:FF:FF:FF >> Bit Rate:6Mb/s Tx-Power:off Sensitivity=0/3 >> Retry:off RTS thr:off Fragment thr:off >> Encryption key:off >> Power Management:off >> Link Quality:0/94 Signal level:-95 dBm Noise level:-95 dBm >> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >> Tx excessive retries:0 Invalid misc:0 Missed beacon:0 >> >> [root@ntclap4 root]# ifconfig atho >> atho: error fetching interface information: Device not found >> [root@ntclap4 root]# ifconfig ath0 >> ath0 Link encap:Ethernet HWaddr 00:20:A6:4C:C1:F3 >> inet addr:192.168.200.44 Bcast:192.168.200.255 >> Mask:255.255.255.0 >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:666 errors:26 dropped:0 overruns:0 frame:26 >> TX packets:59 errors:1 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:199 >> RX bytes:32955 (32.1 Kb) TX bytes:2469 (2.4 Kb) >> Interrupt:11 Memory:e1b91000-e1ba1000 >> >> >> >>> Dan, >>> >>> Use "ifconfig" to bring the interface up: >>> >>> "ifconfig ath0 up" should work. >>> >>> - Terry >>> >>> On Dec 11, 2003, at 5:06 AM, dh...@id... wrote: >>> >>>> >>>> I am very close to getting this to work I think. I am not able to >>>> make >>>> the connection to the wireless access point(WAP). Here is some data: >>>> >>>> [root@ntclap4 root]# iwlist ath0 scan >>>> ath0 No scan results >>>> >>>> [root@ntclap4 root]# iwconfig >>>> lo no wireless extensions. >>>> >>>> eth0 no wireless extensions. >>>> >>>> ath0 IEEE 802.11b ESSID:"NTCOIS" >>>> Mode:Managed Frequency:2.412GHz Access Point: >>>> FF:FF:FF:FF:FF:FF Bit Rate:0kb/s Tx-Power:off >>>> Sensitivity=0/3 >>>> Retry:off RTS thr:off Fragment thr:off >>>> Encryption key:off >>>> Power Management:off >>>> Link Quality:0/94 Signal level:-95 dBm Noise level:-95 >>>> dBm >>>> Rx >>>> invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx >>>> excessive retries:0 Invalid misc:0 Missed beacon:0 >>>> >>>> I have the ESSID set to NTCOIS on the WAP. I have the WAP ESSID set >>>> to >>>> NTCOIS. I am running my wireless card in 802.11b mode only. >>>> >>>> The readme file indicates that I need to "bring the interface up". >>>> How >>>> is >>>> that done? Do you have any suggestions as to things to try? >>>> >>>> I am able to connect to the WAP using Windows XP and a Netgear card. >>>> >>>> Dan >>>> >>>> Also getting this message many times in dmesg: >>>> >>>> D-Link DE-620 pocket adapter not identified in the printer port >>>> divert: no divert_blk to free, eth1 not ethernet >>>> divert: not allocating divert_blk for non-ethernet device eth1 >>>> -------------------------------------------- >>>> ath_hal: 0.9.6.3 >>>> wlan: 0.7.2.0 BETA >>>> ath_pci: 0.8.4.0 BETA >>>> ath_pci: cache line size not set; forcing 32 >>>> divert: allocating divert_blk for ath0 >>>> ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps >>>> 54Mbps >>>> ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps >>>> ath0: turbo rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps >>>> 54Mbps >>>> ath0: 802.11 address: 00:20:a6:4c:c1:f3 >>>> ath0: Atheros 5211: mem=0x21000000, irq=11 >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------- >>>> This SF.net email is sponsored by: IBM Linux Tutorials. >>>> Become an expert in LINUX or just sharpen your skills. Sign up for >>>> IBM's >>>> Free Linux Tutorials. Learn everything from the bash shell to sys >>>> admin. >>>> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click >>>> _______________________________________________ >>>> Madwifi-users mailing list >>>> Mad...@li... >>>> https://lists.sourceforge.net/lists/listinfo/madwifi-users >>> >>> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: IBM Linux Tutorials. >> Become an expert in LINUX or just sharpen your skills. Sign up for >> IBM's >> Free Linux Tutorials. Learn everything from the bash shell to sys >> admin. >> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click >> _______________________________________________ >> Madwifi-users mailing list >> Mad...@li... >> https://lists.sourceforge.net/lists/listinfo/madwifi-users > > |
From: Terry S. <gal...@ma...> - 2003-12-11 22:54:51
|
Try doing an ifconfig ath0 up before you set your ESSID, then set the ESSID, and see if your card is actually associating to the AP correctly. Without an association, you won't be able to pass traffic... and it's not clear to me with the information below if you are actually associated after you bring the interface up. The iwlist command doesn't show you what you are associated to, it only shows APs that are in range. Use iwconfig to look at your association. Check the "Access Point: " area in the iwconfig output. If your output is "Access Point: FF:FF:FF:FF:FF:FF" then you are not associated. I usually up the interface before I do anything with iwconfig. This shouldn't make a difference, but who knows. - Terry On Dec 11, 2003, at 2:32 PM, dh...@id... wrote: > These are the steps I am performing: > > 1) ifconfig eth0 down > 2) ifconfig lo down > 3) [root@ntclap4 root]# iwconfig > lo no wireless extensions. > > eth0 no wireless extensions. > > 4) Push the wireless card into its slot. > > 5) [root@ntclap4 root]# iwconfig ath0 > ath0 IEEE 802.11 ESSID:"" > Mode:Managed Frequency:2.412GHz Access Point: > 00:00:00:00:00:00 > Bit Rate:0kb/s Tx-Power:off Sensitivity=0/3 > Retry:off RTS thr:off Fragment thr:off > Encryption key:off > Power Management:off > Link Quality:0/94 Signal level:-95 dBm Noise level:-95 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > 6) [root@ntclap4 root]# iwconfig ath0 essid "NTCOIS1" > > 7) [root@ntclap4 root]# iwconfig ath0 > ath0 IEEE 802.11 ESSID:"NTCOIS1" > Mode:Managed Frequency:5.805GHz Access Point: > FF:FF:FF:FF:FF:FF > Bit Rate:6Mb/s Tx-Power:off Sensitivity=0/3 > Retry:off RTS thr:off Fragment thr:off > Encryption key:off > Power Management:off > Link Quality:0/94 Signal level:-95 dBm Noise level:-95 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > 8) [root@ntclap4 root]# ifconfig ath0 up > 9) [root@ntclap4 root]# ifconfig > ath0 Link encap:Ethernet HWaddr 00:20:A6:4C:C1:F3 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:24 errors:0 dropped:0 overruns:0 frame:0 > TX packets:41 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:199 > RX bytes:1677 (1.6 Kb) TX bytes:1847 (1.8 Kb) > Interrupt:11 Memory:e1bc5000-e1bd5000 > > A minute later: > 10)[root@ntclap4 root]# ifconfig > ath0 Link encap:Ethernet HWaddr 00:20:A6:4C:C1:F3 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:201 errors:4 dropped:0 overruns:0 frame:4 > TX packets:58 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:199 > RX bytes:13910 (13.5 Kb) TX bytes:2638 (2.5 Kb) > Interrupt:11 Memory:e1bc5000-e1bd5000 > > [root@ntclap4 root]# iwlist ath0 ap > ath0 Peers/Access-Points in range: > 00:09:5B:51:46:B2 : Quality:43/94 Signal level:-52 dBm Noise > level:-95 dBm (updated) > > 11) root@localhost root]# dhclient ath0 > Internet Software Consortium DHCP Client V3.0pl2 > Copyright 1995-2001 Internet Software Consortium. > All rights reserved. > For info, please visit http://www.isc.org/products/DHCP > > Listening on LPF/ath0/00:20:a6:4c:c1:f3 > Sending on LPF/ath0/00:20:a6:4c:c1:f3 > Sending on Socket/fallback > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 3 > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 3 > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 4 > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5 > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6 > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 8 > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 14 > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 18 > No DHCPOFFERS received. > No working leases in persistent database - sleeping. > > Seems to be the access poing DHCP server is not responding or possibly > not > getting the DHCPDISCOVER. Why is the Tx-Power off in the iwconfig ath0 > response? > > 12) Here is the contents of ifcfg-ath0 > [root@localhost network-scripts]# cat ifcfg-ath0 > # Please read /usr/share/doc/initscripts-*/sysconfig.txt > # for the documentation of these parameters. > ONBOOT=yes > USERCTL=no > PEERDNS=no > GATEWAY= > TYPE=Wireless > DHCP_HOSTNAME= > IPADDR= > DEVICE=ath0 > HWADDR=00:20:a6:4c:c1:f3 > BOOTPROTO=dhcp > DOMAIN= > NETMASK= > ESSID=NTCOIS1 > CHANNEL=1 > MODE=Managed > RATE=Auto > > Does this look ok? > > 13) Again I believe the access point DHCP server is working fine since > it > works with the Windows XP wireless configuration. > > 14) Why are all of the TX/RX errors occuring? > > >> You'll need to change your default route to get that to work. >> >> Another way to do it would be to disconnect both interfaces, and then >> only reconnect ath0. >> >> That should take care of the gateway stuff for you, assuming you're >> using DHCP on your wireless interface, and that your DHCP server is >> handing out a default gateway. >> >> Otherwise you'll have to do it by hand. >> >> - Terry >> >> >> On Dec 11, 2003, at 10:46 AM, dh...@id... wrote: >> >>> It seems my wireless card is making a connection to the access point >>> based >>> on the results of iwlist. How do I get my applications (browser,etc) >>> to >>> use ath0 rather than my wired eth0 connection? Here is my data. I >>> am >>> not >>> sure if the output of ifconfig is applicable but I included it >>> anyway. >>> >>> [root@ntclap4 root]# ifconfig ath0 192.168.200.44 up >>> [root@ntclap4 root]# iwconfig ath0 essid "NTCOIS1" >>> [root@ntclap4 root]# iwlist ath0 ap >>> ath0 Peers/Access-Points in range: >>> 00:09:5B:51:46:B2 : Quality:43/94 Signal level:-52 dBm Noise >>> level:-95 dBm (updated) >>> >>> [root@ntclap4 root]# iwconfig ath0 >>> ath0 IEEE 802.11 ESSID:"NTCOIS1" >>> Mode:Managed Frequency:5.24GHz Access Point: >>> FF:FF:FF:FF:FF:FF >>> Bit Rate:6Mb/s Tx-Power:off Sensitivity=0/3 >>> Retry:off RTS thr:off Fragment thr:off >>> Encryption key:off >>> Power Management:off >>> Link Quality:0/94 Signal level:-95 dBm Noise level:-95 >>> dBm >>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0 >>> >>> [root@ntclap4 root]# ifconfig atho >>> atho: error fetching interface information: Device not found >>> [root@ntclap4 root]# ifconfig ath0 >>> ath0 Link encap:Ethernet HWaddr 00:20:A6:4C:C1:F3 >>> inet addr:192.168.200.44 Bcast:192.168.200.255 >>> Mask:255.255.255.0 >>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>> RX packets:666 errors:26 dropped:0 overruns:0 frame:26 >>> TX packets:59 errors:1 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:199 >>> RX bytes:32955 (32.1 Kb) TX bytes:2469 (2.4 Kb) >>> Interrupt:11 Memory:e1b91000-e1ba1000 >>> >>> >>> >>>> Dan, >>>> >>>> Use "ifconfig" to bring the interface up: >>>> >>>> "ifconfig ath0 up" should work. >>>> >>>> - Terry >>>> >>>> On Dec 11, 2003, at 5:06 AM, dh...@id... wrote: >>>> >>>>> >>>>> I am very close to getting this to work I think. I am not able to >>>>> make >>>>> the connection to the wireless access point(WAP). Here is some >>>>> data: >>>>> >>>>> [root@ntclap4 root]# iwlist ath0 scan >>>>> ath0 No scan results >>>>> >>>>> [root@ntclap4 root]# iwconfig >>>>> lo no wireless extensions. >>>>> >>>>> eth0 no wireless extensions. >>>>> >>>>> ath0 IEEE 802.11b ESSID:"NTCOIS" >>>>> Mode:Managed Frequency:2.412GHz Access Point: >>>>> FF:FF:FF:FF:FF:FF Bit Rate:0kb/s Tx-Power:off >>>>> Sensitivity=0/3 >>>>> Retry:off RTS thr:off Fragment thr:off >>>>> Encryption key:off >>>>> Power Management:off >>>>> Link Quality:0/94 Signal level:-95 dBm Noise level:-95 >>>>> dBm >>>>> Rx >>>>> invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx >>>>> excessive retries:0 Invalid misc:0 Missed beacon:0 >>>>> >>>>> I have the ESSID set to NTCOIS on the WAP. I have the WAP ESSID >>>>> set >>>>> to >>>>> NTCOIS. I am running my wireless card in 802.11b mode only. >>>>> >>>>> The readme file indicates that I need to "bring the interface up". >>>>> How >>>>> is >>>>> that done? Do you have any suggestions as to things to try? >>>>> >>>>> I am able to connect to the WAP using Windows XP and a Netgear >>>>> card. >>>>> >>>>> Dan >>>>> >>>>> Also getting this message many times in dmesg: >>>>> >>>>> D-Link DE-620 pocket adapter not identified in the printer port >>>>> divert: no divert_blk to free, eth1 not ethernet >>>>> divert: not allocating divert_blk for non-ethernet device eth1 >>>>> -------------------------------------------- >>>>> ath_hal: 0.9.6.3 >>>>> wlan: 0.7.2.0 BETA >>>>> ath_pci: 0.8.4.0 BETA >>>>> ath_pci: cache line size not set; forcing 32 >>>>> divert: allocating divert_blk for ath0 >>>>> ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps >>>>> 54Mbps >>>>> ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps >>>>> ath0: turbo rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps >>>>> 54Mbps >>>>> ath0: 802.11 address: 00:20:a6:4c:c1:f3 >>>>> ath0: Atheros 5211: mem=0x21000000, irq=11 >>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------- >>>>> This SF.net email is sponsored by: IBM Linux Tutorials. >>>>> Become an expert in LINUX or just sharpen your skills. Sign up for >>>>> IBM's >>>>> Free Linux Tutorials. Learn everything from the bash shell to sys >>>>> admin. >>>>> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click >>>>> _______________________________________________ >>>>> Madwifi-users mailing list >>>>> Mad...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/madwifi-users >>>> >>>> >>> >>> >>> ------------------------------------------------------- >>> This SF.net email is sponsored by: IBM Linux Tutorials. >>> Become an expert in LINUX or just sharpen your skills. Sign up for >>> IBM's >>> Free Linux Tutorials. Learn everything from the bash shell to sys >>> admin. >>> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click >>> _______________________________________________ >>> Madwifi-users mailing list >>> Mad...@li... >>> https://lists.sourceforge.net/lists/listinfo/madwifi-users >> >> |
From: <dh...@id...> - 2003-12-12 12:28:44
|
Starting to think that this driver just doesn't work with this card. I did all those things you suggested with no success so I forced the AP IP address. Still no success. I am wondering about transmit power. As can be seen from below Tx-Power:off. Also I get the following which makes me wonder if the driver is controlling the transmitter properly. iwlist ath0 txpower ath0 No transmit-powers ? Please update driver... iwconfig ath0 ap 00:09:5B:51:46:B2 iwconfig ath0 ath0 IEEE 802.11b ESSID:"NTCOIS1" Nickname:"localhost.localdomain" Mode:Managed Frequency:2.427GHz Access Point: 00:09:5B:51:46:B2 Bit Rate:1Mb/s Tx-Power:off Sensitivity=0/3 Retry:off RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0/94 Signal level:-95 dBm Noise level:-95 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > Try doing an ifconfig ath0 up before you set your ESSID, then set the > ESSID, and see if your card is actually associating to the AP > correctly. > > Without an association, you won't be able to pass traffic... and it's > not clear to me with the information below if you are actually > associated after you bring the interface up. > > The iwlist command doesn't show you what you are associated to, it only > shows APs that are in range. Use iwconfig to look at your association. > Check the "Access Point: " area in the iwconfig output. > > If your output is "Access Point: FF:FF:FF:FF:FF:FF" then you are not > associated. > > I usually up the interface before I do anything with iwconfig. This > shouldn't make a difference, but who knows. > > - Terry > > On Dec 11, 2003, at 2:32 PM, dh...@id... wrote: > >> These are the steps I am performing: >> >> 1) ifconfig eth0 down >> 2) ifconfig lo down >> 3) [root@ntclap4 root]# iwconfig >> lo no wireless extensions. >> >> eth0 no wireless extensions. >> >> 4) Push the wireless card into its slot. >> >> 5) [root@ntclap4 root]# iwconfig ath0 >> ath0 IEEE 802.11 ESSID:"" >> Mode:Managed Frequency:2.412GHz Access Point: >> 00:00:00:00:00:00 >> Bit Rate:0kb/s Tx-Power:off Sensitivity=0/3 >> Retry:off RTS thr:off Fragment thr:off >> Encryption key:off >> Power Management:off >> Link Quality:0/94 Signal level:-95 dBm Noise level:-95 dBm >> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >> Tx excessive retries:0 Invalid misc:0 Missed beacon:0 >> >> 6) [root@ntclap4 root]# iwconfig ath0 essid "NTCOIS1" >> >> 7) [root@ntclap4 root]# iwconfig ath0 >> ath0 IEEE 802.11 ESSID:"NTCOIS1" >> Mode:Managed Frequency:5.805GHz Access Point: >> FF:FF:FF:FF:FF:FF >> Bit Rate:6Mb/s Tx-Power:off Sensitivity=0/3 >> Retry:off RTS thr:off Fragment thr:off >> Encryption key:off >> Power Management:off >> Link Quality:0/94 Signal level:-95 dBm Noise level:-95 dBm >> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >> Tx excessive retries:0 Invalid misc:0 Missed beacon:0 >> >> 8) [root@ntclap4 root]# ifconfig ath0 up >> 9) [root@ntclap4 root]# ifconfig >> ath0 Link encap:Ethernet HWaddr 00:20:A6:4C:C1:F3 >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:24 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:41 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:199 >> RX bytes:1677 (1.6 Kb) TX bytes:1847 (1.8 Kb) >> Interrupt:11 Memory:e1bc5000-e1bd5000 >> >> A minute later: >> 10)[root@ntclap4 root]# ifconfig >> ath0 Link encap:Ethernet HWaddr 00:20:A6:4C:C1:F3 >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:201 errors:4 dropped:0 overruns:0 frame:4 >> TX packets:58 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:199 >> RX bytes:13910 (13.5 Kb) TX bytes:2638 (2.5 Kb) >> Interrupt:11 Memory:e1bc5000-e1bd5000 >> >> [root@ntclap4 root]# iwlist ath0 ap >> ath0 Peers/Access-Points in range: >> 00:09:5B:51:46:B2 : Quality:43/94 Signal level:-52 dBm Noise >> level:-95 dBm (updated) >> >> 11) root@localhost root]# dhclient ath0 >> Internet Software Consortium DHCP Client V3.0pl2 >> Copyright 1995-2001 Internet Software Consortium. >> All rights reserved. >> For info, please visit http://www.isc.org/products/DHCP >> >> Listening on LPF/ath0/00:20:a6:4c:c1:f3 >> Sending on LPF/ath0/00:20:a6:4c:c1:f3 >> Sending on Socket/fallback >> DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 3 >> DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 3 >> DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 4 >> DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5 >> DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6 >> DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 8 >> DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 14 >> DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 18 >> No DHCPOFFERS received. >> No working leases in persistent database - sleeping. >> >> Seems to be the access poing DHCP server is not responding or possibly >> not >> getting the DHCPDISCOVER. Why is the Tx-Power off in the iwconfig ath0 >> response? >> >> 12) Here is the contents of ifcfg-ath0 >> [root@localhost network-scripts]# cat ifcfg-ath0 >> # Please read /usr/share/doc/initscripts-*/sysconfig.txt >> # for the documentation of these parameters. >> ONBOOT=yes >> USERCTL=no >> PEERDNS=no >> GATEWAY= >> TYPE=Wireless >> DHCP_HOSTNAME= >> IPADDR= >> DEVICE=ath0 >> HWADDR=00:20:a6:4c:c1:f3 >> BOOTPROTO=dhcp >> DOMAIN= >> NETMASK= >> ESSID=NTCOIS1 >> CHANNEL=1 >> MODE=Managed >> RATE=Auto >> >> Does this look ok? >> >> 13) Again I believe the access point DHCP server is working fine since >> it >> works with the Windows XP wireless configuration. >> >> 14) Why are all of the TX/RX errors occuring? >> >> >>> You'll need to change your default route to get that to work. >>> >>> Another way to do it would be to disconnect both interfaces, and then >>> only reconnect ath0. >>> >>> That should take care of the gateway stuff for you, assuming you're >>> using DHCP on your wireless interface, and that your DHCP server is >>> handing out a default gateway. >>> >>> Otherwise you'll have to do it by hand. >>> >>> - Terry >>> >>> >>> On Dec 11, 2003, at 10:46 AM, dh...@id... wrote: >>> >>>> It seems my wireless card is making a connection to the access point >>>> based >>>> on the results of iwlist. How do I get my applications (browser,etc) >>>> to >>>> use ath0 rather than my wired eth0 connection? Here is my data. I >>>> am >>>> not >>>> sure if the output of ifconfig is applicable but I included it >>>> anyway. >>>> >>>> [root@ntclap4 root]# ifconfig ath0 192.168.200.44 up >>>> [root@ntclap4 root]# iwconfig ath0 essid "NTCOIS1" >>>> [root@ntclap4 root]# iwlist ath0 ap >>>> ath0 Peers/Access-Points in range: >>>> 00:09:5B:51:46:B2 : Quality:43/94 Signal level:-52 dBm Noise >>>> level:-95 dBm (updated) >>>> >>>> [root@ntclap4 root]# iwconfig ath0 >>>> ath0 IEEE 802.11 ESSID:"NTCOIS1" >>>> Mode:Managed Frequency:5.24GHz Access Point: >>>> FF:FF:FF:FF:FF:FF >>>> Bit Rate:6Mb/s Tx-Power:off Sensitivity=0/3 >>>> Retry:off RTS thr:off Fragment thr:off >>>> Encryption key:off >>>> Power Management:off >>>> Link Quality:0/94 Signal level:-95 dBm Noise level:-95 >>>> dBm >>>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >>>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0 >>>> >>>> [root@ntclap4 root]# ifconfig atho >>>> atho: error fetching interface information: Device not found >>>> [root@ntclap4 root]# ifconfig ath0 >>>> ath0 Link encap:Ethernet HWaddr 00:20:A6:4C:C1:F3 >>>> inet addr:192.168.200.44 Bcast:192.168.200.255 >>>> Mask:255.255.255.0 >>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>>> RX packets:666 errors:26 dropped:0 overruns:0 frame:26 >>>> TX packets:59 errors:1 dropped:0 overruns:0 carrier:0 >>>> collisions:0 txqueuelen:199 >>>> RX bytes:32955 (32.1 Kb) TX bytes:2469 (2.4 Kb) >>>> Interrupt:11 Memory:e1b91000-e1ba1000 >>>> >>>> >>>> >>>>> Dan, >>>>> >>>>> Use "ifconfig" to bring the interface up: >>>>> >>>>> "ifconfig ath0 up" should work. >>>>> >>>>> - Terry >>>>> >>>>> On Dec 11, 2003, at 5:06 AM, dh...@id... wrote: >>>>> >>>>>> >>>>>> I am very close to getting this to work I think. I am not able to >>>>>> make >>>>>> the connection to the wireless access point(WAP). Here is some >>>>>> data: >>>>>> >>>>>> [root@ntclap4 root]# iwlist ath0 scan >>>>>> ath0 No scan results >>>>>> >>>>>> [root@ntclap4 root]# iwconfig >>>>>> lo no wireless extensions. >>>>>> >>>>>> eth0 no wireless extensions. >>>>>> >>>>>> ath0 IEEE 802.11b ESSID:"NTCOIS" >>>>>> Mode:Managed Frequency:2.412GHz Access Point: >>>>>> FF:FF:FF:FF:FF:FF Bit Rate:0kb/s Tx-Power:off >>>>>> Sensitivity=0/3 >>>>>> Retry:off RTS thr:off Fragment thr:off >>>>>> Encryption key:off >>>>>> Power Management:off >>>>>> Link Quality:0/94 Signal level:-95 dBm Noise level:-95 >>>>>> dBm >>>>>> Rx >>>>>> invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx >>>>>> excessive retries:0 Invalid misc:0 Missed beacon:0 >>>>>> >>>>>> I have the ESSID set to NTCOIS on the WAP. I have the WAP ESSID >>>>>> set >>>>>> to >>>>>> NTCOIS. I am running my wireless card in 802.11b mode only. >>>>>> >>>>>> The readme file indicates that I need to "bring the interface up". >>>>>> How >>>>>> is >>>>>> that done? Do you have any suggestions as to things to try? >>>>>> >>>>>> I am able to connect to the WAP using Windows XP and a Netgear >>>>>> card. >>>>>> >>>>>> Dan >>>>>> >>>>>> Also getting this message many times in dmesg: >>>>>> >>>>>> D-Link DE-620 pocket adapter not identified in the printer port >>>>>> divert: no divert_blk to free, eth1 not ethernet >>>>>> divert: not allocating divert_blk for non-ethernet device eth1 >>>>>> -------------------------------------------- >>>>>> ath_hal: 0.9.6.3 >>>>>> wlan: 0.7.2.0 BETA >>>>>> ath_pci: 0.8.4.0 BETA >>>>>> ath_pci: cache line size not set; forcing 32 >>>>>> divert: allocating divert_blk for ath0 >>>>>> ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps >>>>>> 54Mbps >>>>>> ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps >>>>>> ath0: turbo rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps >>>>>> 54Mbps >>>>>> ath0: 802.11 address: 00:20:a6:4c:c1:f3 >>>>>> ath0: Atheros 5211: mem=0x21000000, irq=11 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------- >>>>>> This SF.net email is sponsored by: IBM Linux Tutorials. >>>>>> Become an expert in LINUX or just sharpen your skills. Sign up for >>>>>> IBM's >>>>>> Free Linux Tutorials. Learn everything from the bash shell to sys >>>>>> admin. >>>>>> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click >>>>>> _______________________________________________ >>>>>> Madwifi-users mailing list >>>>>> Mad...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/madwifi-users >>>>> >>>>> >>>> >>>> >>>> ------------------------------------------------------- >>>> This SF.net email is sponsored by: IBM Linux Tutorials. >>>> Become an expert in LINUX or just sharpen your skills. Sign up for >>>> IBM's >>>> Free Linux Tutorials. Learn everything from the bash shell to sys >>>> admin. >>>> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click >>>> _______________________________________________ >>>> Madwifi-users mailing list >>>> Mad...@li... >>>> https://lists.sourceforge.net/lists/listinfo/madwifi-users >>> >>> > > |
From: Terry S. <gal...@ma...> - 2003-12-12 18:01:36
|
Ok, you are definitely associated. I'm not sure what the problem might be. Which specific card do you have? - Terry On Dec 12, 2003, at 5:29 AM, dh...@id... wrote: > Starting to think that this driver just doesn't work with this card. I > did all those things you suggested with no success so I forced the AP > IP > address. Still no success. I am wondering about transmit power. As > can > be seen from below Tx-Power:off. Also I get the following which makes > me > wonder if the driver is controlling the transmitter properly. > > iwlist ath0 txpower > ath0 No transmit-powers ? Please update driver... > > iwconfig ath0 ap 00:09:5B:51:46:B2 > iwconfig ath0 > ath0 IEEE 802.11b ESSID:"NTCOIS1" > Nickname:"localhost.localdomain" > Mode:Managed Frequency:2.427GHz Access Point: > 00:09:5B:51:46:B2 > Bit Rate:1Mb/s Tx-Power:off Sensitivity=0/3 > Retry:off RTS thr:off Fragment thr:off > Encryption key:off > Power Management:off > Link Quality:0/94 Signal level:-95 dBm Noise level:-95 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > > >> Try doing an ifconfig ath0 up before you set your ESSID, then set the >> ESSID, and see if your card is actually associating to the AP >> correctly. >> >> Without an association, you won't be able to pass traffic... and it's >> not clear to me with the information below if you are actually >> associated after you bring the interface up. >> >> The iwlist command doesn't show you what you are associated to, it >> only >> shows APs that are in range. Use iwconfig to look at your >> association. >> Check the "Access Point: " area in the iwconfig output. >> >> If your output is "Access Point: FF:FF:FF:FF:FF:FF" then you are not >> associated. >> >> I usually up the interface before I do anything with iwconfig. This >> shouldn't make a difference, but who knows. >> >> - Terry >> >> On Dec 11, 2003, at 2:32 PM, dh...@id... wrote: >> >>> These are the steps I am performing: >>> >>> 1) ifconfig eth0 down >>> 2) ifconfig lo down >>> 3) [root@ntclap4 root]# iwconfig >>> lo no wireless extensions. >>> >>> eth0 no wireless extensions. >>> >>> 4) Push the wireless card into its slot. >>> >>> 5) [root@ntclap4 root]# iwconfig ath0 >>> ath0 IEEE 802.11 ESSID:"" >>> Mode:Managed Frequency:2.412GHz Access Point: >>> 00:00:00:00:00:00 >>> Bit Rate:0kb/s Tx-Power:off Sensitivity=0/3 >>> Retry:off RTS thr:off Fragment thr:off >>> Encryption key:off >>> Power Management:off >>> Link Quality:0/94 Signal level:-95 dBm Noise level:-95 >>> dBm >>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0 >>> >>> 6) [root@ntclap4 root]# iwconfig ath0 essid "NTCOIS1" >>> >>> 7) [root@ntclap4 root]# iwconfig ath0 >>> ath0 IEEE 802.11 ESSID:"NTCOIS1" >>> Mode:Managed Frequency:5.805GHz Access Point: >>> FF:FF:FF:FF:FF:FF >>> Bit Rate:6Mb/s Tx-Power:off Sensitivity=0/3 >>> Retry:off RTS thr:off Fragment thr:off >>> Encryption key:off >>> Power Management:off >>> Link Quality:0/94 Signal level:-95 dBm Noise level:-95 >>> dBm >>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0 >>> >>> 8) [root@ntclap4 root]# ifconfig ath0 up >>> 9) [root@ntclap4 root]# ifconfig >>> ath0 Link encap:Ethernet HWaddr 00:20:A6:4C:C1:F3 >>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>> RX packets:24 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:41 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:199 >>> RX bytes:1677 (1.6 Kb) TX bytes:1847 (1.8 Kb) >>> Interrupt:11 Memory:e1bc5000-e1bd5000 >>> >>> A minute later: >>> 10)[root@ntclap4 root]# ifconfig >>> ath0 Link encap:Ethernet HWaddr 00:20:A6:4C:C1:F3 >>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>> RX packets:201 errors:4 dropped:0 overruns:0 frame:4 >>> TX packets:58 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:199 >>> RX bytes:13910 (13.5 Kb) TX bytes:2638 (2.5 Kb) >>> Interrupt:11 Memory:e1bc5000-e1bd5000 >>> >>> [root@ntclap4 root]# iwlist ath0 ap >>> ath0 Peers/Access-Points in range: >>> 00:09:5B:51:46:B2 : Quality:43/94 Signal level:-52 dBm Noise >>> level:-95 dBm (updated) >>> >>> 11) root@localhost root]# dhclient ath0 >>> Internet Software Consortium DHCP Client V3.0pl2 >>> Copyright 1995-2001 Internet Software Consortium. >>> All rights reserved. >>> For info, please visit http://www.isc.org/products/DHCP >>> >>> Listening on LPF/ath0/00:20:a6:4c:c1:f3 >>> Sending on LPF/ath0/00:20:a6:4c:c1:f3 >>> Sending on Socket/fallback >>> DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 3 >>> DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 3 >>> DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 4 >>> DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5 >>> DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6 >>> DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 8 >>> DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 14 >>> DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 18 >>> No DHCPOFFERS received. >>> No working leases in persistent database - sleeping. >>> >>> Seems to be the access poing DHCP server is not responding or >>> possibly >>> not >>> getting the DHCPDISCOVER. Why is the Tx-Power off in the iwconfig >>> ath0 >>> response? >>> >>> 12) Here is the contents of ifcfg-ath0 >>> [root@localhost network-scripts]# cat ifcfg-ath0 >>> # Please read /usr/share/doc/initscripts-*/sysconfig.txt >>> # for the documentation of these parameters. >>> ONBOOT=yes >>> USERCTL=no >>> PEERDNS=no >>> GATEWAY= >>> TYPE=Wireless >>> DHCP_HOSTNAME= >>> IPADDR= >>> DEVICE=ath0 >>> HWADDR=00:20:a6:4c:c1:f3 >>> BOOTPROTO=dhcp >>> DOMAIN= >>> NETMASK= >>> ESSID=NTCOIS1 >>> CHANNEL=1 >>> MODE=Managed >>> RATE=Auto >>> >>> Does this look ok? >>> >>> 13) Again I believe the access point DHCP server is working fine >>> since >>> it >>> works with the Windows XP wireless configuration. >>> >>> 14) Why are all of the TX/RX errors occuring? >>> >>> >>>> You'll need to change your default route to get that to work. >>>> >>>> Another way to do it would be to disconnect both interfaces, and >>>> then >>>> only reconnect ath0. >>>> >>>> That should take care of the gateway stuff for you, assuming you're >>>> using DHCP on your wireless interface, and that your DHCP server is >>>> handing out a default gateway. >>>> >>>> Otherwise you'll have to do it by hand. >>>> >>>> - Terry >>>> >>>> >>>> On Dec 11, 2003, at 10:46 AM, dh...@id... wrote: >>>> >>>>> It seems my wireless card is making a connection to the access >>>>> point >>>>> based >>>>> on the results of iwlist. How do I get my applications >>>>> (browser,etc) >>>>> to >>>>> use ath0 rather than my wired eth0 connection? Here is my data. I >>>>> am >>>>> not >>>>> sure if the output of ifconfig is applicable but I included it >>>>> anyway. >>>>> >>>>> [root@ntclap4 root]# ifconfig ath0 192.168.200.44 up >>>>> [root@ntclap4 root]# iwconfig ath0 essid "NTCOIS1" >>>>> [root@ntclap4 root]# iwlist ath0 ap >>>>> ath0 Peers/Access-Points in range: >>>>> 00:09:5B:51:46:B2 : Quality:43/94 Signal level:-52 dBm Noise >>>>> level:-95 dBm (updated) >>>>> >>>>> [root@ntclap4 root]# iwconfig ath0 >>>>> ath0 IEEE 802.11 ESSID:"NTCOIS1" >>>>> Mode:Managed Frequency:5.24GHz Access Point: >>>>> FF:FF:FF:FF:FF:FF >>>>> Bit Rate:6Mb/s Tx-Power:off Sensitivity=0/3 >>>>> Retry:off RTS thr:off Fragment thr:off >>>>> Encryption key:off >>>>> Power Management:off >>>>> Link Quality:0/94 Signal level:-95 dBm Noise level:-95 >>>>> dBm >>>>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >>>>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0 >>>>> >>>>> [root@ntclap4 root]# ifconfig atho >>>>> atho: error fetching interface information: Device not found >>>>> [root@ntclap4 root]# ifconfig ath0 >>>>> ath0 Link encap:Ethernet HWaddr 00:20:A6:4C:C1:F3 >>>>> inet addr:192.168.200.44 Bcast:192.168.200.255 >>>>> Mask:255.255.255.0 >>>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>>>> RX packets:666 errors:26 dropped:0 overruns:0 frame:26 >>>>> TX packets:59 errors:1 dropped:0 overruns:0 carrier:0 >>>>> collisions:0 txqueuelen:199 >>>>> RX bytes:32955 (32.1 Kb) TX bytes:2469 (2.4 Kb) >>>>> Interrupt:11 Memory:e1b91000-e1ba1000 >>>>> >>>>> >>>>> >>>>>> Dan, >>>>>> >>>>>> Use "ifconfig" to bring the interface up: >>>>>> >>>>>> "ifconfig ath0 up" should work. >>>>>> >>>>>> - Terry >>>>>> >>>>>> On Dec 11, 2003, at 5:06 AM, dh...@id... wrote: >>>>>> >>>>>>> >>>>>>> I am very close to getting this to work I think. I am not able >>>>>>> to >>>>>>> make >>>>>>> the connection to the wireless access point(WAP). Here is some >>>>>>> data: >>>>>>> >>>>>>> [root@ntclap4 root]# iwlist ath0 scan >>>>>>> ath0 No scan results >>>>>>> >>>>>>> [root@ntclap4 root]# iwconfig >>>>>>> lo no wireless extensions. >>>>>>> >>>>>>> eth0 no wireless extensions. >>>>>>> >>>>>>> ath0 IEEE 802.11b ESSID:"NTCOIS" >>>>>>> Mode:Managed Frequency:2.412GHz Access Point: >>>>>>> FF:FF:FF:FF:FF:FF Bit Rate:0kb/s Tx-Power:off >>>>>>> Sensitivity=0/3 >>>>>>> Retry:off RTS thr:off Fragment thr:off >>>>>>> Encryption key:off >>>>>>> Power Management:off >>>>>>> Link Quality:0/94 Signal level:-95 dBm Noise >>>>>>> level:-95 >>>>>>> dBm >>>>>>> Rx >>>>>>> invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx >>>>>>> excessive retries:0 Invalid misc:0 Missed beacon:0 >>>>>>> >>>>>>> I have the ESSID set to NTCOIS on the WAP. I have the WAP ESSID >>>>>>> set >>>>>>> to >>>>>>> NTCOIS. I am running my wireless card in 802.11b mode only. >>>>>>> >>>>>>> The readme file indicates that I need to "bring the interface >>>>>>> up". >>>>>>> How >>>>>>> is >>>>>>> that done? Do you have any suggestions as to things to try? >>>>>>> >>>>>>> I am able to connect to the WAP using Windows XP and a Netgear >>>>>>> card. >>>>>>> >>>>>>> Dan >>>>>>> >>>>>>> Also getting this message many times in dmesg: >>>>>>> >>>>>>> D-Link DE-620 pocket adapter not identified in the printer port >>>>>>> divert: no divert_blk to free, eth1 not ethernet >>>>>>> divert: not allocating divert_blk for non-ethernet device eth1 >>>>>>> -------------------------------------------- >>>>>>> ath_hal: 0.9.6.3 >>>>>>> wlan: 0.7.2.0 BETA >>>>>>> ath_pci: 0.8.4.0 BETA >>>>>>> ath_pci: cache line size not set; forcing 32 >>>>>>> divert: allocating divert_blk for ath0 >>>>>>> ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps >>>>>>> 54Mbps >>>>>>> ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps >>>>>>> ath0: turbo rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps >>>>>>> 54Mbps >>>>>>> ath0: 802.11 address: 00:20:a6:4c:c1:f3 >>>>>>> ath0: Atheros 5211: mem=0x21000000, irq=11 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------- >>>>>>> This SF.net email is sponsored by: IBM Linux Tutorials. >>>>>>> Become an expert in LINUX or just sharpen your skills. Sign up >>>>>>> for >>>>>>> IBM's >>>>>>> Free Linux Tutorials. Learn everything from the bash shell to >>>>>>> sys >>>>>>> admin. >>>>>>> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click >>>>>>> _______________________________________________ >>>>>>> Madwifi-users mailing list >>>>>>> Mad...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/madwifi-users >>>>>> >>>>>> >>>>> >>>>> >>>>> ------------------------------------------------------- >>>>> This SF.net email is sponsored by: IBM Linux Tutorials. >>>>> Become an expert in LINUX or just sharpen your skills. Sign up for >>>>> IBM's >>>>> Free Linux Tutorials. Learn everything from the bash shell to sys >>>>> admin. >>>>> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click >>>>> _______________________________________________ >>>>> Madwifi-users mailing list >>>>> Mad...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/madwifi-users >>>> >>>> >> >> > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for > IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys > admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Madwifi-users mailing list > Mad...@li... > https://lists.sourceforge.net/lists/listinfo/madwifi-users |
From: Terry S. <gal...@ma...> - 2003-12-12 18:00:30
|
After you bring the card up with "ifconfig up" you should run "iwconfig ath0" again to ensure you are associated. ifconfig doesn't give you any association information, and iwlist ap doesn't tell you if you are associated either, you need to run iwconfig ath0, not iwlist ath0 ap. iwlist ath0 ap simply shows you the APs in your area, not the association, so run iwconfig ath0 again to see if you are really associated. - Terry On Dec 11, 2003, at 2:32 PM, dh...@id... wrote: > These are the steps I am performing: > > 1) ifconfig eth0 down > 2) ifconfig lo down > 3) [root@ntclap4 root]# iwconfig > lo no wireless extensions. > > eth0 no wireless extensions. > > 4) Push the wireless card into its slot. > > 5) [root@ntclap4 root]# iwconfig ath0 > ath0 IEEE 802.11 ESSID:"" > Mode:Managed Frequency:2.412GHz Access Point: > 00:00:00:00:00:00 > Bit Rate:0kb/s Tx-Power:off Sensitivity=0/3 > Retry:off RTS thr:off Fragment thr:off > Encryption key:off > Power Management:off > Link Quality:0/94 Signal level:-95 dBm Noise level:-95 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > 6) [root@ntclap4 root]# iwconfig ath0 essid "NTCOIS1" > > 7) [root@ntclap4 root]# iwconfig ath0 > ath0 IEEE 802.11 ESSID:"NTCOIS1" > Mode:Managed Frequency:5.805GHz Access Point: > FF:FF:FF:FF:FF:FF > Bit Rate:6Mb/s Tx-Power:off Sensitivity=0/3 > Retry:off RTS thr:off Fragment thr:off > Encryption key:off > Power Management:off > Link Quality:0/94 Signal level:-95 dBm Noise level:-95 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > 8) [root@ntclap4 root]# ifconfig ath0 up > 9) [root@ntclap4 root]# ifconfig > ath0 Link encap:Ethernet HWaddr 00:20:A6:4C:C1:F3 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:24 errors:0 dropped:0 overruns:0 frame:0 > TX packets:41 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:199 > RX bytes:1677 (1.6 Kb) TX bytes:1847 (1.8 Kb) > Interrupt:11 Memory:e1bc5000-e1bd5000 > > A minute later: > 10)[root@ntclap4 root]# ifconfig > ath0 Link encap:Ethernet HWaddr 00:20:A6:4C:C1:F3 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:201 errors:4 dropped:0 overruns:0 frame:4 > TX packets:58 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:199 > RX bytes:13910 (13.5 Kb) TX bytes:2638 (2.5 Kb) > Interrupt:11 Memory:e1bc5000-e1bd5000 > > [root@ntclap4 root]# iwlist ath0 ap > ath0 Peers/Access-Points in range: > 00:09:5B:51:46:B2 : Quality:43/94 Signal level:-52 dBm Noise > level:-95 dBm (updated) > > 11) root@localhost root]# dhclient ath0 > Internet Software Consortium DHCP Client V3.0pl2 > Copyright 1995-2001 Internet Software Consortium. > All rights reserved. > For info, please visit http://www.isc.org/products/DHCP > > Listening on LPF/ath0/00:20:a6:4c:c1:f3 > Sending on LPF/ath0/00:20:a6:4c:c1:f3 > Sending on Socket/fallback > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 3 > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 3 > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 4 > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5 > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6 > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 8 > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 14 > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 18 > No DHCPOFFERS received. > No working leases in persistent database - sleeping. > > Seems to be the access poing DHCP server is not responding or possibly > not > getting the DHCPDISCOVER. Why is the Tx-Power off in the iwconfig ath0 > response? > > 12) Here is the contents of ifcfg-ath0 > [root@localhost network-scripts]# cat ifcfg-ath0 > # Please read /usr/share/doc/initscripts-*/sysconfig.txt > # for the documentation of these parameters. > ONBOOT=yes > USERCTL=no > PEERDNS=no > GATEWAY= > TYPE=Wireless > DHCP_HOSTNAME= > IPADDR= > DEVICE=ath0 > HWADDR=00:20:a6:4c:c1:f3 > BOOTPROTO=dhcp > DOMAIN= > NETMASK= > ESSID=NTCOIS1 > CHANNEL=1 > MODE=Managed > RATE=Auto > > Does this look ok? > > 13) Again I believe the access point DHCP server is working fine since > it > works with the Windows XP wireless configuration. > > 14) Why are all of the TX/RX errors occuring? > > >> You'll need to change your default route to get that to work. >> >> Another way to do it would be to disconnect both interfaces, and then >> only reconnect ath0. >> >> That should take care of the gateway stuff for you, assuming you're >> using DHCP on your wireless interface, and that your DHCP server is >> handing out a default gateway. >> >> Otherwise you'll have to do it by hand. >> >> - Terry >> >> >> On Dec 11, 2003, at 10:46 AM, dh...@id... wrote: >> >>> It seems my wireless card is making a connection to the access point >>> based >>> on the results of iwlist. How do I get my applications (browser,etc) >>> to >>> use ath0 rather than my wired eth0 connection? Here is my data. I >>> am >>> not >>> sure if the output of ifconfig is applicable but I included it >>> anyway. >>> >>> [root@ntclap4 root]# ifconfig ath0 192.168.200.44 up >>> [root@ntclap4 root]# iwconfig ath0 essid "NTCOIS1" >>> [root@ntclap4 root]# iwlist ath0 ap >>> ath0 Peers/Access-Points in range: >>> 00:09:5B:51:46:B2 : Quality:43/94 Signal level:-52 dBm Noise >>> level:-95 dBm (updated) >>> >>> [root@ntclap4 root]# iwconfig ath0 >>> ath0 IEEE 802.11 ESSID:"NTCOIS1" >>> Mode:Managed Frequency:5.24GHz Access Point: >>> FF:FF:FF:FF:FF:FF >>> Bit Rate:6Mb/s Tx-Power:off Sensitivity=0/3 >>> Retry:off RTS thr:off Fragment thr:off >>> Encryption key:off >>> Power Management:off >>> Link Quality:0/94 Signal level:-95 dBm Noise level:-95 >>> dBm >>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0 >>> >>> [root@ntclap4 root]# ifconfig atho >>> atho: error fetching interface information: Device not found >>> [root@ntclap4 root]# ifconfig ath0 >>> ath0 Link encap:Ethernet HWaddr 00:20:A6:4C:C1:F3 >>> inet addr:192.168.200.44 Bcast:192.168.200.255 >>> Mask:255.255.255.0 >>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>> RX packets:666 errors:26 dropped:0 overruns:0 frame:26 >>> TX packets:59 errors:1 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:199 >>> RX bytes:32955 (32.1 Kb) TX bytes:2469 (2.4 Kb) >>> Interrupt:11 Memory:e1b91000-e1ba1000 >>> >>> >>> >>>> Dan, >>>> >>>> Use "ifconfig" to bring the interface up: >>>> >>>> "ifconfig ath0 up" should work. >>>> >>>> - Terry >>>> >>>> On Dec 11, 2003, at 5:06 AM, dh...@id... wrote: >>>> >>>>> >>>>> I am very close to getting this to work I think. I am not able to >>>>> make >>>>> the connection to the wireless access point(WAP). Here is some >>>>> data: >>>>> >>>>> [root@ntclap4 root]# iwlist ath0 scan >>>>> ath0 No scan results >>>>> >>>>> [root@ntclap4 root]# iwconfig >>>>> lo no wireless extensions. >>>>> >>>>> eth0 no wireless extensions. >>>>> >>>>> ath0 IEEE 802.11b ESSID:"NTCOIS" >>>>> Mode:Managed Frequency:2.412GHz Access Point: >>>>> FF:FF:FF:FF:FF:FF Bit Rate:0kb/s Tx-Power:off >>>>> Sensitivity=0/3 >>>>> Retry:off RTS thr:off Fragment thr:off >>>>> Encryption key:off >>>>> Power Management:off >>>>> Link Quality:0/94 Signal level:-95 dBm Noise level:-95 >>>>> dBm >>>>> Rx >>>>> invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx >>>>> excessive retries:0 Invalid misc:0 Missed beacon:0 >>>>> >>>>> I have the ESSID set to NTCOIS on the WAP. I have the WAP ESSID >>>>> set >>>>> to >>>>> NTCOIS. I am running my wireless card in 802.11b mode only. >>>>> >>>>> The readme file indicates that I need to "bring the interface up". >>>>> How >>>>> is >>>>> that done? Do you have any suggestions as to things to try? >>>>> >>>>> I am able to connect to the WAP using Windows XP and a Netgear >>>>> card. >>>>> >>>>> Dan >>>>> >>>>> Also getting this message many times in dmesg: >>>>> >>>>> D-Link DE-620 pocket adapter not identified in the printer port >>>>> divert: no divert_blk to free, eth1 not ethernet >>>>> divert: not allocating divert_blk for non-ethernet device eth1 >>>>> -------------------------------------------- >>>>> ath_hal: 0.9.6.3 >>>>> wlan: 0.7.2.0 BETA >>>>> ath_pci: 0.8.4.0 BETA >>>>> ath_pci: cache line size not set; forcing 32 >>>>> divert: allocating divert_blk for ath0 >>>>> ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps >>>>> 54Mbps >>>>> ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps >>>>> ath0: turbo rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps >>>>> 54Mbps >>>>> ath0: 802.11 address: 00:20:a6:4c:c1:f3 >>>>> ath0: Atheros 5211: mem=0x21000000, irq=11 >>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------- >>>>> This SF.net email is sponsored by: IBM Linux Tutorials. >>>>> Become an expert in LINUX or just sharpen your skills. Sign up for >>>>> IBM's >>>>> Free Linux Tutorials. Learn everything from the bash shell to sys >>>>> admin. >>>>> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click >>>>> _______________________________________________ >>>>> Madwifi-users mailing list >>>>> Mad...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/madwifi-users >>>> >>>> >>> >>> >>> ------------------------------------------------------- >>> This SF.net email is sponsored by: IBM Linux Tutorials. >>> Become an expert in LINUX or just sharpen your skills. Sign up for >>> IBM's >>> Free Linux Tutorials. Learn everything from the bash shell to sys >>> admin. >>> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click >>> _______________________________________________ >>> Madwifi-users mailing list >>> Mad...@li... >>> https://lists.sourceforge.net/lists/listinfo/madwifi-users >> >> > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for > IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys > admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Madwifi-users mailing list > Mad...@li... > https://lists.sourceforge.net/lists/listinfo/madwifi-users |
From: Viktor P. <vi...@fi...> - 2003-12-16 13:54:06
|
I've installed the e-builds you've provided to the gentoo ports. The = installation went smooth=C2=B8 and the card is up running nice, it's = listed in both iwconfig and ifconfig (using -a for ifconfig). Since i'm = using 128bit wep, i have to specify them before connecting to the AP (i = think?). So i ran:=20 "iwconfig ath0essid <my ssid> key restricted <my wep-key> rate auto = channel 11 ap <my ap's mac>" and there after: "dhcpcd ath0" | | The NIC's blinking for a while, but whithout much happening, after | a while the card's stops blinking and dhcpcd command ends. But when | i run "ifconfig ath0" the card havn't fetched any IP from the dhcp. | | | I've also checked the AP's logs, and there no tracks after that my | NIC have tried to connect to the it. | | Think you have any clue about this little piece of problem? | | Best regards Viktor Pettersson ----dmesg---- wlan: 0.7.2.0 BETA ath_pci: 0.8.4.0 BETA ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps = 24Mbps 36Mbps 48Mbps 54Mbps ath0: turbo rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ath0: 802.11 address: 00:0d:54:98:99:85 ath0: Atheros 5212: mem=3D0x10400000, irq=3D11 / -----dmesg----- ----ifconfig----- thinkpad madwifi-driver # ifconfig -a ath0 Link encap:Ethernet HWaddr 00:0D:54:98:99:85 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:121 errors:75902 dropped:0 overruns:0 frame:27 TX packets:22 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:199 RX bytes:9438 (9.2 Kb) TX bytes:1092 (1.0 Kb) Interrupt:11 Memory:d0c66000-d0c76000 ......... /----ifconfig---- ----iwconfig----- thinkpad madwifi-driver # iwconfig lo no wireless extensions. eth0 no wireless extensions. ath0 IEEE 802.11 ESSID:"XXXXXX" Mode:Managed Frequency:5.64GHz Access Point: = 00:0D:54:9A:E8:01 Bit Rate:6Mb/s Tx-Power:off Sensitivity=3D0/3 Retry:off RTS thr:off Fragment thr:off Encryption key:XXXXXXXX Security mode:open Power Management:off Link Quality:0/94 Signal level:-95 dBm Noise level:-95 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 /---iwconifig------ ---my iwconfig flags--- "iwconfig ath0 essid <my ssid> key <my wep-key> rate auto channel 11 ap = <my ap's mac>" /---my iwconfig flags--- |
From: SIA \FastNets\ <fa...@fa...> - 2004-01-03 03:21:35
|
Hello !!! I have problem with yours driver for wireless cards in atheros chipsets. My version is madwifi-20030802.gz Problem is: I can't install driver on FreeBSD platfrom FreeBSD test.fastnet.lv 5.1-RELEASE FreeBSD 5.1-RELEASE #0: Thu Jun 5 02:55:42 GMT 2003 ro...@wv...:/usr/obj/usr/src/sys/GENERIC i386 Is this driver only for linux platforms ? if it's adapted for freebsd platforms please send me a manual how install this driver on my FreeBSD platform !!! Big thnx ! -------------------------------------- SIA "FastNets" Adress: Latvija, Riga, Lielvardes 101 Phone: 7598978, 9415465, 9285300 E-mail: fastnet@FastNet.lv Web: www.FastNet.lv Who: Oleg Kantor -------------------------------------- |
From: silas b. <spi...@ho...> - 2004-01-11 06:15:58
|
Hello All, I just recently built a bi-quad antenna based apon Trevor Marshall's design (http://www.trevormarshall.com/biquad.htm). Minus the primestar dish. While doing this I ran across some noteworthy stuff concerning madwifi: 1.) I can official confirm that ad-hoc mode, while it appears to work, does not play nicely with other clients. I consistantly kicked my co-workers ibook off of the ad-hoc network every time I joined it, and If I started the network he could not join it. I know ad-hoc is broken, but I thought this info might be usefull anyway. 2.) I have been using iwlist scanning to get statistics for SNR with and without external antennas attached. I have now come to doubt the statistics I see when running iwlist ath0 scanning. Inside our building, which has 3 foot thick concrete walls (one hell of a 2.4GHz anttenuator), I only see our single AP with or without High Gain Antennas. Outside the building using the built in antenna I don't see any AP's that I don't bring out there with me. I see about 18 different APs outside with the bi-quad attached. Yet once I go back in the building I continue to see the networks that were visable from the outside even when only using the built in Orinoco antenna. The very troubling part is that it is reporting SNR's between 30-50db. I.E. the Noise floor is at -95dbm and the Signal to the ghost AP is -42dbm. Also according to info gathered from iwlist the bi-quad I built is showing as having a gain of about 20db, which sounds way to high for this design which should be about 10-12db of gain. Also the noise floor stays consistantly at -95dbm even with the laptop next to a microwave running on the highest power setting. This just dosn't seem right. 3.) on a good note, a lot of the problems I was personally experiencing with madwifi (such as constantly dropping connections), have gone away with recent CVS updates. WAY TO GO SAM AND GREG. ;0) This driver is getting very useable for me now, if only ad-hoc worked (this mode is indespensable on field tests). Cheers, Silas Bennett =0) _________________________________________________________________ Check out the new MSN 9 Dial-up fast & reliable Internet access with prime features! http://join.msn.com/?pgmarket=en-us&page=dialup/home&ST=1 |
From: Tom M. <to...@ho...> - 2004-01-11 15:10:47
|
> 2.) I have been using iwlist scanning to get statistics for SNR with and= =20 > without external antennas attached. I have now come to doubt the statisti= cs=20 > I see when running iwlist ath0 scanning. Inside our building, which has 3= =20 > foot thick concrete walls (one hell of a 2.4GHz anttenuator), I only see= =20 > our single AP with or without High Gain Antennas. Outside the building=20 > using the built in antenna I don't see any AP's that I don't bring out=20 > there with me. I see about 18 different APs outside with the bi-quad=20 > attached. Yet once I go back in the building I continue to see the networ= ks=20 > that were visable from the outside even when only using the built in=20 > Orinoco antenna. The very troubling part is that it is reporting SNR's=20 > between 30-50db. I.E. the Noise floor is at -95dbm and the Signal to the= =20 > ghost AP is -42dbm. Also according to info gathered from iwlist the bi-qu= ad=20 > I built is showing as having a gain of about 20db, which sounds way to hi= gh=20 > for this design which should be about 10-12db of gain. Also the noise flo= or=20 > stays consistantly at -95dbm even with the laptop next to a microwave=20 > running on the highest power setting. This just dosn't seem right. I've also noticed that the scan results don't seem to reflect AP changes often, or at all, with the current CVS code. In my case, I have an .11g AP that is always on and an .11a AP that comes and goes. Whatever the scan initially finds seems to stay until I reset the results by issuing an iwconfig. I had assumed that once the driver is set to one band (2.4GHz) it stops scanning the other (5GHz). But perhaps it stops scanning at all..? --=20 If you haven't dreamt about conversing with your loved ones in a programming language, you haven't programmed enough. -- seen on slashdot.org |
From: Sam L. <sa...@er...> - 2004-01-11 16:07:35
|
On Sunday 11 January 2004 07:11 am, Tom Marshall wrote: > > 2.) I have been using iwlist scanning to get statistics for SNR with and > > without external antennas attached. I have now come to doubt the > > statistics I see when running iwlist ath0 scanning. Inside our building, > > which has 3 foot thick concrete walls (one hell of a 2.4GHz anttenuator), > > I only see our single AP with or without High Gain Antennas. Outside the > > building using the built in antenna I don't see any AP's that I don't > > bring out there with me. I see about 18 different APs outside with the > > bi-quad attached. Yet once I go back in the building I continue to see > > the networks that were visable from the outside even when only using the > > built in Orinoco antenna. The very troubling part is that it is reporting > > SNR's between 30-50db. I.E. the Noise floor is at -95dbm and the Signal > > to the ghost AP is -42dbm. Also according to info gathered from iwlist > > the bi-quad I built is showing as having a gain of about 20db, which > > sounds way to high for this design which should be about 10-12db of gain. > > Also the noise floor stays consistantly at -95dbm even with the laptop > > next to a microwave running on the highest power setting. This just > > dosn't seem right. > > I've also noticed that the scan results don't seem to reflect AP changes > often, or at all, with the current CVS code. In my case, I have an .11g AP > that is always on and an .11a AP that comes and goes. Whatever the scan > initially finds seems to stay until I reset the results by issuing an > iwconfig. I had assumed that once the driver is set to one band (2.4GHz) > it stops scanning the other (5GHz). But perhaps it stops scanning at > all..? Scanning is only restricted to a band when you lock the mode to one of 11a/b/g using an iwpriv mode operation or otherwise restrict the set of channels to use (doesn't appear there's a wireless extension hooked up to do this yet). Sam |
From: Greg C. <ma...@at...> - 2004-01-11 18:18:34
|
Tom Marshall wrote: >>2.) I have been using iwlist scanning to get statistics for SNR with and >>without external antennas attached. I have now come to doubt the statistics >>I see when running iwlist ath0 scanning. Inside our building, which has 3 >>foot thick concrete walls (one hell of a 2.4GHz anttenuator), I only see >>our single AP with or without High Gain Antennas. Outside the building >>using the built in antenna I don't see any AP's that I don't bring out >>there with me. I see about 18 different APs outside with the bi-quad >>attached. Yet once I go back in the building I continue to see the networks >>that were visable from the outside even when only using the built in >>Orinoco antenna. The very troubling part is that it is reporting SNR's >>between 30-50db. I.E. the Noise floor is at -95dbm and the Signal to the >>ghost AP is -42dbm. Also according to info gathered from iwlist the bi-quad >>I built is showing as having a gain of about 20db, which sounds way to high >>for this design which should be about 10-12db of gain. Also the noise floor >>stays consistantly at -95dbm even with the laptop next to a microwave >>running on the highest power setting. This just dosn't seem right. >> >> > >I've also noticed that the scan results don't seem to reflect AP changes >often, or at all, with the current CVS code. In my case, I have an .11g AP >that is always on and an .11a AP that comes and goes. Whatever the scan >initially finds seems to stay until I reset the results by issuing an >iwconfig. I had assumed that once the driver is set to one band (2.4GHz) it >stops scanning the other (5GHz). But perhaps it stops scanning at all..? > > > the current wlan.o doesn't do background scanning. also, there's no provision for sending preference info into the thing before the device is marked UP. Background scanning is necessary for implementing a good roaming procedure - which we don't have. And that gets complex when WPA is added to the mix and you're trying to handoff a voip call between APs. So, there is lots of work to be done. |
From: Sam L. <sa...@er...> - 2004-01-11 18:57:55
|
On Sunday 11 January 2004 10:17 am, Greg Chesson wrote: > there's no provision for sending preference info into the thing > before the device is marked UP Actually you can set all the preference info you want before starting a scan. The issue is that it is used only when evaluating the results of the scan. I know you want preference info to steer and/or terminate a scan. Sam |
From: Greg C. <ma...@at...> - 2004-01-11 19:12:57
|
Sam Leffler wrote: >On Sunday 11 January 2004 10:17 am, Greg Chesson wrote: > > > >>there's no provision for sending preference info into the thing >>before the device is marked UP >> >> > >Actually you can set all the preference info you want before starting a scan. >The issue is that it is used only when evaluating the results of the scan. I >know you want preference info to steer and/or terminate a scan. > > Sam > > > That's certainly true, but I think there's even more to the story if we want to have self-selecting profiles. In that mode you would want the device to come up and scan and then select security profiles and other things (printers, fixed IP addresses or dhcp, automounter, etc) after listening for APs. Totally a client-user thing and different from what's needed for APs. It's possible to do that with the current driver, although a more efficient implementation would be to first restrict scanning to channels found in a preference list and then launching a full-up scan only if the constrained scan failed. The driver default should be a full scan unless its given a constrained scan directive. |
From: Sam L. <sa...@er...> - 2004-01-11 20:12:25
|
On Sunday 11 January 2004 11:11 am, Greg Chesson wrote: > Sam Leffler wrote: > >On Sunday 11 January 2004 10:17 am, Greg Chesson wrote: > >>there's no provision for sending preference info into the thing > >>before the device is marked UP > > > >Actually you can set all the preference info you want before starting a > > scan. The issue is that it is used only when evaluating the results of > > the scan. I know you want preference info to steer and/or terminate a > > scan. > > > > Sam > > That's certainly true, but I think there's even more to the story if we > want to have self-selecting profiles. > In that mode you would want the device to come up and scan and then > select security profiles > and other things (printers, fixed IP addresses or dhcp, automounter, > etc) after listening for APs. > Totally a client-user thing and different from what's needed for APs. > It's possible to do that > with the current driver, although a more efficient implementation would > be to first restrict > scanning to channels found in a preference list and then launching a > full-up scan only > if the constrained scan failed. The driver default should be a full > scan unless its given > a constrained scan directive. Except for a few small pieces missing you can do all this now. If you set the channel list and related info then you'll constrain the scan to only those frequences. Then the user app can select the AP from the scan result set and fix the bssid. If nothing shows in the constrained scan then the user app can unconstrain the channel list to expand the scan. The missing bits in this scenario are to dispatch wireless events so the user app doesn't have to block waiting for scan results and to not scan again when told to set the bssid if that AP is already in the cached scan list (assuming the list is recent enough--which we can't tell because we don't timestamp things). However I'm not aware of any user app that does something like this right now. There's also the tie-in to a GUI. The dhclient app could be taught to do some of this but it's not clear it's the right place for this. I vaguely recall some KDE app that I might be close to this. If there's a GNOME app I wouldn't know as I'm a KDE user. Sam |
From: Chris D. <una...@in...> - 2004-02-08 12:10:43
|
unsubscribe hello123 una...@in... |
From: Bob H. <bo...@88...> - 2004-03-13 01:48:09
|
Aloha, Does anyone have experience/information on using atheros first generation radios .11a for long links greater than .5 mile? Thanks for all the great work on madwifi. bob |
From: Elizabeth P. <li...@un...> - 2004-12-26 00:48:35
|
Greetings :) I have a Toshiba Satellite 340 and the wireless card refuses to work :( I put in an external Netgear temporarily and that works fine its just ath0 that just doesnt walk. Btw: the netgear is seen as ath1 :) It sees it.. Dhclient doesnt work. I cant attach to any wifi networks its the darndest thing. Im running Debian ( testing) and the 2.6.9 kernel. Its a Toshiba 340 (bestBuy) ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ath0: mac 5.9 phy 4.3 radio 4.6 ath0: 802.11 address: 00:11:f5:15:5c:5e ath0: Use hw queue 0 for WME_AC_BE traffic ath0: Use hw queue 1 for WME_AC_BK traffic ath0: Use hw queue 2 for WME_AC_VI traffic ath0: Use hw queue 3 for WME_AC_VO traffic ath0: Atheros 5212: mem=0xe0200000, irq=11 ath0: no IPv6 routers present If you can help id sure appreciate it :) Liz -- Elizabeth Palomino <li...@un...> |
From: Michael R. <ma...@no...> - 2004-12-26 18:28:01
|
Hi. Elizabeth Palomino wrote: > It sees it.. Dhclient doesnt work. What version of dhclient are you using (that's the ISC thingy, right?)? And what CVS snapshot of madwifi are you using? There have been several reports about DHCP not working during the last weeks (and others who reported success with DHCP). Bye, Mike |
From: Jason L. <hub...@ne...> - 2005-01-10 00:33:35
|
I have a Netgear WG311T card running on FC2. It has been running fine for 3 months or so, but today just stopped working. I recreated the ifcfg-ath0 file and can now get it to start after boot with via ifup ath0. The problem is when I boot up it does not load, but it loads fine with ifup ath0 after bootup. Here is my ifcfg-ath0: DEVICE=ath0 ONBOOT=yes #BOOTPROTO=dhcp HWADDR=00:09:5B:E8:6E:AF IPADDR=192.168.1.21 NETMASK=255.255.255.0 NETWORK=192.168.1.0 TYPE=Wireless WIRELESS=yes #Wireless Config MODE=Managed ESSID=XXX KEY=XXX Any suggestions? Thanks! |