search

Nitrux / nitrux-bug-tracker

Bug Repository for Nitrux
https://nxos.org
5 stars 2 forks source link

There's no network connectivity with live ISO on Virtualbox 7.0.x when using bridged networking #181

Open sirg opened 2 months ago

sirg commented 2 months ago

Issue Description

Unable to get any network connectivity from live ISO under Linux Mint/Virtualbox 7.0.18. Similar results reported with Windows/VB 7.0.10. Similar behavior with NAT and Bridged Adapter. But no issues with KVM.

Please make sure to include a clear and concise description of what the bug is.

Steps to reproduce the bug

  1. Configure VirtualBox VM as generic or Debian Linux/64 bit, 8GM memory, 20GB disk, nitrux-nx-desktop-plasma-65624aeb-amd64.iso
  2. Boot the VM
  3. Observe multiple warnings and indications of lack of network connectivity

Expected behavior Working networking by default, like with many other VMs.

Additional context

Tried to turn off NetworkManager and manually config the link up with a static address. No response to ping from local router or the host. Exact same approach works fine on other VMs.

OS version and Desktop information Mint 21.3, but same results seen on Win 10 with VirtualBox 7.0.10.

Open System Settings, go to About System, click "Copy to clipboard in English," and paste the content here. Attached: about-nitrux.png about-nitrux

Please advise what specific additional info is needed and how to extract it w/o network connectivity. I guess I could configure a local virtual disk, save data to it and mount/read it on the host afterwards.

UriHerrera commented 2 months ago

Duplicate of #177

sirg commented 2 months ago

I do not believe this is a duplicate of #177: it's not a name resolution issue. The system fails to exhibit any connectivity with the host LAN - ARP, ping, DHCP all fail.

UriHerrera commented 2 months ago

You're right, it isn't a duplicate of that issue. I booted the ISO in VBox 7.0.18 r162988, and networking works when using NAT and all of the adapters except virtio-net which may require adding modules to the initram and rebuilding it.

Selecting a bridged network does indeed not work with any of the adapters.

sirg commented 2 months ago

HTH, to get networking to work with NAT after trying bridged, I had to switch back-and-forth between adapter types. Once you can ping something by IP, you still need to fix DNS per #177 to get full functionality (just commenting out the nameserver line in /etc/resolv.conf works)