From: Mateusz Viste <mateusz@viste-family.net>
To: Stas Sergeev <stsp@list.ru>
Cc: linux-msdos@vger.kernel.org
Subject: Re: DOSemu networking made easy
Date: Mon, 24 Jun 2013 16:40:48 +0200 [thread overview]
Message-ID: <51C85A70.9090109@viste-family.net> (raw)
In-Reply-To: <51C84847.60903@list.ru>
Hi again,
Added a little schema that shows how taprouter interacts with the linux
bridge, dosemu, tap interfaces and slirp...
http://www.viste-family.net/mateusz/software/taprouter/
Not sure it makes the whole thing looking less of a contraption, though :P
The silver bullet would be to integrate all this mess into DOSemu (ie de
facto implementing a 'user network' like in qemu/bochs/vbox), but that's
something I unfortunately don't have enough time for.
Mateusz
On 06/24/2013 03:23 PM, Stas Sergeev wrote:
> 24.06.2013 15:36, Mateusz Viste пишет:
>> Hi all,
>>
>> I'm happily using DOSemu since a long time now, and the one thing that
>> has always been bothering me is the complicated networking settings.
>> Playing with bridging and masquerading and transforming the host into
>> a routing machine is usually fine on a home desktop PC, but it becomes
>> a real pain on a laptop which, by nature, often change it's network
>> settings and physical locations.
>>
>> This is why I wrote a tool to make DOSemu networking much easier (at
>> least from my POV): taprouter.
> Hi!
>
> Maybe a naive question, but, what problem does it
> actually solve? I can see some advantage of this over
> the bridging tap0 with eth0 solution, but what advantage
> does it give over the static route with masquerading solution?
>
> You seem to be saying that the dosemu's networking
> configuration tends to change when you relocate your
> laptop - I can agree with this if we talk about bridging,
> but is it still true for the routing case?
>
> I think I can just install a generic DHCP server and dosemu
> will be able to reach it. Also, if tap0 is bridged with eth0,
> dosemu will be able to reach an outer DHCP server.
> Is this not true?
>
> I am not sure what does this mean:
> ---
> taprouter expects you to use the IP address 10.0.2.1 as a default gateway
> ---
> you mean default gateway for dosemu or what?
>
> Why your tool itself need a tap device?
>
> Sorry, I am just a bit lost. :)
> Never used dosemu with DHCP, but I haven't expected there
> are any problems that need an extra tool to solve.
> --
> 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
>
--
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
prev parent reply other threads:[~2013-06-24 14:40 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
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 [this message]
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=51C85A70.9090109@viste-family.net \
--to=mateusz@viste-family.net \
--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