Users Report Faulty WPA In 2nd-Gen IPod Touch 188
jesuscash writes "It seems early adopters of the new iPod Touch are out of luck when they bring it home and attempt to connect it to their WPA/WPA2 secured network. Reading this Apple forum thread shows that many tests with different configurations show a no-go on WPA. Some of the last entries give the best clue, revealing a 'received deauthentication' error in their router logs. Apple has yet to respond."
Re:Single apple ipod touch bug slashdot worthy? (Score:2, Informative)
To use the ever-present car analogy, it would be like one of a car's most advertised features only working if you removed all the locks
Get a linksys router then (Score:5, Informative)
Re:An old problem, resurfaced (Score:2, Informative)
I have a D-Link DIR-655 set up with WPA. I'm typing this comment on a MacBook Pro running Leopard. Never had a problem with this combo. Neither has my wife with her MacBook/Leopard.
Are you using 802.11n? Compatibility issues are rife with this protocol :-/
Re:Single apple ipod touch bug slashdot worthy? (Score:2, Informative)
Re:Single apple ipod touch bug slashdot worthy? (Score:3, Informative)
Some major points against your solution (I'm the AC you've responded to)
Proposed solution: not broadcasting SSID
Verdict:
a. anyone with entry level IT knowledge will be able to detect and connect to non-SSID-broadcasting APs. I don't want anyone to connect to my AP unauthorized. If everyone would be fair and could be trusted to not upload illegal material or download oodles of torrents, that would be fine, but in our current world, no.
b. anyone with mid to high level IT knowledge will be able to eavesdrop on any cleartext going over the air. I don't want anyone to listen to my connection, no matter I look for cookie recipes or make stock trade orders. There are several housemates on my WLAN with less than entry-level IT knowledge and it's my responsibility to protect them.
Proposed solution 2: restrict MAC entries.
Verdict:
a. I don't have enough time to actively administer my AP, so every housemate and their guest can use the net. SSID and password are pinned on the fridge, everyone who is trustworthy enough to enter our apartment is considered trustworthy enough to access our network until proven otherwise. With 5 roommates and several guests a month, everything else would be like a second job.
b. MACs can be spoofed. This may require mid-high-level IT knowledge, but I don't want anyone unauthorized on my net. See above entries: IT-un-savvy roommates, friends and guests need protection.
Conclusion: proposed solutions would be unworkable given my time constraints and requirements ("You can access my net IF you are able to access my apartment AND you don't bother me").
Personal opinion: redesigning network policies because of a single misbehaving or incompatible device is a waste of time.
Character encoding (5:erocS) (Score:3, Informative)
Spell Apple with the Euro symbol for the E.
Can't, reliably, unless you mean actually spelling out the three-letter currency sign as in "ApplEUR" or "AppGBPe". Due to past abuses of directional overrides [slashdot.org], Slashdot is not configured to work well with code points U+0100 and above. Heck, I haven't even got Firefox 3 + Slashdot D2 to work reliably with U+00A0 through U+00FF.
Re:Problem seems to be with D-Link routers... (Score:3, Informative)
My roommate got a MacBook recently, and he couldn't connect to our D-Link router. The fix was to put his MAC address directly into the router's DHCP config.
Actually, this isn't the first time this has happened. It's occured with Thinkpads and Linksys cards, and my D-Link card. Doing the MAC address thing and assigning static IPs solved a lot of problems with this router.