From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend@broadcom.com>
Cc: Maximilian Engelhardt <maxi@daemonizer.de>,
brcm80211-dev-list@broadcom.com,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: WLAN not working anymore after changing the MAC address
Date: Sun, 09 Dec 2012 19:25:40 +0100 [thread overview]
Message-ID: <1355077540.9878.1.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1355077493.9878.0.camel@jlt4.sipsolutions.net> (sfid-20121209_192436_572441_F392233B)
On Sun, 2012-12-09 at 19:24 +0100, Johannes Berg wrote:
> On Sun, 2012-12-09 at 18:52 +0100, Arend van Spriel wrote:
>
> > > After changing the MAC address of my wireless network interface it
> > > doesn't work anymore. I would very much like to change the MAC
> > > address to avoid being traceable by it. Steps how this can be
> > > reproduced are shown below. Here is first some information about my
> > > Hardware and test setup:
> > >
> >
> > How is this supposed to be distributed to the driver? I have been
> > looking in the mac80211 interface. The only callback that I can think
> > is is the change_interface() callback although the documentation does
> > state this is only for changing the interface type. Or is it to be
> > done upon add_interface()?
>
> You should read the interface address in add_interface and basically
read ... well that came out wrong. I mean use vif->addr.
johannes
next prev parent reply other threads:[~2012-12-09 18:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201212090940.38269.maxi@daemonizer.de>
2012-12-09 17:52 ` WLAN not working anymore after changing the MAC address Arend van Spriel
2012-12-09 18:24 ` Johannes Berg
2012-12-09 18:25 ` Johannes Berg [this message]
2012-12-09 22:35 ` Arend van Spriel
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=1355077540.9878.1.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=maxi@daemonizer.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.