Hello, Currently I'm testing a recent kernel from the mainline tree (head at 20b0f65d35ae45d43f363ace3744a775a752d265). Good news is that the bcm43xx driver works on nx6325 . And works quite well. Though I tested it in managed mode only. Wpa_supplicant was able to negotiate with an AP using WPA-PSK, WPA2-PSK as well as no data encryption. I haven't noticed any data-link errors nor transfer limits so far (non-local access beyond 180kB/s). However, I had to set everything related to network layer manually, because all dhcp transactions ended up more less like that:
Listening on LPF/eth1/00:14:a5:eb:d4:32 Sending on LPF/eth1/00:14:a5:eb:d4:32 Sending on Socket/fallback DHCPREQUEST on eth1 to 255.255.255.255 port 67 ip length 272 disagrees with bytes received 534. accepting packet with data after udp payload. DHCPNAK from 192.168.1.1 DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4 receive_packet failed on eth1: Network is down DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11 DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 16 Before I start bashing netgear who sells crappy wpn824's, I would like to rule out possibility that it's a bcm43xx fault. Anyway something went wrong in the module. -- at _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
