28.06.2013 19:11, Mateusz Viste пишет: > After a quick look, I see that slirpvde is to VDE what my taprouter is > to TAP interfaces (that is, a glue between a layer 2 architecture - > TAP/VDE - and a layer 3 tunnel provided by slirp). How would you then interpret this: --- vde_plug2tap is another plug tool that can be connected to vde_switches. Instead of using standard input and standard output for network I/O everything that come from vde_switch to the plug is redirected to the specified tap interface. --- So to me it seems like they normally use stdio instead of tap, hence doing everything in userspace. IMHO its worth taking a look into that.
> Another interesting thing about slirpvde is they embed slirp's code > (that's is, Qemu does it). This is something that would be actually > pretty great for DOSemu. This has the downsides too. dosemu releases are so infrequent that the new features of slirp, if any, will be delayed for too long. IF vde have some better availability in the repos, then my vote will be with it.... but it doesn't seem to be the case. :) > I was looking today at slirp, but haven't succeeded to compile it for > some obscure reasons. The idea was to try to compile it, changing > main() by some main_slirp() function that I could call then from > within DOSemu, and communicate with the slirp core via fake > stdin/stdout that I'd dup2() Not directly related to you problem, but see if pty suits better for your needs then socketpairs etc. It usually always does. ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Dosemu-devel mailing list Dosemu-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dosemu-devel
