From: Stas Sergeev <stssppnn@yahoo.com>
To: Peter Eckhardt <peter@dadi-linux.de>
Cc: linux-msdos@vger.kernel.org
Subject: Re: DOSEMU SPX PDETHER SOLVED!!!!
Date: Wed, 29 Oct 2003 22:44:15 +0300 [thread overview]
Message-ID: <3FA0188F.4010604@yahoo.com> (raw)
Hello.
Peter Eckhardt wrote:
> Sorry for late answer, i am quite busy at the moment ...
OK, thanks for the reply.
Although it is not polite to CC the
private replies to the public list, I am
doing that in hope that your info may be
usefull for others (hope you don't mind,
but please CC the list next time if there
is nothing private).
>> used tunctil). You have probably brought it
>> up with ifconfig?
> looks as if persistent tap devices were already present. I simply used
> ifconfig tap0 up.
Yes, that's what I had in mind. The
persistent tap devices were *not* present
and that's why you had to use ifconfig to
bring them up. Dosemu can either create a
new TAP device in a "down" state (your case)
or bind to a persistent TAP device that may
be already "up" (or may not).
>> Also it is not clear how have
>> you connected the TAP interface with an outside
>> world.
> I have patched the ipxbridge makefile to bridge between eth0 and tap0.
The general strategy is to use the brctl
for that. Are there any reasons to use the
patched ipxbridge instead?
I am also wondering if it is possible to
establish some routing. I think with help
of the ipx_route and ipx_interface utilities
it is possible to avoid the bridging entirely.
Can this please be verified?
Asking this all I am only thinking about
fulfilling the gaps in your previous description,
because dealing with TAPs is the only untrivial
thing there and you forgot to describe it.
next reply other threads:[~2003-10-29 19:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 19:44 Stas Sergeev [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-24 17:06 DOSEMU SPX PDETHER SOLVED!!!! Stas Sergeev
2003-10-24 7:28 Peter Eckhardt
2003-10-24 8:27 ` Bart Oldeman
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=3FA0188F.4010604@yahoo.com \
--to=stssppnn@yahoo.com \
--cc=linux-msdos@vger.kernel.org \
--cc=peter@dadi-linux.de \
/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