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). With the difference that slirpvde ripped most of its code from Qemu, while I implemented the whole DHCP/ARP/IP connectivity myself. I haven't looked at slirpvde6, though (but I don't really believe IPv6 should be of any concern to DOSemu anyway).
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. 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() just before calling slirp_main(). This would allow to have a totally standalone 'nat-like' setting inside DOSemu, where the user would just have to set '$_vnet=nat' have an immediately working internet connectivity. This would be magic. :) Mateusz On 06/28/2013 04:42 PM, Stas Sergeev wrote: > There seems to be some project called slirpvde: > http://wiki.virtualsquare.org/wiki/index.php/VDE#slirpvde > and with IPv6 support, it seems. > Does anyone have a clue on that? > Looks like it can understand the ethernet frames directly, > then no need to slip. And there is already some dhcp support > in it etc. Can this be of any use for dosemu? > ------------------------------------------------------------------------------ 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
