Re: Network manager and Gnome 3.12
The only plugin enabled is the RH/Fedora one [main] plugins=ifcfg-rh should I put unmanaged for the virtual interfaces to avoid this unnecessary dhcp retries? The IP addresses are correct for them, but nm-applet still trying to get address from dhcp... very strange Thanks L: On 28 July 2014 00:37, Thomas Haller thal...@redhat.com wrote: On Sun, 2014-07-27 at 13:53 +0200, David BERCOT wrote: Hello, I'm on Debian (Sid) and I've recently upgraded to Gnome 3.12. For my network, I use guessnet to put the right configuration, depending on the place I plug my computer (work, home, etc...). Before Gnome 3.12, NM showed me the list of options (from /etc/network/interfaces) : - Ifupdown (Maison) - Ifupdown (Travail) - etc... Now, it shows me... nothing... And more, it uses DHCP even I'm in a place where the connection should be in static mode... It seems that, at boot, the right connection is configured by guessnet (for exemple Maison) but, just after, NM changes it with DHCP. Do you have any clue for me ? Thank you. check whether the ifupdown plugin is enabled in /etc/NetworkManager/NetworkManager.conf. See `man NetworkManager.conf`. Also, check the logfile of NM whether it was able to read those connections. Sounds like it was not. Thomas ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network manager and Gnome 3.12
It seems this is totally my fault (as always). By enabling Rhughes's Gnome 3.12 repo it's make my life harder and harder :) I don't blame him :) So, sometimes my nm-applet trying to get IP address through DHCP for virtual interfaces which should have static address. When I check the output of ifconfig I can see the correct values, but when I open nm-applet edit connections dialog I can see dhcp where I should see static addresses :) Here is my versions NetworkManager.x86_64 1:0.9.9.1-4.git20140319.fc20 @rhughes-f20-gnome-3-12-x86_64 NetworkManager-adsl.x86_64 1:0.9.9.1-4.git20140319.fc20 @rhughes-f20-gnome-3-12-x86_64 NetworkManager-bluetooth.x86_64 1:0.9.9.1-4.git20140319.fc20 @rhughes-f20-gnome-3-12-x86_64 NetworkManager-glib.i6861:0.9.9.1-4.git20140319.fc20 @rhughes-f20-gnome-3-12-i386 NetworkManager-glib.x86_64 1:0.9.9.1-4.git20140319.fc20 @rhughes-f20-gnome-3-12-x86_64 NetworkManager-openvpn.x86_64 1:0.9.9.0-0.1.git20140128.fc20 @updates NetworkManager-openvpn-gnome.x86_64 1:0.9.9.0-0.1.git20140128.fc20 @updates NetworkManager-wwan.x86_64 1:0.9.9.1-4.git20140319.fc20 @rhughes-f20-gnome-3-12-x86_64 Maybe the easiest way to get back to normal is to reinstall my machine and forget those experimental repos :)) L: On 28 July 2014 14:34, Thomas Haller thal...@redhat.com wrote: On Mon, 2014-07-28 at 14:07 +0200, Pal, Laszlo wrote: The only plugin enabled is the RH/Fedora one [main] plugins=ifcfg-rh which would be correct, seeing that you use Fedora. should I put unmanaged for the virtual interfaces to avoid this unnecessary dhcp retries? The IP addresses are correct for them, but nm-applet still trying to get address from dhcp... very strange Not sure what you mean by unnecessary dhcp retries. If you don't want to use DHCP, set the IPv4 method to manual. Also not sure what you mean by unmanaged, but that doesn't sound right. Please configure the connections they way you want them too. Use nm-applet, or one of the other UI tools for that. If you have remaining issues, please give some more information, such as: what you want to do; what do you think you are doing; what seems to be happening; and what do you expect to happen instead. Thanks, Thomas ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network manager and Gnome 3.12
I think it is some kind of bug of specific version of NetworkManager since I have very similar issue with my virtual interfaces. They are configured as static but NM always trying to get IP address using DHCP. Here is my version: Installed Packages Name: NetworkManager Arch: x86_64 Epoch : 1 Version : 0.9.9.1 Release : 4.git20140319.fc20 Size: 5.7 M Repo: installed From repo : rhughes-f20-gnome-3-12-x86_64 Summary : Network connection manager and user applications URL : http://www.gnome.org/projects/NetworkManager/ License : GPLv2+ Description : NetworkManager is a system network service that manages your network devices : and connections, attempting to keep active network connectivity when available. : It manages ethernet, WiFi, mobile broadband (WWAN), and PPPoE devices, and : provides VPN integration with a variety of different VPN services. Someone told me I should try to use some COPR repo, but I can't find any newer version there L: On 27 July 2014 13:53, David BERCOT deb...@bercot.org wrote: Hello, I'm on Debian (Sid) and I've recently upgraded to Gnome 3.12. For my network, I use guessnet to put the right configuration, depending on the place I plug my computer (work, home, etc...). Before Gnome 3.12, NM showed me the list of options (from /etc/network/interfaces) : - Ifupdown (Maison) - Ifupdown (Travail) - etc... Now, it shows me... nothing... And more, it uses DHCP even I'm in a place where the connection should be in static mode... It seems that, at boot, the right connection is configured by guessnet (for exemple Maison) but, just after, NM changes it with DHCP. Do you have any clue for me ? Thank you. David. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: recent update makes me crazy...
So, the solution works until the next boothoping in a quick patch arrival :) L: The only solution worked for me is to remove ifcfg files related to these bridge connections, also I removed the connections from nm-applet and re-created them (or just recreated by restarting networkmanager, I'm not sure) One thing I noticed, in the previous version there was no virtual nic assigned to bridges, but now I have virb[0..4]-nic for each of them Anyway, it is working again this is the most important :) L: ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: recent update makes me crazy...
On 16 July 2014 17:36, Michael Biebl bi...@debian.org wrote: Am 16.07.2014 10:59, schrieb Pal, Laszlo: Hi, One of the recent upgrade continuously trying to destroy my brain by changing my virtual bridge configs... I don't have a very complicated config, one physical ethernet, one wireless and five virtual networks for my KVM machines. It was ok for several months, but after one of the recent update I cannot enable static addressing for my bridges. If I set-up the interface correctly (I mean using static address) and I restart NetworkManager my bridge interfaces are duplicated and NM creates another ones with DHCP enabled... crazy... I'm not sure if this is because virt-manager or nm this is why I post on both list [1] and [2] might be related here. In the Debian package I currently ship [3], to not make NM manage any virtual devices, since I saw a similar behaviour as yours (NM tried to run DHCP on the vbox interfaces). Hope that helps, Michael [1] https://bugzilla.gnome.org/show_bug.cgi?id=731014#c27 [2] https://bugzilla.gnome.org/show_bug.cgi?id=732998 [3] http://anonscm.debian.org/gitweb/?p=pkg-utopia/network-manager.git;a=blob;f=debian/patches/0005-Mark-virtual-ethernet-interfaces-as-unmanaged.patch;hb=HEAD The only solution worked for me is to remove ifcfg files related to these bridge connections, also I removed the connections from nm-applet and re-created them (or just recreated by restarting networkmanager, I'm not sure) One thing I noticed, in the previous version there was no virtual nic assigned to bridges, but now I have virb[0..4]-nic for each of them Anyway, it is working again this is the most important :) L: ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
recent update makes me crazy...
Hi, One of the recent upgrade continuously trying to destroy my brain by changing my virtual bridge configs... I don't have a very complicated config, one physical ethernet, one wireless and five virtual networks for my KVM machines. It was ok for several months, but after one of the recent update I cannot enable static addressing for my bridges. If I set-up the interface correctly (I mean using static address) and I restart NetworkManager my bridge interfaces are duplicated and NM creates another ones with DHCP enabled... crazy... I'm not sure if this is because virt-manager or nm this is why I post on both list Here is my versions Name: NetworkManager Arch: x86_64 Epoch : 1 Version : 0.9.9.1 Release : 4.git20140319.fc20 Installed Packages Name: virt-manager Arch: noarch Version : 1.0.1 Release : 3.fc20 Any idea? Thank you L: ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
