linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Reinette Chatre <reinette.chatre@intel.com>
Subject: Re: IWL3945 problems in 2.6.35-rc1
Date: Fri, 18 Jun 2010 11:28:47 +0200	[thread overview]
Message-ID: <1276853327.3638.17.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1275395142.14385.6.camel@maxim-laptop>

Maxim,

> 2. mulicast/broadcast is broken.
> this results in DHCP non working on open access point.
> It seems that DHCP does work on my home wireless, but avahi-autoipd
> doesn't see any neighbours, and this is annoying.
> It can be worked around by doing (sudo ifconfig wlan0 promisc)

Reinette has reverted the patch in iwlwifi-2.6, but I think I actually
just now identified the problem. Can you try one or two things for me?

 1) with the patch reverted, which is what presumably you're running
    now, can you try
    ifconfig wlan0 allmulti
    ifconfig wlan0 -allmulti

    I think this will *break* the driver right now.

 2) with the patch *not* reverted, apply the patch below and see if that
    fixes the problem as well (if it gets mangled, just remove the one
    CHK() line manually)

Actually, (2) is obviously more important to me, but (1) would indicate
that my guess is correct wrt. what's causing the problem

Thanks,
Johannes

---
 drivers/net/wireless/iwlwifi/iwl-core.c |    7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

--- wireless-testing.orig/drivers/net/wireless/iwlwifi/iwl-core.c	2010-06-18 11:22:34.000000000 +0200
+++ wireless-testing/drivers/net/wireless/iwlwifi/iwl-core.c	2010-06-18 11:27:00.000000000 +0200
@@ -1331,7 +1331,6 @@ void iwl_configure_filter(struct ieee802
 			changed_flags, *total_flags);
 
 	CHK(FIF_OTHER_BSS | FIF_PROMISC_IN_BSS, RXON_FILTER_PROMISC_MSK);
-	CHK(FIF_ALLMULTI, RXON_FILTER_ACCEPT_GRP_MSK);
 	CHK(FIF_CONTROL, RXON_FILTER_CTL2HOST_MSK);
 	CHK(FIF_BCN_PRBRESP_PROMISC, RXON_FILTER_BCON_AWARE_MSK);
 
@@ -1346,6 +1345,12 @@ void iwl_configure_filter(struct ieee802
 
 	mutex_unlock(&priv->mutex);
 
+	/*
+	 * Receiving all multicast frames is always enabled by the
+	 * default flags setup in iwl_connection_init_rx_config()
+	 * since we currently do not support programming multicast
+	 * filters into the device.
+	 */
 	*total_flags &= FIF_OTHER_BSS | FIF_ALLMULTI | FIF_PROMISC_IN_BSS |
 			FIF_BCN_PRBRESP_PROMISC | FIF_CONTROL;
 }




  parent reply	other threads:[~2010-06-18  9:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-01 12:25 IWL3945 problems in 2.6.35-rc1 Maxim Levitsky
2010-06-01 14:57 ` Maxim Levitsky
2010-06-01 15:21   ` Sedat Dilek
2010-06-01 18:12     ` Maxim Levitsky
2010-06-02 16:53       ` Maxim Levitsky
2010-06-02 18:01         ` Sedat Dilek
2010-06-01 19:03     ` Abhijeet Kolekar
2010-06-01 19:59       ` Maxim Levitsky
2010-06-02  8:35       ` Sedat Dilek
2010-06-03  6:00         ` reinette chatre
2010-06-03  9:18           ` Sedat Dilek
2010-06-03 15:55             ` reinette chatre
2010-06-18  9:28 ` Johannes Berg [this message]
2010-06-18 10:19   ` Maxim Levitsky
2010-06-18 10:30     ` Johannes Berg
2010-06-18 10:40       ` Maxim Levitsky

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=1276853327.3638.17.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=maximlevitsky@gmail.com \
    --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).