From: David S. <da...@ne...> - 2006-10-31 06:22:39
|
hi there, okay, I gave up on wifi autodetection since it would not work reliably. But even if I manually configure the wifi on campus, the driver sometimes fails to associate or claims association with an ap with quite good link quality but then claims not to get dhcp-responses. I am frustrated. Is there anyone who knows if the macbook atheros chip works with ndiswrapper (and where to get the particular windows drivers?) thanks for your help, I need networking on campus and this starts to be annoying. Especially because I don't know how to debug the ath0 interface. bye, david |
From: Brian C <brianwc@OCF.Berkeley.EDU> - 2006-10-31 07:20:28
|
David Spreen wrote: > hi there, > okay, I gave up on wifi autodetection since it would not work reliably. > But even if I manually configure the wifi on campus, the driver > sometimes fails to associate or claims association with an ap with quite > good link quality but then claims not to get dhcp-responses. I am > frustrated. I have no trouble with the madwifi drivers on my macbook. To get automatic association at work/home or school/home I slightly modified the instructions at: http://tips.linux.com/article.pl?sid=06/07/03/1744235&tid=100&tid=13 which will require installing hotplug, guessnet, ifplugd, and arping. Suppose your home network assigns you IPs in 192.168.0.x and your school network assigns them in 192.168.1.x, each with routers at 192.168.x.1. Then use arping to figure out the MAC address of the routers you connect to and put them in place of the XX:XX and YY:YY that I show below. Edit /etc/network/interfaces as follows: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo ath0 iface lo inet loopback # This is a list of hotpluggable network interfaces. # They will be activated automatically by the hotplug subsystem. mapping eth0 script grep map eth0 # The primary network interface allow-hotplug eth0 ath0 iface eth0 inet dhcp # The Atheros Wireless Interface mapping ath0 script /usr/sbin/guessnet-ifupdown map default: roam map verbose: true iface home inet dhcp wireless_essid HOME_ESSID pre-up modprobe ath_pci pre-up ifconfig ath0 up post-up iwconfig ath0 essid HOME_ESSID test1 wireless mac 00:XX:XX:XX:XX:XX essid HOME_ESSID test2 peer address 192.168.0.1 mac 00:XX:XX:XX:XX:XX iface borg inet dhcp wireless_essid SCHOOL_ESSID pre-up modprobe ath_pci pre-up ifconfig ath0 up post-up iwconfig ath0 essid SCHOOL_ESSID test1 wireless mac 00:YY:YY:YY:YY:YY essid SCHOOL_ESSID test2 peer address 192.168.1.1 mac 00:YY:YY:YY:YY:YY iface roam inet dhcp wireless_essid any pre-up modprobe ath_pci pre-up ifconfig ath0 up |
From: David S. <da...@ne...> - 2006-10-31 23:08:22
|
Hi Brian, thanks for your help. This is all very well but as I wrote, if I don't bring up the interface at all at boot time and I just have a shellscript like this: iwconfig ath0 essid SCHOOLSSID ifconfig ath0 up dhcpcd ath0 the interface will not associate with any access point. iwconfig ap macaddress won't work either. bye, david |
From: Brian C <brianwc@OCF.Berkeley.EDU> - 2006-11-01 03:03:37
|
David Spreen wrote: > Hi Brian, > thanks for your help. This is all very well but as I wrote, if I don't > bring up the interface at all at boot time and I just have a shellscript > like this: > > iwconfig ath0 essid SCHOOLSSID > ifconfig ath0 up > dhcpcd ath0 > > the interface will not associate with any access point. iwconfig ap > macaddress won't work either. That's weird. I suppose it works fine under OS X and/or Windows, otherwise you'd suspect a hardware problem. That makes me think your version of madwifi and/or your kernel version are not playing nice either in isolation or together. Did you do something like the following when installing madwifi? Add the following to /etc/apt/sources.list # Testing deb http://ftp.au.debian.org/debian testing main contrib non-free deb-src http://ftp.au.debian.org/debian testing main contrib non-free After adding the sources above to sources.list do apt-get update Then, apt-get install madwifi-source madwifi-tools module-assistant Finally, m-a prepare m-a a-i madwifi depmod -a modprobe ath_pci See http://madwifi.org/wiki/UserDocs/Distro/Debian/MadWifi for more details. |
From: Ludovic R. <lud...@gm...> - 2006-11-01 12:10:59
|
On 01/11/06, Brian C <br...@oc...> wrote: > David Spreen wrote: > > the interface will not associate with any access point. iwconfig ap > > macaddress won't work either. I also have a similar problem. Some times (say 50%) the interface associates to the access point (I can see the AP Mac address in iwconfig) but the DHCP negotiation does not work. But maybe the association do not work at all. > That's weird. I suppose it works fine under OS X and/or Windows, > otherwise you'd suspect a hardware problem. That makes me think your > version of madwifi and/or your kernel version are not playing nice > either in isolation or together. > > Did you do something like the following when installing madwifi? I am using madwifi-source 1:0.9.2+r1710.20060914-1 from Debian testing and madwifi-tools 1:0.9.2+dfsg-1 also from Debian testing. In general I can make the network card work correctly by removing and reinstalling the madwifi kernel module # rmmod ath_pci # modprobe ath_pci but it does not always works. Of course I do not have this problem under Mac OS X. It looks like the bug is already known as Debian bug #394606 "madwifi-source: Driver frequently loses association or cannot associate" and is already correct in upstream subversion revision r1755. I hope to see a Debian package correcting the bug soon. bye, -- Dr. Ludovic Rousseau |