From owner-freebsd-wireless@FreeBSD.ORG Wed Jul 27 10:48:50 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F77A106564A for ; Wed, 27 Jul 2011 10:48:50 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id C2FA98FC0C for ; Wed, 27 Jul 2011 10:48:49 +0000 (UTC) Received: by gxk28 with SMTP id 28so1171983gxk.13 for ; Wed, 27 Jul 2011 03:48:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=QbA8AZMXNkv7O7TtDpYnsl/UZQannrEyPszAiH9Z38Q=; b=b7ydz5nUTQ9oyKgfqFv6xr6Wt29kF63tV3SJcSHHNyuExhuZgyt++lghfGfovL9+oU FiOOAeqYEB8P2ThcYzv7C0GdtaN3mTodO4JQVROB5HwMZHpg1woVGgo7gVlebCwzi2ST ANl9nQwAf9wtq5dkCUiErDKbZwb18x+kjFJ+Q= MIME-Version: 1.0 Received: by 10.150.225.1 with SMTP id x1mr21552ybg.272.1311763729058; Wed, 27 Jul 2011 03:48:49 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.150.197.5 with HTTP; Wed, 27 Jul 2011 03:48:49 -0700 (PDT) In-Reply-To: References: Date: Wed, 27 Jul 2011 18:48:49 +0800 X-Google-Sender-Auth: Y9tD-4AvMOwYetS8OV9pU7npico Message-ID: From: Adrian Chadd To: Monthadar Al Jaberi Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: Ack, Net80211 & ath X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2011 10:48:50 -0000 Hi, Yup, you're right. net80211 doesn't get notification of it by default. What do you need it for? Adrian On 27 July 2011 18:23, Monthadar Al Jaberi wrote: > Hi, > > How is ack frames being handled by the net80211? I guess the driver > (or maybe hardware) takes care of resending, but what happens if it > max number of retries is reached? How is net8011 notified? > > There is ieee80211_add_callback that I think should be used for that, > but it is only used by managment frames of type > IEEE80211_FC0_SUBTYPE_ASSOC_REQ, IEEE80211_FC0_SUBTYPE_REASSOC_REQ and > IEEE80211_FC0_SUBTYPE_AUTH (in station mode) and one for HT code. > > What about the others? I guess the hardware only keeps stat counters > for failures.... > > br, > > -- > //Monthadar Al Jaberi > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" >