On Fri, May 13, 2011 at 12:39:53PM -0400, thus spake Brian Prodoehl: > Have you tested only with hw crypto? Try passing the nohwcrypt param > to the module while loading. I just tried that and at first it seemed to make no difference. But at some point, one of the two nodes of my testbed started to send encrypted frames (both broadcast and unicast) and the other node could receive them okay. Unfortunately, I just can't make the other node work (the difference being it is a x86_64 netbook vs. an i386 embedded atom industrial PC for the first node). Next week, I'll hopefully have more time to investigate and find a repeatable procedure to make that work or break. My preliminary tests show that setting the nohwcrypt option makes no difference. Thanks for the hint anyway. Ignacy -- A person is shit's way of making more shit. -- S. Barnett, anthropologist. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
