Date: Wed, 27 Jul 2011 19:06:51 +0800 From: Adrian Chadd <adrian@freebsd.org> To: Monthadar Al Jaberi <monthadar@gmail.com> Cc: freebsd-wireless@freebsd.org Subject: Re: Ack, Net80211 & ath Message-ID: <CAJ-Vmo=2EmcGYcCagXwXZARPFy5sQzDCSGG0V09kb8SM-j2YUQ@mail.gmail.com> In-Reply-To: <CA%2BsBSoK_0M92O13Xz96FJ-jHgGuE8xc%2BeMDRc6u5=NUEH97=TA@mail.gmail.com> References: <CA%2BsBSoLmGGZBWLSFbm9kh9YoRa4NO_wkx_330f_U7U7SH8s%2BkA@mail.gmail.com> <CAJ-Vmo=F9LhJaVoQT1t%2BTV-KCPh_D%2BnmH2BGNW=FkFBAzc7Mig@mail.gmail.com> <CA%2BsBSoKjviQyx5KbQrMrF_7LoJx3zeyV0=gXB1RrV==PXd4S_A@mail.gmail.com> <CA%2BsBSoK_0M92O13Xz96FJ-jHgGuE8xc%2BeMDRc6u5=NUEH97=TA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 27 July 2011 18:59, Monthadar Al Jaberi <monthadar@gmail.com> wrote: > Ok. For mesh forwarding information, how do I know about link failure > (not able to forward an MSDU/MMPDU). Cause then we need to generate a > PERR frame. Why not create a callback for all TXed frames when you're in mesh mode? Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=2EmcGYcCagXwXZARPFy5sQzDCSGG0V09kb8SM-j2YUQ>