public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Mateusz Viste <mateusz@viste-family.net>
To: ebiederm@xmission.com
Cc: Stas Sergeev <stsp@list.ru>,
	linux-msdos@vger.kernel.org,
	dosemu-devel <dosemu-devel@lists.sourceforge.net>
Subject: Re: DOSemu networking made easy
Date: Tue, 25 Jun 2013 08:49:20 +0200	[thread overview]
Message-ID: <8fbd00db-16cc-4fd2-8135-0c3c99fcc3a6@email.android.com> (raw)
In-Reply-To: <87a9mfdqid.fsf@xmission.com>

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.

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.

cheers
Mateusz


ebiederm@xmission.com wrote:

>Mateusz Viste <mateusz@viste-family.net> writes:
>
>> Hi
>>
>> I do not think there is any ipv6 support in slirp. But it is not that
>> important I believe, since there is no dos tcp/ip stack with ipv6
>> support :)
>
>I believe tcp/ip with ipv6 support can be had from one of the etherboot
>descendents of gpxe or ipxe.
>
>Ok.  I see what you mean about slirp and qemu.  qemu has forked slirp
>and has an internal version.  The standalone slirp package seems only
>to
>be actively maintained by the debian package maintainers at this point.
>Of course we are talking old stable code here.  I wonder if it would
>make sense for someone to reimport the BSD networking stack into slirp?
>
>At a very basic level I don't know if it is wise to make it easy to
>open up old unmaintained dos executables to the public internet.  But
>unless it becomes common there are unlikely to be anything except
>government level attacks that will target old DOS binaries to break
>into
>your machine so I doubt it is particularly.
>
>With respect to ipv6.  My current swag is 2020 for when ipv6 will have
>achieved effectively universal penetration and some ISPs will stop
>routing legacy ipv4 from their customers across the internet.
>
>Given that what this is about keeping old software on life support for
>a minimal amount of work I don't see any reason to object to the lack
>of
>ipv6 support.  I was mostly curious if this was walking down a
>maintenance dead end.  If slirp updates can be pulled from qemu I don't
>imagine there will be any maintenance problems.
>
>Eric


-- 
Sent from mobile mail.

  reply	other threads:[~2013-06-25  6:49 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 [this message]
     [not found]                   ` <8fbd00db-16cc-4fd2-8135-0c3c99fcc3a6-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>
2013-06-25  7:47                     ` Eric W. Biederman
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=8fbd00db-16cc-4fd2-8135-0c3c99fcc3a6@email.android.com \
    --to=mateusz@viste-family.net \
    --cc=dosemu-devel@lists.sourceforge.net \
    --cc=ebiederm@xmission.com \
    --cc=linux-msdos@vger.kernel.org \
    --cc=stsp@list.ru \
    /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