lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 12 Aug 2014 10:43:27 +0200
From:	Jonas Gorski <>
To:	Marcel Holtmann <>
Cc:	Daniel Gimpelevich <>,
	"John W. Linville" <>,
	" Wireless" 
	Johannes Berg <>,
	"David S. Miller" <>,
	Network Development <>,
	"" <>
Subject: Re: [PATCH] allow setting wiphy.perm_addr after driver probe

On Tue, Aug 12, 2014 at 9:59 AM, Marcel Holtmann <> wrote:
> Hi Daniel,
>>> the way I read the nl80211 code is that the NL80211_CMD_NEW_INTERFACE
>>> requires a wiphy device to be specified. And that is actually just a
>>> number. So I have no idea what the MAC has to here.
>> OpenWrt finds a wiphy by its MAC.
> maybe that is the first problem right there. I see that over sysfs you get phy80211/macaddress. However if you do a dump via NL80211_CMD_GET_WIPHY then you do not have the MAC address there.

OpenWrt nowadays uses the device path in sysfs/devices to identify
wiphys, not the mac anymore (e.g 'pci0000:00/0000:00:01.0/ssb0:0').

To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists