OK, I spent some time with filtering of NM log. I removed the debug lines related to WiFi connections management (they contain way too much sensitive data IMO, and are irrelevant to my problem anyway). Still the resulting file is around 280k (1,5k lines), so the question is: Is it OK to attach such "huge" file here? Or shall I gzip (bzip2/xz ) it first?
Jeka On Mon, Nov 16, 2015 at 4:57 PM Jetchko Jekov <[email protected]> wrote: > I am not comfortable sending full NM log (even partially filtered) on > public mailing list. is there a way to do it privately? > > Br, > Jeka > > On Mon, Nov 16, 2015 at 4:29 PM Thomas Haller <[email protected]> wrote: > >> On Mon, 2015-11-16 at 15:05 +0000, Jetchko Jekov wrote: >> > Hello, >> > >> > I am pretty sure that this question was raised several times already >> > on this list as I found some references when searching. But somehow >> > none of proposed settings work for me. >> > >> > In general, I want to tell NM to ignore all virtual interfaces which >> > are not explicitly created with it. For example interfaces created by >> > libvirt, virtual box, docker (that includes bridges, veth pairs, >> > tun/tap interfaces and so on) . These are not in control of NM and I >> > am not sure why NM insist on reporting status and/or controlling >> > them. >> > Currently I am trying tell NM to ignore tap interface which is my end >> > of VPN tunnel without success at all. It insist to run dhclient on >> > this interface breaking my network setup. >> > >> > after many iterations my current config (as parsed by NM itself) is: >> > nm_config_data_log(): CONFIG: [main] >> > nm_config_data_log(): CONFIG: plugins=keyfile,ifupdown,ifcfg- >> > rh,ibft >> > nm_config_data_log(): CONFIG: dns=dnsmasq >> > nm_config_data_log(): CONFIG: no-auto-default=* >> > nm_config_data_log(): CONFIG: ignore-carrier=* >> > nm_config_data_log(): CONFIG: >> > nm_config_data_log(): CONFIG: [ifupdown] >> > nm_config_data_log(): CONFIG: managed=false >> > nm_config_data_log(): CONFIG: >> > nm_config_data_log(): CONFIG: [logging] >> > nm_config_data_log(): CONFIG: level=DEBUG >> > nm_config_data_log(): CONFIG: >> > nm_config_data_log(): CONFIG: [connectivity] >> > nm_config_data_log(): CONFIG: uri=http://fedoraproject.org/static/h >> > otspot.txt >> > nm_config_data_log(): CONFIG: response=OK >> > nm_config_data_log(): CONFIG: interval=300 >> > nm_config_data_log(): CONFIG: >> > nm_config_data_log(): CONFIG: [keyfile] >> > nm_config_data_log(): CONFIG: unmanaged-devices=interface- >> > name:~virbr?;interface-name:~vboxnet?;interface- >> > name:~docker?;interface-name:tap?;interface-name:~tap?;type:tap >> >> >> keyfile.unmanaged-devices should do it. >> >> You already enabled DEBUG logging, can you post the logfile during >> startup to see why NM has the device managed? >> >> >> Thomas >> >
_______________________________________________ networkmanager-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/networkmanager-list
