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

Drop tun/tap requirement? #1

Open
donaldsycamore opened this issue Jul 31, 2016 · 4 comments
Open

Drop tun/tap requirement? #1

donaldsycamore opened this issue Jul 31, 2016 · 4 comments

Comments

@donaldsycamore
Copy link

Have you considered using the "fake network" code from VDE ( http://wiki.v2.cs.unibo.it/wiki/index.php?title=VDE_Basic_Networking#Slirp:_a_virtual_NAT_router_as_a_process ) as an alternative to requiring TUN/TAP?

@vvviperrr
Copy link
Collaborator

Don't even knew about this feature) Seems interesting. I'll research. Thanks for respond.

@donaldsycamore
Copy link
Author

The long history is that back in dial-up days when some people paid for "dial in to a unix shell", SLIRP was a program you could run that spoke SLIP (forerunner to PPP) via stdin/stdout, and translated everything into BSD socket calls. A bit like a userspace transparent proxy. You send it your network traffic, it terminates the TCP sessions, opens equivalent connections with a socket call and copies bytes between the two.

VDE (and QEMU) have both used this to provide a fake network connection to virtual machines -- in their versions, there's a DHCP server in the Slirp process too. This is what lets you run a VM with network access as non-root.

@vvviperrr
Copy link
Collaborator

i see, a bit like lwip project

@randomstuff
Copy link

What's wrong with TUN? We need to be root to create the TUN device but AFAIU it's neeeded to open the USB device anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants