linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Scherping <richard@scherping.de>
To: "Chatre, Reinette" <reinette.chatre@intel.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: mac80211/iwl4965: ad-hoc broken in 2.6.25-rc1
Date: Wed, 13 Feb 2008 00:06:53 +0100	[thread overview]
Message-ID: <47B2268D.7060205@scherping.de> (raw)
In-Reply-To: <D936D925018D154694D8A362EEB0892003A461BF@orsmsx416.amr.corp.intel.com>

Chatre, Reinette schrieb:

> We have not done ad-hoc testing in the recent code. Any debugging you
> can do will be greatly appreciated (anything interesting in your logs?).
> Just to confirm the monitor mode is ok, can you confirm that your
> monitoring machine can see data between a host and AP? We have seen some
> problems with monitoring in iwlwifi so I would like to make sure.

The monitoring (as well as the counterpart for ad-hoc operation) was done with madwifi 0.9.3.3 on a different machine with kernel 2.6.22 - a setup that has proven to work for me already.

> Please load the driver with debugging (debug=0x43fff) and send us what
> you see during data transmission. It may be useful to open a bug at
> bughost.org at this point for us to keep track of the problem.

Looking at the debugging output helped a bit:

Feb 12 23:27:37 merom kernel: iwl4965: I iwl4965_mac_tx enter
Feb 12 23:27:37 merom kernel: iwl4965: I iwl4965_tx_skb Dropping - !iwl4965_is_associated
Feb 12 23:27:37 merom kernel: iwl4965: I iwl4965_mac_tx leave

I changed that output to be more verbose:

iwl4965: I iwl4965_tx_skb Dropping - !iwl4965_is_associated: iwl4965_is_associated(priv)=1; priv->assoc_id=0; priv->assoc_station_added=1

This is in line with the following output:

Feb 12 23:44:08 merom kernel: iwl4965: U iwl4965_bg_post_associate Associated as 0 to: 2a:20:22:f0:4f:f0

The full log is available at http://www.scherping.de/misc/iwl4965-2625rc1.txt
What I did is:

merom:/home/richard# uname -a
Linux merom 2.6.25-rc1 #1 SMP Mon Feb 11 08:18:47 CET 2008 x86_64 GNU/Linux
merom:/home/richard# modprobe iwl4965 debug=0x43fff
merom:/home/richard# iwconfig wlan0 mode ad-hoc
merom:/home/richard# ifconfig wlan0 10.0.0.1 up
merom:/home/richard# iwconfig wlan0 channel 1
merom:/home/richard# iwconfig wlan0 essid test
merom:/home/richard# iwconfig wlan0
wlan0     IEEE 802.11g  ESSID:"test"  
          Mode:Ad-Hoc  Frequency:2.412 GHz  Cell: 2A:20:22:F0:4F:F0   
          Tx-Power=27 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B   
          Encryption key:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

merom:/home/richard# ping 10.0.0.2
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
>From 10.0.0.1 icmp_seq=1 Destination Host Unreachable
>From 10.0.0.1 icmp_seq=2 Destination Host Unreachable
>From 10.0.0.1 icmp_seq=3 Destination Host Unreachable
^C
--- 10.0.0.2 ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4016ms
, pipe 3
merom:/home/richard# 

The same thing worked with 2.6.24 - 10.0.0.2 is the other ad-hoc station (MadWifi-based).

Thanks for your help!

Richard

  reply	other threads:[~2008-02-12 23:06 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 [this message]
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
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=47B2268D.7060205@scherping.de \
    --to=richard@scherping.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).