On 06/28/2013 07:12 PM, Stas Sergeev wrote:
> But there may be new features added, like pings.
> There are the efforts to allow pings/icmp without a root
> requirement:
> http://lwn.net/Articles/420801/
> Not sure if that happened already or not.
Sure, there is plenty of features we can imagine in the feature :)
I'd say then that a simple design would be:
if $_netdev is empty (or undefinied), then we use an internal, embedded
slirp for user-friendliness, else we use the one specified in $_netdev.
This would have the benefit of providing a DOSemu internet connectivity
that works out of the box, and, for super-users, the possiblity to call
their own version of slirp, or any other SLIP-compatible app.
>> Having a setting named naively 'nat' that says 'check this and you
>> will have a working internet connectivity' is, IMHO, much more sexy
> But why would we call it a nat, if it is not nat by any means?
That's just an example.. anything that is easy to understand is fine.
And from the user point of view, a SLIRP channel is seen exactly as it
would be a virtual NAT mechanism, even if it's technically totally
untrue, and much more complex. BTW, that's exactly how VirtualBox call
their slirp-powered networking ("NAT").
> The main point is to see if maybe VDE also has everything
> _you_ wrote (I mean librouter). Then there could be fewer
> additions to dosemu itself.
I see, you mean the DHCP server and ARP interceptor. I see various
mentions about DHCP in the slirpvde code, so they seem to handle this,
too (and ARP proxy for sure as well, otherwise it couldn't work).
So for DOSemu it might be 'less additions', because it would require
only to encapsulate frames into whatever container VDE expects, and
handing it to them for processing.
> If VDE does not replace any of your code, then I immediately
> stop talking about it. :) (since anyway it doesn't seem to have
> any advantages on other fronts too)
Well, it does replace pretty much all of my code - since both librouter
and vdeslirp do the same thing. The main difference is that they embed
the slirp code from qemu, while I call the standalone slirp app instead.
> Maybe VDE can also be integrated?
I'm pretty sure it can. But I have no idea at what development cost :)
C ya
Mateusz
------------------------------------------------------------------------------
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
