[Bug 1632084] Re: Virtualbox not able to see network in yakkety

2016-12-16 Thread Launchpad Bug Tracker
[Expired for virtualbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: virtualbox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1632084] Re: Virtualbox not able to see network in yakkety

2016-10-17 Thread LocutusOfBorg
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

[Bug 1632084] Re: Virtualbox not able to see network in yakkety

2016-10-16 Thread Joe Barnett
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

[Bug 1632084] Re: Virtualbox not able to see network in yakkety

2016-10-10 Thread LocutusOfBorg
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 ** Changed in: virtualbox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member