Public bug reported:
I'm not sure if it is ubuntu xenial Kernel or something that does NM,
but if you disconnect the ethernet cable, you network lan card stops
working for everything.
This might seem obvious, but if you are working with your laptop/pc
developing a network service running on your local IP (attached to the
ethernet), it stops working because it cannot bind that address. At the
same time, if you are running a VirtualBox solution that is bridging all
instances with that ethernet interface, you can no longer reach those
interfaces because ARP level is disabled (that is, the network interface
stops replying to ARP queries)...however, you can still communicate
between VMs.
That is, there's nothing that should stop you from reaching a local
service attached to the ethernet interface as long as you are sending
that traffic from the system itself. At the same time, if you try to
reach your VMS (on the virtualbox), you should be able doing so even
though you don't have the ethernet cable plugged.
Another interesting element to consider is that if you run a tcpdump on
the ethernet (with the cable disconnected) and you try to communicate
from a VM) you can see ARP packages arriving, but they aren't replied.
Please, let me know if you need any additional detail, command's output
or something similar,
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1585675
Title:
Network manager clears configuration and takes ethernet cable down
when cable is unplugged
Status in network-manager package in Ubuntu:
New
Bug description:
I'm not sure if it is ubuntu xenial Kernel or something that does NM,
but if you disconnect the ethernet cable, you network lan card stops
working for everything.
This might seem obvious, but if you are working with your laptop/pc
developing a network service running on your local IP (attached to the
ethernet), it stops working because it cannot bind that address. At
the same time, if you are running a VirtualBox solution that is
bridging all instances with that ethernet interface, you can no longer
reach those interfaces because ARP level is disabled (that is, the
network interface stops replying to ARP queries)...however, you can
still communicate between VMs.
That is, there's nothing that should stop you from reaching a local
service attached to the ethernet interface as long as you are sending
that traffic from the system itself. At the same time, if you try to
reach your VMS (on the virtualbox), you should be able doing so even
though you don't have the ethernet cable plugged.
Another interesting element to consider is that if you run a tcpdump
on the ethernet (with the cable disconnected) and you try to
communicate from a VM) you can see ARP packages arriving, but they
aren't replied.
Please, let me know if you need any additional detail, command's
output or something similar,
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1585675/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
