Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: use TCP/IP emulator for providing access to network #108

Open
dadada opened this issue Feb 23, 2024 · 0 comments
Open

feat: use TCP/IP emulator for providing access to network #108

dadada opened this issue Feb 23, 2024 · 0 comments

Comments

@dadada
Copy link
Collaborator

dadada commented 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.

@dadada 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant