NetworkManager/tools/nm-guest-data/nm-90-my.conf.in

[main]
no-auto-default=*
debug=RLIMIT_CORE,fatal-warnings

[logging]
level=TRACE
domains=ALL,VPN_PLUGIN:TRACE

[device-managed-0]
match-device=interface-name:d_*,interface-name:tap*
managed=0

[device-managed-1]
match-device=interface-name:net*,interface-name:eth*
managed=1

[device-host-net]
match-device=interface-name:host_net
managed=0
tools: nm-in-container: don't generate files from the script The script was generating the data-* files that later copies to the container. In order to the files being reusable for nm-in-vm, put them as separate files inside the data directory. However, some of the files need the full path to NetworkManager project, which varies for each user. Instead, make a sed replacement on them and generate the actual files that will be copied. Replacement: {{BASEDIR_NM}} -> $BASEDIR_NM Also, rename the files to more descriptive names, using some prefixes that give a hint of where those files will be put, and the .in extension to indicate that they will be processed. 2023-07-21 15:36:22 +02:00			`[main]`
			`no-auto-default=*`
			`debug=RLIMIT_CORE,fatal-warnings`

			`[logging]`
			`level=TRACE`
			`domains=ALL,VPN_PLUGIN:TRACE`

			`[device-managed-0]`
			`match-device=interface-name:d_,interface-name:tap`
			`managed=0`

			`[device-managed-1]`
			`match-device=interface-name:net,interface-name:eth`
			`managed=1`
tools: nm-in-vm: fix connectivity with host The connectivity with the host depends on getting a DHCP lease from the host. With the latest commit's customizations, the virtual NIC is not managed by NM so it is not configured. Keep it unmanaged so debuging NetworkManager doesn't affect to this virtual NIC. Use dhclient to get a DHCP lease from the host. Assign a fixed interface name (host_net) to match it from NM and dhclient config files. 2023-08-03 11:53:42 +02:00
			`[device-host-net]`
			`match-device=interface-name:host_net`
			`managed=0`