qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Tim <tim-qemu@sentinelchicken.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] TUN settings
Date: Mon, 7 Jun 2004 09:21:57 -0700	[thread overview]
Message-ID: <20040607162157.GA19110@sentinelchicken.org> (raw)
In-Reply-To: <200406071257.34308.hetz@softier.com>

> Here's my /etc/qemu-ifup script (based on what Tim posted):
> 
> !/bin/sh sudo /sbin/ifconfig tun0 192.168.2.200 netmask 255.255.255.0 
> broadcast 192.168.2.255
> sudo sh -c 'echo 1 > /proc/sys/net/ipv4/ip_forward'


on the first line... shouldn't that be broken into two?  
making it look something like:

#!/bin/sh
sudo /sbin/ifconfig tun0 192.168.2.200 netmask 255.255.255.0 broadcast 192.168.2.255
sudo sh -c 'echo 1 > /proc/sys/net/ipv4/ip_forward'


> And yet, I cannot ping the TUN interface in the host (192.168.2.200), and I 
> cannot ping anywhere else.

You probably know all of these things, but it doesn't hurt to check:

 - Your qemu-ifup script is executable by your user, yes?
 - /dev/net/tun exists (`MAKEDEV tun' has been run in /dev ??)
 - /dev/net/tun is writable by your user?
 - Your host OS's real ethernet card is configured to a different
   network than tun0, right?  You aren't going to be able to route (and
   ping may not even work) if you set tun0 and the guest OS to an IP in
   the same network range that your real NIC is a part of.

When QEMU is running, does ifconfig report the correct settings for
tun0?  

pardon me if this stuff is obvious to you,
tim

  parent reply	other threads:[~2004-06-07 16:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-07  9:57 [Qemu-devel] TUN settings Hetz Ben Hamo
2004-06-07 10:13 ` Adrian Smarzewski
2004-06-07 16:21 ` Tim [this message]
2004-06-07 19:14   ` Adrian Smarzewski

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=20040607162157.GA19110@sentinelchicken.org \
    --to=tim-qemu@sentinelchicken.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).