From: Patrick Grimm <patrick@lunatiki.de>
To: "Chatre, Reinette" <reinette.chatre@intel.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [HOTFIX] Re: mac80211/iwl4965: ad-hoc broken in 2.6.25-rc1
Date: Fri, 15 Feb 2008 02:29:09 +0100 [thread overview]
Message-ID: <200802150229.09602.patrick@lunatiki.de> (raw)
In-Reply-To: <D936D925018D154694D8A362EEB0892003ABCCAE@orsmsx416.amr.corp.intel.com>
Am Freitag, 15. Februar 2008 01:21:15 schrieb Chatre, Reinette:
> On , Chatre, Reinette wrote:
> > On Thursday, February 14, 2008 3:40 PM, Patrick Grimm wrote:
> >> For me not.
> >> I use 3945ABG card in an ad-hoc network with 4 other wlan devices
> >> like rt2500 and ath5k. I have applied your
> >> 0001-iwlwifi-only-check-for-association-id-when-associat.patch
> >> patch. But i can't see incoming packets witch tcpdump.
> >> I have try to commet out the check for associat with the same
> >> result.
> >>
> >> dmesg
> >> iwl3945: I iwl3945_rx_handle r = 76, i = 75, REPLY_3945_RX, 0x1b
> >> iwl3945: I iwl3945_rx_handle r = 77, i = 76, REPLY_3945_RX, 0x1b
> >> iwl3945: I iwl3945_mac_tx enter
> >> iwl3945: I iwl3945_tx_skb Dropping - !iwl3945_is_associated
> >> iwl3945: I iwl3945_mac_tx leave
> >> iwl3945: I iwl3945_rx_handle r = 78, i = 77, REPLY_3945_RX, 0x1b
> >> iwl3945: I iwl3945_rx_handle r = 79, i = 78, REPLY_3945_RX, 0x1b
> >
> > When you say "with the same result" does it mean that you comment out
> > the check for priv->assoc_id and you still see the error "Dropping -
> > !iwl3945_is_associated" or do you then see traffic with tcpdump?
I mean that I don't see traffic with tcpdump and I don't see the Dropping
error.
> >
> > Could you please print out the values of fc, priv->iw_mode,
> > iwl3945_is_associated(priv) and priv->assoc_id just before that error
> > message is printed?
Yes
iwl3945: I iwl3945_tx_skb fc: 8<3>
iwl3945: I iwl3945_tx_skb mode: 2<3>
iwl3945: I iwl3945_tx_skb assoc_id: 0<3>
iwl3945: I iwl3945_tx_skb Dropping - !iwl3945_is_associated
My changes
IWL_DEBUG_DROP("fc: %d\n", fc);
IWL_DEBUG_DROP("mode: %d\n", priv->iw_mode);
IWL_DEBUG_DROP("assoc_id: %d\", priv->assoc_id);
if ((!iwl3945_is_associated(priv) ||
((priv->iw_mode == IEEE80211_IF_TYPE_STA) && !priv->assoc_id)) &&
((fc & IEEE80211_FCTL_FTYPE) == IEEE80211_FTYPE_DATA)) {
IWL_DEBUG_DROP("Dropping - !iwl3945_is_associated\n");
goto drop_unlock;
}
Was it right?
>
> One more question ... did ad-hoc work for you before this patch?
No. In my tests only ipw3945 works in Ad-Hoc mode.
next prev parent reply other threads:[~2008-02-15 2:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 19:31 mac80211/iwl4965: ad-hoc broken in 2.6.25-rc1 Richard Scherping
2008-02-12 21:51 ` Chatre, Reinette
2008-02-12 23:06 ` Richard Scherping
2008-02-13 9:06 ` [HOTFIX] " Richard Scherping
2008-02-13 22:20 ` Chatre, Reinette
2008-02-14 18:26 ` Richard Scherping
2008-02-14 23:40 ` Patrick Grimm
2008-02-14 23:57 ` Chatre, Reinette
2008-02-15 0:21 ` Chatre, Reinette
2008-02-15 1:29 ` Patrick Grimm [this message]
2008-02-15 16:39 ` Chatre, Reinette
2008-02-15 21:12 ` Richard Scherping
2008-02-15 21:21 ` Chatre, Reinette
2008-02-16 0:19 ` Patrick Grimm
2008-02-17 21:37 ` Patrick Grimm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200802150229.09602.patrick@lunatiki.de \
--to=patrick@lunatiki.de \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).