So far I have had my ATV (Broadcom 4328 rev 01) working fine using Wireless G using a WPA-PSK.
Since I have upgraded my router to a NetGear WNR3500L I wanted my ATVs to connect over N instead of G. I am having zero luck unfortunately. So I am wondering if anyone else has it working. First off, I following the instructions on this page using the ndiswrapper: http://code.google.com/p/atv-bootloader/wiki/InstallWireless Basically this stuff: <code> Download and extract a Windows based Broadcom driver. mkdir R140746 wget http://ftp.us.dell.com/network/R140746.EXE unzip -d R140746 R140746.EXE # # this will extract the required bits from the Windows driver sudo ndiswrapper -i R140746/DRIVER/bcmwl5.inf Load the ndiswrapper kernel module and check dmesg. sudo modprobe -v ndiswrapper dmesg You should see something like this. ndiswrapper version 1.52 loaded (smp=yes, preempt=yes) ndiswrapper: driver bcmwl5 (Broadcom,10/12/2006, 4.100.15.5) loaded PCI: Enabling device 0000:02:00.0 (0000 -> 0002) ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16 PCI: Setting latency timer of device 0000:02:00.0 to 64 ndiswrapper: using IRQ 16 wlan0: ethernet device 00:19:e3:dc:14:88 using NDIS driver: bcmwl5, version: 0x4640f05, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 14E4:4328.5.conf wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK usbcore: registered new interface driver ndiswrapper </code> I have tried a number of things, but it basically boils down to this. If my router is setup for both N and G connections it will not work. The wireless will _not_ connect at all. If I change the router to only accept G (TKIP) connections it works flawlessly. My router has a number of options, G only (TKIP WPA-PSK), N only (AES, WPA2-PSK), or G and N with both options. Here is my working /etc/network/interfaces file: <code> auto lo iface lo inet loopback iface eth0 inet dhcp iface wlan0 inet dhcp pre-up sleep 10 wpa-driver wext #wpa-conf master wpa-ssid JackSprat2010 wpa-ap-scan 1 #wpa-scan-ssid 1 wpa-proto RSN WPA wpa-pairwise CCMP TKIP wpa-group CCMP TKIP wpa-key-mgmt WPA-PSK #wpa-psk 1901c146206bd9ed17018669377cbd9c1ac44dee5a54a28f9530144e27c255ac wpa-psk password_in_clear_text auto wlan0 auto eth0 </code> With the above configuration, it will attempt WPA2-PSK first (AES, RSN, CCMP), and fail back to WPA-PSK (WPA, TKIP). That is controlled via these options: <code>wpa-proto RSN WPA</code> One thing I question was how to properly convert the wpa-psk into a hex value and if it differs when using WPA-PSK and WPA2-PSK. This is why I have tried with it in clear text as well. So for TKIP, using clear text or the hex value, I can connect. The hex value was originally generated using the GUI tool under System -> Network with my Mythbuntu install (8.04). Here is the output I get when attempting to connect to my N router: <code> Listening on LPF/eth0/00:17:f2:fc:18:c5 Sending on LPF/eth0/00:17:f2:fc:18:c5 Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13 No DHCPOFFERS received. No working leases in persistent database - sleeping. </code> dmesg, var/log/messages do not show anything worth while. The router log does not even register the attempts. So, if anyone has any suggestions, I would be grateful. Dave -- To post to this group, send email to atv-bootloader@googlegroups.com For more options, visit this group at http://groups.google.com/group/atv-bootloader?hl=en
