You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now access to network destinations is provided using individual UDP or TCP sockets that are connected / bound inside the hypervisor and passed to partitions using UNIX domain sockets. This has the limitation of only ever allowing existing connections to the target from at the time the hypervisor started. With something like slirp it would be possible to provide a (limited) TCP/IP stack to partitions. This is how QEMU and rootless podman do it by default.
The text was updated successfully, but these errors were encountered:
dadada
changed the title
feat: use TCP/IP virtual machine for providing access to network
feat: use TCP/IP emulator for providing access to network
Feb 23, 2024
Right now access to network destinations is provided using individual UDP or TCP sockets that are connected / bound inside the hypervisor and passed to partitions using UNIX domain sockets. This has the limitation of only ever allowing existing connections to the target from at the time the hypervisor started. With something like slirp it would be possible to provide a (limited) TCP/IP stack to partitions. This is how QEMU and rootless podman do it by default.
The text was updated successfully, but these errors were encountered: