Hi! I have a Nov. 2002 ibook running a 2.4.21-pre3-ben0 kernel. I'm very happy that support for the new hardware has come appeared so quickly. There is only one unsolved problem I have with my ibook, which is that the airport card isn't communicating properly with some access points.
My ibook associates fine with the AP; the AP can receive packets from the ibook. But the ibook can receive no packets from the AP, with the exception of arp who-has requests from other machines on the network. Here is an example of the ibook (10.0.0.12) trying to ping the AP (10.0.0.1): -- seen through the eyes of the AP tcpdump: listening on wi0 23:28:12.529118 arp who-has 10.0.0.1 tell 10.0.0.12 23:28:12.529275 arp who-has 10.0.0.1 tell 10.0.0.12 23:28:12.529593 arp reply 10.0.0.1 is-at 0:4:e2:57:80:f6 23:28:13.525091 arp who-has 10.0.0.1 tell 10.0.0.12 23:28:13.525253 arp who-has 10.0.0.1 tell 10.0.0.12 23:28:13.525429 arp reply 10.0.0.1 is-at 0:4:e2:57:80:f6 23:28:14.525087 arp who-has 10.0.0.1 tell 10.0.0.12 23:28:14.525249 arp who-has 10.0.0.1 tell 10.0.0.12 23:28:14.525421 arp reply 10.0.0.1 is-at 0:4:e2:57:80:f6 -- seen through the eyes of the ibook tcpdump: listening on eth1 23:28:13.884345 arp who-has 10.0.0.1 tell 10.0.0.12 23:28:14.880021 arp who-has 10.0.0.1 tell 10.0.0.12 23:28:15.880020 arp who-has 10.0.0.1 tell 10.0.0.12 My housemate was listening with her ibook running OS X (which works fine with the AP) and confirmed the AP's version of events --- the ibook sends out two arps in quick succession, thinking it's only sending one, and doesn't see the reply. And here's another machine on the network trying to ping the ibook; the ibook sees and responds to the arp, but it doesn't see the pings: -- tcpdump on the AP says: 00:05:18.584524 arp who-has 10.0.0.12 tell 10.0.0.9 00:05:18.679824 arp reply 10.0.0.12 is-at 0:30:65:7:fa:34 00:05:18.680120 10.0.0.9 > 10.0.0.12: icmp: echo request (DF) -- tcpdump on the ibook says: 00:05:20.162634 arp who-has 10.0.0.12 tell 10.0.0.9 00:05:20.162725 arp reply 10.0.0.12 is-at 0:30:65:7:fa:34 ... and then silence. Has anyone else run into this problem? If not, I'm not afraid of getting my hands dirty from a little debugging, but maybe I can save myself some headaches by asking beforehand. If anyone is interested, here is what the hermes, orinoco and airport modules say when they're loaded: Jan 25 21:15:51 queensboro-bridge kernel: hermes.c: 5 Apr 2002 David Gibson <[EMAIL PROTECTED]> Jan 25 21:16:10 queensboro-bridge kernel: orinoco.c 0.11b (David Gibson <[EMAIL PROTECTED]> and others) Jan 25 21:16:15 queensboro-bridge kernel: airport.c 0.11b (Benjamin Herrenschmidt <[EMAIL PROTECTED]>) Jan 25 21:16:16 queensboro-bridge kernel: eth1: Station identity 001f:0001:0004:0010 Jan 25 21:16:16 queensboro-bridge kernel: eth1: Looks like a Lucent/Agere firmware version 4.16 Jan 25 21:16:16 queensboro-bridge kernel: eth1: Ad-hoc demo mode supported Jan 25 21:16:16 queensboro-bridge kernel: eth1: MAC address 00:30:65:07:FA:34 Jan 25 21:16:16 queensboro-bridge kernel: eth1: Station name "HERMES I" Jan 25 21:16:16 queensboro-bridge kernel: eth1: ready Jan 25 21:16:16 queensboro-bridge kernel: airport: card registered for interface eth1 The machine is Linux queensboro-bridge 2.4.21-pre3-ben0 #11 Thu Jan 23 22:18:40 PST 2003 ppc unknown, compiled with a .config like the one http://web.mit.edu/jmuelmen/www/.config Any suggestions are welcome. Cheers, Johannes
