Bug 1387421 - network manager use random MAC for scanning WiFi
Summary: network manager use random MAC for scanning WiFi
Keywords:
Status: CLOSED DUPLICATE of bug 1387350
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: sushil kulkarni
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-20 20:21 UTC by Dalibor Pospíšil
Modified: 2016-10-21 09:25 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-21 09:25:30 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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 ***
Note You need to log in before you can comment on or make changes to this bug.