Hi,

On Tue, 8 Apr 2014 20:40:01 -0700
Adrian Chadd <adr...@freebsd.org> wrote:

> I'm not sure. I'd really like to see what the story is with
> coexistence somehow.

one other note. I start my machine randomly with a kernel built from
sources dated 26.03.14. I never faced this problem with these sources.

Erich
> 
> 
> -a
> 
> 
> On 8 April 2014 20:32, Erich Dollansky <erichsfreebsdl...@alogt.com>
> wrote:
> > Hi,
> >
> > On Tue, 8 Apr 2014 20:07:39 -0700
> > Adrian Chadd <adr...@freebsd.org> wrote:
> >
> >> Coexistence is to deal with the fact that a 40MHz channel may
> >> overlap a 20MHz-only AP in the extension channel.
> >>
> >> If the AP finds a 20MHz AP in the extension channel (ie, the other
> >> half of its 40MHz) channel then it'll flip itself to 20MHz. If it
> >> determines it isn't there any more, it'll flip the BSS to the 40MHz
> >> channel.
> >>
> >> Now, why the hell it's causing the connection to fail? I have no
> >> idea.
> >>
> >> can someone file a PR that says it's all busted with 40MHz
> >> coxistence enabled? We can then start debugging from that position.
> >>
> > I am not so sure if it is a general problem or just a DLink problem.
> >
> > I just activated my own access point and it worked there. The only
> > problem is that it also works with DLink but only randomly. So, it
> > still could have been that I was just always lucky when connecting
> > to the ProLink access point I have.
> >
> > As the DLink is not mine, I am not even able to access its
> > administration interface.
> >
> > Can I suggest to wait a bit to get more feedback to see if it is a
> > general problem or a problem only linked to one manufacturer?
> >
> > Erich

_______________________________________________
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Reply via email to