View Single Post
Old 11-24-2010, 03:22 PM   #16
tubemonkey
monkey on the fringe
tubemonkey ought to be getting tired of karma fortunes by now.tubemonkey ought to be getting tired of karma fortunes by now.tubemonkey ought to be getting tired of karma fortunes by now.tubemonkey ought to be getting tired of karma fortunes by now.tubemonkey ought to be getting tired of karma fortunes by now.tubemonkey ought to be getting tired of karma fortunes by now.tubemonkey ought to be getting tired of karma fortunes by now.tubemonkey ought to be getting tired of karma fortunes by now.tubemonkey ought to be getting tired of karma fortunes by now.tubemonkey ought to be getting tired of karma fortunes by now.tubemonkey ought to be getting tired of karma fortunes by now.
 
tubemonkey's Avatar
 
Posts: 45,782
Karma: 158733736
Join Date: May 2010
Location: Seattle Metro
Device: Moto E6, Echo Show
Quote:
Originally Posted by LoganK View Post
In short, your last option above, tubemonkey, should have worked, and I'm not sure where the fault lies.

In general, AES WiFi support is implemented in hardware (which, as you might expect, means it generally performs better than TKIP), but I don't know if the Nook Color has support for it. (I attempted to look up the WiFi chipset through the MAC address only to learn that the MAC range is registered to "BARNES&NOBLE.COM" ... not very helpful. )
That was my thinking too. I've tried it three times already with no luck. I'll give it another shot next week when I have more time to research it.

B&N is so open ...LOL Remember the big NC event and not a word on the processor being used? Thankfully TI broke the silence and said "hey, it's us and this is what they used".
tubemonkey is offline   Reply With Quote