On Wednesday 11 January 2006 23:36, Jeroen Cranendonk wrote:
> Several things in this mail really :)
>
> - Firstly, I love the driver, keep up the good work, it's appreciated!! :)
>
> - Secondly, after my DS (the nintendo thing, only wifi device to test
> with atm. ;) ) disconnects I see this in the kernel log:
> ( LOG moved to end of mail, for readability :) )
>
> Should I worry about this (it complains about overheating?), or is this
> all normal ?:)
>
> - Thirdly, I've been messing with the nintendo ds protocol nicknamed
> nifi, there's a libnifi thing in very early stages of development which
> connects to it and allows you to download demo roms/games. On windows
> there's only one card supporting it, but I think on linux (without the
> ndis horror) more might do so. I've actually had succes sending
> something to the ds using the libnifi thing over it, and got all excited
> :) But this is only the initial banner/logo for a rom/game, after that
> the connection fails.
> Since this all works in monitor mode (set via iwpriv), I've also been
> testing with kismet a bit, which uses the same monitor mode.
> All that seems to give is lots of 'noise' packets, and I'm wondering if
> that is why the libnifi thing won't work either, does anyone know
> anything about that ? :) If this would support nifi, lots of people 'll
> get even more excited about the driver ;)
>
> - Fourdly, how much hope is there for TI ever giving specs? ;) It's been
> a few years since they released the chip isn't it? linux has gotten a
> lot more popular since ? :) (I know.. but I like to dream ^_^ )
>
> - Finally, I've got the latest 2006something running on my box, is there
> anything I could give in the way of logs, eeprom dumps, things I could
> try/test (no pc clients to connect to though, just the ds :/ ) that
> might help development ? :)
>
> Cheers!
> Jeroen
>
> -LOG:-
> Jan 11 22:26:53 dolphinblue kernel: AUTHEN priv->addr=00:50:18:2B:6B:06
> a1=00:50:18:2B:6B:06 a2=00:09:BF:AF:A6:36 a3=00:50:18:2B:6B:06
> priv->bssid=00:50:18:2B:6B:06
> Jan 11 22:26:53 dolphinblue kernel: algorithm is ok
> Jan 11 22:26:53 dolphinblue kernel: acx_process_authen auth seq step 1
> Jan 11 22:26:53 dolphinblue kernel: transmit_auth2: BSSID=00:50:18:2B:6B:06
> Jan 11 22:26:54 dolphinblue dhcpd: DHCPDISCOVER from 00:09:bf:af:a6:36
> via wlan0
> Jan 11 22:26:54 dolphinblue dhcpd: DHCPOFFER on 192.168.1.5 to
> 00:09:bf:af:a6:36 via wlan0
> Jan 11 22:26:54 dolphinblue dhcpd: DHCPREQUEST for 192.168.1.5
> (192.168.1.1) from 00:09:bf:af:a6:36 via wlan0
> Jan 11 22:26:54 dolphinblue dhcpd: DHCPACK on 192.168.1.5 to
> 00:09:bf:af:a6:36 via wlan0
> Jan 11 22:26:57 dolphinblue dhcpd: DHCPRELEASE of 192.168.1.5 from
> 00:09:bf:af:a6:36 via wlan0 (not found)
> Jan 11 22:26:57 dolphinblue kernel: DEAUTHEN
> priv->addr=00:50:18:2B:6B:06 a100:50:18:2B:6B:06 a200:09:BF:AF:A6:36
> a300:50:18:2B:6B:06 priv->bssid00:50:18:2B:6B:06
You got a deauth packet from STA 00:09:BF:AF:A6:36.
/me fixing a message, it looks mangled.
if (acx_debug & L_ASSOC) {
acx_print_mac("got deauth from sta:", hdr->a2, " ");
acx_print_mac("a1:", hdr->a1, " ");
acx_print_mac("a3:", hdr->a3, " ");
acx_print_mac("priv->addr:", priv->dev_addr, " ");
acx_print_mac("priv->bssid:", priv->bssid, "\n");
}
This will look better.
--
vda
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
