Bug 1387421

Summary:	network manager use random MAC for scanning WiFi
Product:	Red Hat Enterprise Linux 7	Reporter:	Dalibor Pospíšil <dapospis>
Component:	NetworkManager	Assignee:	sushil kulkarni <sukulkar>
Status:	CLOSED DUPLICATE	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.3	CC:	atragler, bgalvani, fgiudici, lrintel, rkhan, sukulkar, thaller
Target Milestone:	rc	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-10-21 09:25:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Dalibor Pospíšil 2016-10-20 20:21:37 UTC

Description of problem:
NetworkManager randomly changes MAC address of WiFi device while scanning for available networks by default. This is regression against RHEL-7.2. It should be optional, not default.

Version-Release number of selected component (if applicable):
NetworkManager-1.4.0-12.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. disconnect from any WiFi, disable WiFi using nm-applet
2. enable WiFi using nm-applet
3. watch ip a / journalctl

Actual results:
Oct 20 20:25:29 sopos-ntb.usersys.redhat.com NetworkManager[30881]: <info>  [1476987929.4813] device (wlp3s0): set-hw-addr: set MAC address to 1E:D0:81:3B:24:B0 (scanning)
...
Oct 20 20:30:44 sopos-ntb.usersys.redhat.com NetworkManager[30881]: <info>  [1476988244.4800] device (wlp3s0): set-hw-addr: set MAC address to 8A:50:CF:42:5C:AA (scanning)


Additional info:
regression against NetworkManager-1.0.6-27.el7.x86_64

Comment 2 Thomas Haller 2016-10-21 09:25:30 UTC

This was an intentional change.

This is a duplicate of bug 1387350.

It would be helpful, if you could elaborate (on the other bug) what concrete issue this causes for you. Thanks.

*** This bug has been marked as a duplicate of bug 1387350 ***