summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLubomir Rintel <lkundrak@v3.sk>2019-04-08 10:10:25 +0200
committerLubomir Rintel <lkundrak@v3.sk>2019-04-08 10:10:25 +0200
commita4a6a6b6ee907ad0ca4304f5f332354278bdcdc3 (patch)
tree52aa166c010553197595becf7a6011728f4870cc
parentce7a631ae6464290e3abfaa38a6905f7d88c6657 (diff)
downloadNetworkManager-a4a6a6b6ee907ad0ca4304f5f332354278bdcdc3.tar.gz
examples: drop rtl drivers from the mac address change blacklist
Just in case anyone uses this file as-is; I believe that these drivers don't need to be in a blacklist. There's a good chance they either work or we can detect failure to change a MAC address on runtime and act accordingly. Blacklisting the driver gives the driver maintainers no chance to fix the behavior and we are not able to log a warning on failure.
-rw-r--r--examples/nm-conf.d/31-mac-addr-change.conf4
1 files changed, 2 insertions, 2 deletions
diff --git a/examples/nm-conf.d/31-mac-addr-change.conf b/examples/nm-conf.d/31-mac-addr-change.conf
index 3a9400d98f..f32507a15c 100644
--- a/examples/nm-conf.d/31-mac-addr-change.conf
+++ b/examples/nm-conf.d/31-mac-addr-change.conf
@@ -5,7 +5,7 @@
#
# https://bugzilla.gnome.org/show_bug.cgi?id=777523
[device-31-mac-addr-change]
-match-device=driver:rtl8723bs,driver:rtl8189es,driver:r8188eu,driver:8188eu,driver:eagle_sdio,driver:wl
+match-device=driver:eagle_sdio,driver:wl
wifi.scan-rand-mac-address=no
[connection-31-mac-addr-change]
@@ -15,5 +15,5 @@ wifi.scan-rand-mac-address=no
#
# Also note that this is only the default. Per-profile settings still take
# precedence.
-match-device=driver:rtl8723bs,driver:rtl8189es,driver:r8188eu,driver:8188eu,driver:eagle_sdio,driver:wl
+match-device=driver:eagle_sdio,driver:wl
wifi.cloned-mac-address=preserve