Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 Jan 2008 20:37:39 +0800
From:      "Sepherosa Ziehau" <sepherosa@gmail.com>
To:        "=?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?=" <des@des.no>
Cc:        kevlo@freebsd.org, sam@freebsd.org, current@freebsd.org, net@freebsd.org
Subject:   Re: if_ral regression
Message-ID:  <ea7b9c170801110437w3313d346i60b1cebffb911d3e@mail.gmail.com>
In-Reply-To: <864pds8idc.fsf@ds4.des.no>
References:  <86ir2hznnd.fsf@ds4.des.no> <ea7b9c170712312227m7a961c95kc2bed20f94d09593@mail.gmail.com> <86abnpu0wv.fsf@ds4.des.no> <ea7b9c170801020518m6d5f8fdejd01947166669e9e4@mail.gmail.com> <86abnovy4k.fsf@ds4.des.no> <86odc3dlgi.fsf@ds4.des.no> <ea7b9c170801031824n2205c1e8i2f010df67a07dfff@mail.gmail.com> <86lk76c6t5.fsf@ds4.des.no> <ea7b9c170801040620l1e1c27a1t30a875b32dc0f01c@mail.gmail.com> <864pds8idc.fsf@ds4.des.no>

next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 5, 2008 10:19 PM, Dag-Erling Sm=F8rgrav <des@des.no> wrote:
> "Sepherosa Ziehau" <sepherosa@gmail.com> writes:
> > This actually brings up two things:
> > 1) I think we should ignore seq in multicast frames; this is permitted =
in
> > 802.11 standard.  In dfly I did that, since one of our users
> > encountered a broken commercial AP which is not 802.11e but uses
> > different seq for data and beacon.
> > 2) TX sequence.  I think standards only mention QSTA/nQSTA, but not
> > AP.  Currently our AP uses per node TX seq, which means beacon's seq
> > is difficult to choose, at least for 2560 based ral(4), whose beacons'
> > seq need to be set by software.  I saw Linksys AP uses one seq for all
> > of the frames it sends.  Sam, what's you opinion on this?
> >
> > I think if STA counts ral(4)'s beacon seq, as what we do currently,
> > beacon missing will quickly happen since beacons will be discarded
> > after first several data frames.
>
> OK, I *think* I understood most of that.  Does this suggest a solution
> to you?  I will try to get the wlandebug output tonight.

I don't know whether you are still interested to track down the wired
problem you had experienced.
If you have time please try following patches:

revert the old patch at your AP side and try this one
http://people.freebsd.org/~sephe/rt2560_test.diff1

apply following patch at you STA side
http://people.freebsd.org/~sephe/ieee80211_input.c.diff

Best Regards,
sephe

--=20
Live Free or Die



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ea7b9c170801110437w3313d346i60b1cebffb911d3e>