From: "Arend van Spriel" <arend@broadcom.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
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, 9 Dec 2012 23:35:05 +0100 [thread overview]
Message-ID: <50C51219.2090900@broadcom.com> (raw)
In-Reply-To: <1355077540.9878.1.camel@jlt4.sipsolutions.net>
On 12/09/2012 07:25 PM, Johannes Berg wrote:
> 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.
Thanks, Johannes
I got the idea of it.
Gr. AvS
prev parent reply other threads:[~2012-12-09 22:35 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
2012-12-09 22:35 ` Arend van Spriel [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=50C51219.2090900@broadcom.com \
--to=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=johannes@sipsolutions.net \
--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 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).