On Mon, 19 May 2008 17:10:26 -0700
Quaker Fang <Quaker.Fang at Sun.COM> wrote:
> Michael Hunter wrote:
> > On Mon, 19 May 2008 14:04:19 -0700 (PDT)
> > Eric <eric.k.125 at gmail.com> wrote:
> >
> >
> >> Unfortunately, despite being right, it still doesn't work. I made a key,
> >> and it just says 'operation timed out'. I am positive that the internet
> >> is up, since I am typing this on Windows, with the internet working fine.
> >>
> >
> > WPA support wasn't integrated into Solaris until build 77. I'm
> > assuming you are using something more recent then that.
> >
> > It is hard to see into WPA (bugs 6673831, 6673837, 6673765). If you
> > have control over the (or a) AP I would suggest trying to either look
> > at any logs it has or manipulate it to see what other issues might
> > exist. You should also look at /var/adm/messages to see what the
> > driver is saying.
> >
> > I've filed 6704677 because I think WPA usability is serious compromised
> > by being almost completely opaque.
> >
> The opaque is intentional for end users, since end users need not to
> know the "wpa service",
> dladm control the service instance once it is need.
> (In Windows, the wpa is also opaque to end users)
OK, dladm needs to be able to tell you more if possible but I think
that is just passing the buck. While I agree that the user shouldn't
be involved in what WPA does or even what it does just being told it
timed out isn't a reasonable way to interact with the user.
mph
