Virtualbox not able to see network in yakkety

[Joe Barnett]

Having some trouble with a windows host inside virtualbox's ability to see the network since upgrading to yakkety.

Attaching it as NAT used to work, but now results in a mostly un-navigable internet. Attaching as a bridged adapter works better at times, but reports an IP conflict. Eventually switching back and forth between the two results in a usable internet, but something's not quite right....

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: virtualbox 5.1.6-dfsg-2
ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
Uname: Linux 4.8.0-21-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Oct 10 12:46:05 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-08-21 (416 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: virtualbox
UpgradeStatus: Upgraded to yakkety on 2016-09-29 (11 days ago)

[Gianfranco Costamagna (costamagnagianfranco)]

I would wild guess that you have some network issue regardless of virtualbox, e.g. duplicate ip address might mean bad dhcp or some device with a static ip address

[Joe Barnett (thejoe)]

it's only within the virutalbox windows OS that the duplicate ip is reported, and only in bridged mode, and it happens on multiple differenlty-configured networks that otherwise work fine.

when in NAT mode, it _feels_ similar to an issue I reported in steam (https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1631980) which was resolved by installing libnss-resolv:i386. however, it still occurs. is the virtualbox hosted OS unable to connect to the 127.0.0.53 systemd-resolved nameserver somehow?

[Gianfranco Costamagna (costamagnagianfranco)]

Just shutdown the network and look for a duplicate ip address (nmap, ping or whatever).
If you can't debug your network, I'm afraid I can't help too much.
127.0.0.53 is a localhost address, so you can't probably see it from inside the virtualbox machine in case you are exposing such service from the host.
Probably some hacky static network rule might help, but without nmap scan logs I can't help further.

[Launchpad Janitor (janitor)]

[Expired for virtualbox (Ubuntu) because there has been no activity for 60 days.]