The ifupdown configuration is working for me now, so for me this has
been resolved.
I'm not sure what changed or when.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
I'm experiencing exactly the same thing as the other report.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1485558
Title:
NetworkManager breaks vboxnet*
It seems the 15.04 version of network manager (0.9.10) is now quite out-
of-date (!).
https://wiki.gnome.org/Projects/NetworkManager/
From
https://download.gnome.org/sources/NetworkManager/1.0/NetworkManager-1.0.4.news
* The management of devices can now be controlled with udev rules. The veth
Attached - what the network manager applet now looks like.
All my VPN connections are off the bottom of my screen, so I currently
have to use 'nmcli' from a terminal to control them :(
** Attachment added: network-panel-issue.png
** Changed in: network-manager (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1485558
Title:
NetworkManager breaks
Summary: more trouble, nm-applet menu starts to fill with irrelevant
vboxnet0 entries.
Details
Now nm-applet shows 5 vboxnet0 ethernet connections, though I've not
created any of them. 4 of them show ipv4 parameters disabled, ipv6
parameters ignore. Only the currently auto-activated one shows
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
I tried this variant to tell NetworkManager to ignore the virtual
devices:
[keyfile]
unmanaged-devices=mac:xx:xx:xx:xx:xx:xx
(using the real MAC address of course)
It still does not change anything.
But I noticed this in the log, which happen whether or not the
unmanaged-devices option is set:
I unchecked the auto-connect option on connection 'Auto SG IP auto' to
see if it changes anything.
The behavior is different but satisfying.
Again, on suspend of the host, NetworkManager disables vboxnet0.
It just does not do DHCP on it.
Again, suspending the resuming the virtual machine repairs
Oops I sent The behavior is different but satisfying.
It meant: The behavior is different but not satisfying.
Summary: somehow NetworkManager has very well understood (as shown in
log) that vboxnet* interfaces should be ignored, but somehow it still
manages them.
--
You received this bug
I tried to move away all connections in /etc/NetworkManager/system-connections/
then restart network-manager, just in case configuration somehow confused it.
Problem still happens.
Thank you for your attention.
--
You received this bug notification because you are a member of Ubuntu
Touch
11 matches
Mail list logo
