From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman)
To: Mateusz Viste <mateusz-IMIDigHRhuggabnWlOdIvg@public.gmane.org>
Cc: dosemu-devel
<dosemu-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
linux-msdos-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: DOSemu networking made easy
Date: Tue, 25 Jun 2013 00:47:17 -0700 [thread overview]
Message-ID: <87txkmbpiy.fsf@xmission.com> (raw)
In-Reply-To: <8fbd00db-16cc-4fd2-8135-0c3c99fcc3a6-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org> (Mateusz Viste's message of "Tue, 25 Jun 2013 08:49:20 +0200")
Mateusz Viste <mateusz-IMIDigHRhuggabnWlOdIvg@public.gmane.org> writes:
> I think there is no point refreshing the bsd stack used in slirp (iirc
> it uses the stack of a 4.4 bsd), because it is used only between slirp
> and dosemu anyway. Between slirp and the outside world only 'normal'
> host's sockets are used.
I did not mean in the context of dosemu. I meant more in the context of
qemu and places where applications will start caring. Depending on the
network stack it should not be too difficult to get ipv6 support in
there as well.
> Anyway, as a 1st step I will transform taprouter into an easy-to-link
> module. Then, I will look how to integrate it into DOSemu.
Sounds good.
I am inclined to look at some of this for the context of lxc so we can
have unprivileged containers that have packets that go out the host
network stack. ;-) Now that I know what the trick qemu uses.
Eric
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
next prev parent reply other threads:[~2013-06-25 7:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 11:36 DOSemu networking made easy Mateusz Viste
2013-06-24 13:23 ` Stas Sergeev
2013-06-24 13:50 ` Mateusz Viste
2013-06-24 15:00 ` Stas Sergeev
2013-06-24 15:38 ` Mateusz Viste
2013-06-24 16:12 ` Stas Sergeev
2013-06-24 19:58 ` Eric W. Biederman
2013-06-24 20:42 ` Stas Sergeev
2013-06-24 22:04 ` Mateusz Viste
2013-06-25 7:03 ` Stas Sergeev
2013-06-25 7:33 ` Mateusz Viste
2013-06-25 8:27 ` Eric W. Biederman
[not found] ` <87zjue8ujo.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2013-06-25 11:43 ` Stas Sergeev
2013-06-25 9:48 ` Stas Sergeev
2013-06-25 11:16 ` Eric W. Biederman
2013-06-25 13:30 ` Mateusz Viste
2013-06-24 21:47 ` Mateusz Viste
2013-06-24 23:43 ` Eric W. Biederman
2013-06-25 6:49 ` Mateusz Viste
[not found] ` <8fbd00db-16cc-4fd2-8135-0c3c99fcc3a6-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>
2013-06-25 7:47 ` Eric W. Biederman [this message]
2013-06-25 7:13 ` Stas Sergeev
2013-06-25 7:57 ` Eric W. Biederman
2013-06-25 9:45 ` Stas Sergeev
2013-06-24 14:40 ` Mateusz Viste
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87txkmbpiy.fsf@xmission.com \
--to=ebiederm-as9lmozglivwk0htik3j/w@public.gmane.org \
--cc=dosemu-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-msdos-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mateusz-IMIDigHRhuggabnWlOdIvg@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox