All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jesus M. Salvo Jr." <jesus.salvo@migasia.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Help with tun/tap with qemu
Date: Wed, 11 Aug 2004 12:50:37 +1000	[thread overview]
Message-ID: <4119897D.8030001@migasia.com> (raw)
In-Reply-To: <4119885E.3020002@migasia.com>

Jesus M. Salvo Jr. wrote:

> Antony T Curtis wrote:
>
>> On Tue, 2004-08-10 at 16:50, Bartosz Fabianowski wrote:
>>  
>>
>>>> So I am trying TUN/TAP.  The guest and host OS can ping each other.
>>>> However, the guest OS cannot ping any other host
>>>>     
>>>
>>> If the setup on Linux is any similar to that on FreeBSD (and I am 
>>> sure it is), the problem probably is routing. The guest and host are 
>>> on different networks. So, you need to tell your host to forward 
>>> packets to and from the guest's network. You didn't have that 
>>> problem in slirp, because slirp bridges between the two networks for 
>>> you, it implicitly does the forwarding.
>>>
>>> Unfortunately, I can't tell you how to add the route under Linux due 
>>> to my lack of experience with that platform.
>>>
>>> - Bartosz
>>>   
>>
>>
>> When I am using TAP on FreeBSD, I use ng_bridge so the guest is on the
>> same network as the host.
>>
>> Info for configuring ng_bridge is in
>> /usr/share/examples/netgraph/ether.bridge
>>
>>  
>>
> OK, I have now setup a bridge on linux as follows.
> On the host OS, I have the following script and ran it as root:
>
> #!/bin/sh
> /usr/sbin/brctl addbr br0
> /sbin/ifconfig eth2 0.0.0.0 promisc up
> /sbin/ifconfig tap0 0.0.0.0 promisc up
> /sbin/ifconfig br0 192.168.0.199 netmask 255.255.255.0 broadcast 
> 192.168.0.255 up
> /usr/sbin/brctl stp br0 off
> /usr/sbin/brctl setfd br0 1
> /usr/sbin/brctl sethello br0 1
> /usr/sbin/brctl addif br0 eth2
> /usr/sbin/brctl addif br0 tap0
> /sbin/route add default gw 192.168.0.1
>
> I can confirm that the host still has network connectivity using the 
> bridge.
>
> Now the question is, what to do on the qemu side ?? 

Not clear enough.
What I have done so far on the guest OS side is:

/sbin/ifconfig eth0 192.168.0.98 up
/sbin/route add default gw 192.168.0.1

However, the host and guest OS could not ping each other.

Also, how does one setup a bridge in the case where one only has a 
dial-up modem to the ISP, where all I have on the host OS is a ppp 
interface ?

  reply	other threads:[~2004-08-11  2:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10 15:06 [Qemu-devel] Help with tun/tap with qemu jesus.salvo
2004-08-10 15:50 ` Bartosz Fabianowski
2004-08-10 18:52   ` Antony T Curtis
2004-08-11  2:45     ` Jesus M. Salvo Jr.
2004-08-11  2:50       ` Jesus M. Salvo Jr. [this message]
2004-08-11  5:10       ` Jesus M. Salvo Jr.

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=4119897D.8030001@migasia.com \
    --to=jesus.salvo@migasia.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.