lists.openwall.net | 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 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 11 Aug 2014 17:01:06 -0700 From: Daniel Gimpelevich <daniel@...pelevich.san-francisco.ca.us> To: Marcel Holtmann <marcel@...tmann.org> Cc: "John W. Linville" <linville@...driver.com>, "linux-wireless@...r.kernel.org Wireless" <linux-wireless@...r.kernel.org>, Johannes Berg <johannes@...solutions.net>, "David S. Miller" <davem@...emloft.net>, Network Development <netdev@...r.kernel.org>, linux-kernel@...r.kernel.org Subject: Re: [PATCH] allow setting wiphy.perm_addr after driver probe On Mon, 2014-08-11 at 16:56 -0700, Marcel Holtmann wrote: > 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. > Why does the wiphy need to know the MAC if it is always specified from > userspace when actually creating the new netdev interface. Works for > P2P devices, so why wouldn't it work for access point and station > mode? > A MAC can be specified for the netdev, but it is assigned to a wiphy identified by its MAC. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists