linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Pedro Francisco <pedrogfrancisco@gmail.com>
Cc: linux-wireless@vger.kernel.org, ipw3945-devel@lists.sourceforge.net
Subject: Re: iwl3945: WPA2+swcrypto=0: receives broadcast only
Date: Thu, 16 Feb 2012 13:03:04 +0100	[thread overview]
Message-ID: <20120216120303.GD25833@redhat.com> (raw)
In-Reply-To: <CAJZjf_y_fSYv0U8y8APLJAvWe=xKWpa_poLc9h7qjQuRSj_rGw@mail.gmail.com>

Hi

On Mon, Feb 06, 2012 at 06:41:21PM +0000, Pedro Francisco wrote:
> When I connect to a WPA2 AP with swcrypto=0 I get the following kinds
> of traffic:
> ARP (Broadcast)
> DHCP (255.255.255.255)
> IGMP (224.0.0.22 and 224.0.0.1)
> 
> If I do a normal DHCP, I get no response. If I do "dhclient -B",
> requesting BOOTP broadcast flag, I get an IP, as expected. However ARP
> requests go unresponded as expected.
> 
> The closest I've found relative to this is
> http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=1872 . It is
> however reported as fixed on *both* "software/hardware crypto with
> WPA2 PSK and EAP" (2009-01-06).
> 
> It seems curious I can receive broadcast traffic but not traffic specific to me.
Brodcast traffic encrypted with different key, but perhaps there are
some more differences.

I think that hw crypto problems can be fixed only in firmware, but I'm
not sure.

> I'd present the debug of iwl3945 but apparently that option was
> removed from iwl3945 module?
??? absolutily not, perhaps you did not compile CONFIG_IWLEGACY_DEBUG=y ?

Stanislaw

  reply	other threads:[~2012-02-16 12:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06 18:41 iwl3945: WPA2+swcrypto=0: receives broadcast only Pedro Francisco
2012-02-16 12:03 ` Stanislaw Gruszka [this message]
2012-03-01  2:05   ` Pedro Francisco

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=20120216120303.GD25833@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pedrogfrancisco@gmail.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).