[Bug 1632084] Re: Virtualbox not able to see network in yakkety
[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. https://bugs.launchpad.net/bugs/1632084 Title: Virtualbox not able to see network in yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1632084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632084] Re: Virtualbox not able to see network in yakkety
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. ** Changed in: virtualbox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632084 Title: Virtualbox not able to see network in yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1632084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632084] Re: Virtualbox not able to see network in yakkety
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? ** Changed in: virtualbox (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632084 Title: Virtualbox not able to see network in yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1632084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632084] Re: Virtualbox not able to see network in yakkety
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 of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632084 Title: Virtualbox not able to see network in yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1632084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
