On Mon, Aug 11, 2008 at 11:34:34PM +0200, Patrick Ale wrote: > Ello! > > On Mon, Aug 11, 2008 at 11:02 PM, Renee Danson <renee.danson at sun.com> > wrote: > > On Sat, Aug 09, 2008 at 12:18:03PM +0200, Patrick Ale wrote: > >> On Sat, Aug 9, 2008 at 11:35 AM, Toby Richmond <toby at > >> puddlecottage.co.uk> wrote: > > > > > This isn't entirely accurate. > > > > NWAM should work just fine with WPA; however, not all wireless drivers > > support it. Quaker or one of the other folks from the wireless team can > > give you an authoritative answer on which drivers do/do not support WPA. > > I already got my answer from quaker. I did a fresh install of SXCE95 > and that fixed it for me. BFU-ing from SXCE90 to b95 wont work well > apparently, nwam wise :)
Ah. The bfu issue is puzzling, but I'm glad the clean install took care of things. > > If you find that you can connect with WPA using dladm, but cannot with > > NWAM, that's a bug that we'd like to know about; nwamd uses libdladm, > > the same backend as dladm, so if one works, the other should as well. > > Could you enable nwam debugging and get a log of an attempt to connect > > using WPA? You can find notes on how to do that on the troubleshooting > > page: > > > > The problem is that it appears as if the timeout setting NWAM uses is > to low. dladm only works when I run it like, dladm -e essid -k key -m > g -T 120 , and even then sometimes I get a timeout and have to retry. > Next to that I seem to have had a known issue with nwam that when you > change the password on the router, nwam wont ask you for new password > credentials, I've talked offline with Quaker about this and he told me > what to do :) Thanks for the info! We're painfully aware of the password problem, and working on ways to make that better; but I hadn't run across a situation where you needed to extend the timeout. We might need to make that a tunable of some sort for nwam. -renee
