All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gianni Tedesco <gianni@scaramanga.co.uk>
To: jbrown106@swift-mail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Question about tun/tap networking
Date: Wed, 23 Jun 2004 18:16:32 +0100	[thread overview]
Message-ID: <1088010992.30210.58.camel@sherbert> (raw)
In-Reply-To: <20040623170325.GB22835@jbrown.mylinuxbox.org>

[-- Attachment #1: Type: text/plain, Size: 487 bytes --]

On Wed, 2004-06-23 at 13:03 -0400, Jim C. Brown wrote:
> That is tricky. You will need to look into bridging.

There are a few ways to do it:
 o static nat
 o iptables nat
 o bridging

Try this qemu-ifup for script for the iptables method:

	http://www.scaramanga.co.uk/stuff/qemu-ifup

-- 
// Gianni Tedesco (gianni at scaramanga dot co dot uk)
lynx --source www.scaramanga.co.uk/scaramanga.asc | gpg --import
8646BE7D: 6D9F 2287 870E A2C9 8F60 3A3C 91B5 7669 8646 BE7D

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-06-23 17:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200406230754.07821.pjr@ucar.edu>
2004-06-23 17:03 ` [Qemu-devel] Question about tun/tap networking Jim C. Brown
2004-06-23 17:15   ` Phil Rasch
2004-06-23 17:16   ` Gianni Tedesco [this message]
2004-06-23 19:32     ` Jim C. Brown
2004-05-03  3:09 Jim C. Brown
2004-05-03 11:45 ` Arne Bernin
2004-05-03 12:59   ` Renzo Davoli
2004-05-03 13:12     ` Renzo Davoli
2004-05-03 14:05     ` Renzo Davoli
2004-05-03 20:22   ` Jim C. Brown
2004-05-03 21:31     ` Arne Bernin
  -- strict thread matches above, loose matches on Subject: below --
2004-05-03  1:13 Arne Bernin
2004-05-03  1:35 ` nhand42
2004-05-03  9:27   ` Carlos Valiente

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=1088010992.30210.58.camel@sherbert \
    --to=gianni@scaramanga.co.uk \
    --cc=jbrown106@swift-mail.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.