[Click] Madwifi+Click Problems

[Nels Anderson]

Aloha,

As a follow-up to the problem I'm having getting the madwifi.stripped driver to
act as an access point, here's the output from the click config itself:

Aug 31 13:48:37 dhcp147 kernel: chatter: ath0: 37 | NODS mgt probe_req
00:04:e2:80:45:42 ->  ff:ff:ff:ff:ff:ff (ff:ff:ff:ff:ff:ff) 4 Mbps +74/0
Aug 31 13:48:37 dhcp147 kernel: chatter: pr :: ProbeResponder: ProbeReq:
00:04:e2:80:45:42 ssid athyo rates { * 2 * 4 11 22 }
Aug 31 13:48:37 dhcp147 kernel: chatter: probe_responce:   58 | 50000000
0004e280 4542000d 888a78e3 000d888a 78e30000
Aug 31 13:48:37 dhcp147 kernel: chatter: ath0: 37 | NODS mgt probe_req
00:04:e2:80:45:42 ->  ff:ff:ff:ff:ff:ff (ff:ff:ff:ff:ff:ff) 4 Mbps +73/0
Aug 31 13:48:37 dhcp147 kernel: chatter: pr :: ProbeResponder: ProbeReq:
00:04:e2:80:45:42 ssid athyo rates { * 2 * 4 11 22 }
Aug 31 13:48:37 dhcp147 kernel: chatter: probe_responce:   58 | 50000000
0004e280 4542000d 888a78e3 000d888a 78e30000
Aug 31 13:48:37 dhcp147 kernel: chatter: ath0: 37 | NODS mgt probe_req
00:04:e2:80:45:42 ->  ff:ff:ff:ff:ff:ff (ff:ff:ff:ff:ff:ff) 4 Mbps +72/0
Aug 31 13:48:37 dhcp147 kernel: chatter: pr :: ProbeResponder: ProbeReq:
00:04:e2:80:45:42 ssid athyo rates { * 2 * 4 11 22 }
Aug 31 13:48:37 dhcp147 kernel: chatter: probe_responce:   58 | 50000000
0004e280 4542000d 888a78e3 000d888a 78e30000
Aug 31 13:48:37 dhcp147 kernel: chatter: ath0: 30 | NODS mgt auth
00:04:e2:80:45:42 ->  00:0d:88:8a:78:e3 (00:0d:88:8a:78:e3) 4 Mbps +73/0
Aug 31 13:48:37 dhcp147 kernel: chatter: auth:   30 | b0000201 000d888a 78e30004
e2804542 000d888a 78e3d0c3
Aug 31 13:48:38 dhcp147 kernel: chatter: ath0: 37 | NODS mgt probe_req
00:04:e2:80:45:42 ->  ff:ff:ff:ff:ff:ff (ff:ff:ff:ff:ff:ff) 4 Mbps +79/0
Aug 31 13:48:38 dhcp147 kernel: chatter: pr :: ProbeResponder: ProbeReq:
00:04:e2:80:45:42 ssid athyo rates { * 2 * 4 11 22 }
Aug 31 13:48:38 dhcp147 kernel: chatter: probe_responce:   58 | 50000000
0004e280 4542000d 888a78e3 000d888a 78e30000
Aug 31 13:48:38 dhcp147 kernel: chatter: ath0: 37 | NODS mgt probe_req
00:04:e2:80:45:42 ->  ff:ff:ff:ff:ff:ff (ff:ff:ff:ff:ff:ff) 4 Mbps +76/0
Aug 31 13:48:38 dhcp147 kernel: chatter: pr :: ProbeResponder: ProbeReq:
00:04:e2:80:45:42 ssid athyo rates { * 2 * 4 11 22 }
Aug 31 13:48:38 dhcp147 kernel: chatter: probe_responce:   58 | 50000000
0004e280 4542000d 888a78e3 000d888a 78e30000
Aug 31 13:48:39 dhcp147 dhclient: DHCPREQUEST on click to 128.138.129.136 port
67
Aug 31 13:48:39 dhcp147 kernel: chatter: ath0: 37 | NODS mgt probe_req
00:04:e2:80:45:42 ->  ff:ff:ff:ff:ff:ff (ff:ff:ff:ff:ff:ff) 4 Mbps +76/0
Aug 31 13:48:39 dhcp147 kernel: chatter: pr :: ProbeResponder: ProbeReq:
00:04:e2:80:45:42 ssid athyo rates { * 2 * 4 11 22 }
Aug 31 13:48:39 dhcp147 kernel: chatter: probe_responce:   58 | 50000000
0004e280 4542000d 888a78e3 000d888a 78e30000
Aug 31 13:48:39 dhcp147 kernel: chatter: ath0: 30 | NODS mgt auth
00:04:e2:80:45:42 ->  00:0d:88:8a:78:e3 (00:0d:88:8a:78:e3) 4 Mbps +78/0
Aug 31 13:48:39 dhcp147 kernel: chatter: auth:   30 | b0000201 000d888a 78e30004
e2804542 000d888a 78e390c4
<repeats...>

On the other side, I tried associating with two different clients, using two
completely seperate cards, and they just fail with:

Jul 20 13:23:46 localhost kernel: wlan0: LinkStatus: BSSID=44:44:44:44:44:44
Jul 20 13:23:48 localhost kernel: wlan0: LinkStatus=6 (Association failed)
Jul 20 13:23:48 localhost kernel: wlan0: LinkStatus: BSSID=44:44:44:44:44:44
Jul 20 13:23:50 localhost kernel: wlan0: LinkStatus=6 (Association failed)
Jul 20 13:23:50 localhost kernel: wlan0: LinkStatus: BSSID=44:44:44:44:44:44
<repeats...>

Does this shed any light on the problem?  Just looking at the click config
output, everything seems to be fine, but it's clearly not actually associating.
 Once again, thanks for the assistance.

-Nels

Quoting John Bicket <jbicket at amsterdam.lcs.mit.edu>:

> Hi Nels,
>
> This is because the madwifi.stripped driver report ath0 with a device
> type of ARPHRD_IEEE80211, and ifconfig doesn't know how to print mac
> addresses for that.  (I sent a patch to the net-tools guy, but I think
> he just ignored me).
>
> Everything else should work normally, and the address is just the first
> 6 bytes of the hwaddr in ifconfig.  (ie 00-0D-88-8A-78-E3).
> I'm not sure the stripped driver supports changing mac addresses.
>
> Let me know if this answers your question. I'm also at sigcomm now, so
> look me up if you're here.
>
>
> --john
>
>
> Nels Anderson [Nels.Anderson at colorado.edu] wrote:
> >Aloha,
> >
> >Hello again, I'm still experiencing some problems with wifi-enable click and
> the
> >stripped madwifi driver for the atheros cardset.  After building the latest
> >driver and loading all the modules, ath0 comes up with the bizarre ethernet
> >address of:
> >
> >ath0   Link encap:UNSPEC  HWaddr
> 00-0D-88-8A-78-E3-00-00-00-00-00-00-00-00-00-00
> >
> >Also when I try and change the MAC address of the card with 'ifconfig ath0
> hw
> >ether $mac' (with a proper address for $mac), it also fails with this
> message:
> >
> >SIOCSIFHWADDR: Invalid argument
> >
> >Anyone have any idea what might be causing these problems?
> >
> >This doesn't happen when I build and load the non-click sourceforge madwifi
> >drivers.  I actually had both of these things working normally under that
> >driver.  Now, I'm not sure if it's the stripped driver itself (I don't think
> it
> >is) or if it's some combination of kernel options and the stripped driver.
> >Something the stripped madwifi uses but the sourceforge one does not.  Does
> >anyone have a 2.4.26 kernel config that they've been able to get the
> click-wifi
> >stuff working with?  I'm just using a stock kernel.org 2.4.26 kernel.
> >
> >If anyone has any ideas, ran across similiar problems or anything else,
> >assistance would be much appreciated.  Thanks,
> >
> >-Nels
> >_______________________________________________
> >click mailing list
> >click at amsterdam.lcs.mit.edu
> >https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>