All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arne Bernin <arne@alamut.de>
To: qemu mailing list <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Question about tun/tap networking
Date: Mon, 03 May 2004 23:31:34 +0200	[thread overview]
Message-ID: <1083619894.3425.1.camel@localhost> (raw)
In-Reply-To: <20040503202233.GB8530@jbrown.mylinuxbox.org>

On Mon, 2004-05-03 at 22:22, Jim C. Brown wrote:

> [/space/qemu/qemu-0.5.4/ $] su root
> [/space/qemu/qemu-0.5.4/ #] vde_switch -daemon -tap tap0
> [/space/qemu/qemu-0.5.4/ #] ifconfig tap0 192.168.1.254
> [/space/qemu/qemu-0.5.4/ #] chmod 777 /tmp/vde.ctl
> [/space/qemu/qemu-0.5.4/ #] exit
> [/space/qemu/qemu-0.5.4/ $] vdeq qemu -hda disk1.img
> 
> This works, not only can I ping 2 different machines on the vde, I can also
> ping the LAN from the vde, and vice versa. (ifconfig seems to set up
> routing automagicly. Or was it something I put into shorewall...)
> 
> Note that for teh guest OS, you need to set up 192.168.1.254 as the default gateway
> for just about everything.
> 

thanks, it is working now, just had some wrong firewall settings on the
guest OS linux boxes....

--arne

  reply	other threads:[~2004-05-03 21:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-03  3:09 [Qemu-devel] Question about tun/tap networking 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 [this message]
     [not found] <200406230754.07821.pjr@ucar.edu>
2004-06-23 17:03 ` Jim C. Brown
2004-06-23 17:15   ` Phil Rasch
2004-06-23 17:16   ` Gianni Tedesco
2004-06-23 19:32     ` Jim C. Brown
  -- 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=1083619894.3425.1.camel@localhost \
    --to=arne@alamut.de \
    --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.