From: Stas Sergeev <stsp@list.ru>
To: Mateusz Viste <mateusz@viste-family.net>
Cc: linux-msdos@vger.kernel.org
Subject: Re: DOSemu networking made easy
Date: Mon, 24 Jun 2013 19:00:52 +0400 [thread overview]
Message-ID: <51C85F24.9050809@list.ru> (raw)
In-Reply-To: <51C84EB4.3070000@viste-family.net>
24.06.2013 17:50, Mateusz Viste пишет:
> Hi Stas!
>
> No, it's not naive at all :). And my descriptions are probably lacking
> a fair amount of clarity.
>
> > actually solve? I can see some advantage of this over
> > the bridging tap0 with eth0 solution,
>
> Bridging tap0 with eth0 requires that:
> - there is a DHCP server somewhere in the network
> - you are actually using always eth0 (and not wlan0 for instance when
> on the road, and eth0 when at home, etc)
True.
There seem to be the project to solve this:
http://fedoraproject.org/wiki/Features/NetworkManagerBridging
> I hope it's a bit clearer now :) Let me know.
Thanks for the picture you added to the page.
I was actually just writing a mail asking you to do something
like this pict. :)
So basically the static DNS and static gateway are only
needed to allow the configuration without DHCP? Maybe
it is not worth the troubles, and only the DHCP-based
configuration can be left? I mean if you (or anyone else)
is going to port that inside dosemu, that may be easier.
But then, remove the static configuration, and suddenly
not too much is left at all. :)
Could you please explain a little more how NAT+slirp work
in that scenario? What was the task of slirp, is there no
other way to deal with the raw IP packets?
--
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-06-24 15:00 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 [this message]
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
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=51C85F24.9050809@list.ru \
--to=stsp@list.ru \
--cc=linux-msdos@vger.kernel.org \
--cc=mateusz@viste-family.net \
/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