public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stsp@aknet.ru>
To: linux-msdos@vger.kernel.org
Subject: Re: understanding TUN/TAP
Date: Wed, 14 Jan 2004 20:18:15 +0300	[thread overview]
Message-ID: <400579D7.6050805@aknet.ru> (raw)

Hello.

Grigory Batalov wrote:
> So after "ifup tap0" I have:
Looks about all-right.

> But not from host to dosemu:
Most likely because the TCP/IP stack
on a dosemu side is not loaded by the
time you are pinging it. Try pinging
linux->dosemu at the same time you are
pinging dosemu->linux, because when
you are pinging dosemu->linux, the
TCP/IP is loaded, but then it gets
unloaded.

> If I start bridging between tap0 and eth0 then I even can't
> ping host from dosemu:
That's right. As soon as you start
bridging on some interface, this
interface became unavailable for TCP/IP.
Therefore it is suggested to not even
assign an IP address to the interface
that is used for the bridging.
Although it is possible to make the
linux box available for the same subnet
again after the bridging was started,
it is rather tricky and lets hope you
don't need that.

> So my question is: where am I wrong and what also should
> be tuned?
For the case of a bridging, after you
created br0 interface, you have to bring
it up with ifconfig to activate the
bridge (or create ifcfg-br0 config).

             reply	other threads:[~2004-01-14 17:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-14 17:18 Stas Sergeev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-14 11:48 understanding TUN/TAP Grigory Batalov

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=400579D7.6050805@aknet.ru \
    --to=stsp@aknet.ru \
    --cc=linux-msdos@vger.kernel.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