Created
July 12, 2016 01:19
-
-
Save lanrat/458066dbdeb460b9cef40dc2af639a24 to your computer and use it in GitHub Desktop.
NetworkManager ignore docker, virtualbox, and vmware adapters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| [main] | |
| plugins=ifupdown,keyfile | |
| [ifupdown] | |
| managed=false | |
| [keyfile] | |
| unmanaged-devices=interface-name:docker0;interface-name:vmnet1;interface-name:vmnet8;interface-name:vboxnet0 |
@dragon788 Please see manpage for NetworkManager.conf, section "Device List Format"
It states clearly that:
interface-name:IFNAME, interface-name:~IFNAME Case sensitive match of interface name of the device. Simple globbing is supported with * and ?. Ranges and escaping is not supported. interface-name:=IFNAME Case sensitive match of interface name of the device. Globbing is disabled and IFNAME is taken literally.
I used this line to ignore bridge interfaces as well and use wildcards:
unmanaged-devices=interface-name:docker*;interface-name:br-*;interface-name:vmnet*;interface-name:vboxnet*
This tweak helped me with docker containers gets unavailable inside of vmware linux mint 20 (ubuntu 20.04) after pause/resume.
unmanaged-devices=interface-name:docker*;interface-name:veth*;interface-name:br-*;interface-name:vmnet*;interface-name:vboxnet*
Still works perfectly with wildcards, KDE Plasma. 👍
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Depending on the number of containers you have running there may also be numerous
vethXXXXXdevices as well. Does this support wildcards? If so it would be handy to dovmnet*as if you create more than the default NAT/bridge/host-only networks you will get more to ignore.