canonical / canonical/multipass
Can't communicate VM from NAT Traversal with driver virtualbox
- Dominant language
- C++
- Stars
- 9.2k
- Forks
- 828
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 43
Description
**Describe the bug**
Can't communicate VM from NAT Traversal with driver virtualbox
**To Reproduce**
System:MacOS Ventury + virtualbox 7.0
firewall:off
DHCP:on
1.multipass set local.bridged-network=en0
2.multipass set local.driver=qemu
3.multipass launch jammy --name ubuntu-q --network en0
4.It works perfectly from local network and NAT Traversal
5.multipass set local.driver=virtualbox
6.multipass launch jammy --name ubuntu-v --network en0
7.It works perfectly from local network, but can't connect this VM from NAT Traversal
**Expected behavior**
NAT Traversal + virtualbox
**Logs**
none
**Additional info**
- OS: macOS 13
sh-3.2# multipass version
multipass 1.12.2+mac
multipassd 1.12.2+mac
sh-3.2# multipass get local.driver
virtualbox
sh-3.2# multipass info --all
Name: ubuntu-v-1p
State: Running
IPv4: 192.168.16.143
Release: Ubuntu 22.04.3 LTS
Image hash: 5bed3f233c24 (Ubuntu 22.04 LTS)
CPU(s): 8
Load: 0.28 0.06 0.02
Disk usage: 1.4GiB out of 193.8GiB
Memory usage: 186.0MiB out of 3.8GiB
Mounts: --
Contributor guide
Research direction
No files, tests, or entry points are named. Reproduce the listed NAT Traversal steps on macOS with the QEMU and VirtualBox drivers, then compare their networking behavior; done means the VirtualBox VM is reachable through NAT Traversal as the QEMU VM is.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100