netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Woodard <woodard@redhat.com>
Cc: netdev@vger.kernel.org
Subject: Re: WiFi and changed MAC addrs
Date: Wed, 05 Sep 2007 17:34:44 +0200	[thread overview]
Message-ID: <1189006484.9942.113.camel@johannes.berg> (raw)
In-Reply-To: <46DEC94C.9010301@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]

On Wed, 2007-09-05 at 08:20 -0700, Ben Woodard wrote:

> If a particular piece of hardware will refuse to send frames after the 
> MAC address has been changed, then shouldn't the card's driver refuse to 
> allow a change of the MAC address and return an error in response to the 
> IOCTL that tries to change it?

Yes.

> I can't think of a situation where this 
> wouldn't be the right thing to do. However, before I submit a patch to 
> fix this, does anyone else know of any special cases that I might need 
> to deal with?

That wouldn't make sense now, would it?

> Also is behavior of refusing to send frames with a non-hardware 
> specified MAC address part of the WiFi spec or is it particular to 
> certain WiFi cards? IOW at what level do I need to fix it? Should I just 
> fix it for the Intel cards that I've tested or do I need to fix it for 
> all WiFi cards?

Most wifi cards don't care at all what MAC address you send, in fact
allowing you to send with various MAC addresses. So this is something
intel specific. Oh are we talking about iwlwifi? If so, please report to
their maintainers immediately, they're lazy bastards and don't even
upload the new MAC address to the card even if they could.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

      reply	other threads:[~2007-09-05 15:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-05 15:20 WiFi and changed MAC addrs Ben Woodard
2007-09-05 15:34 ` Johannes Berg [this message]

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=1189006484.9942.113.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=netdev@vger.kernel.org \
    --cc=woodard@redhat.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).