qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: William Greenland <William.Greenland@comlab.ox.ac.uk>
To: esrever_otua@pythonhacker.is-a-geek.net, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Windows Update on guest
Date: Tue, 23 Nov 2004 09:26:09 +0000	[thread overview]
Message-ID: <16803.561.49364.119388@client83.comlab> (raw)
In-Reply-To: <1101121526.3726.4.camel@localhost.localdomain>

Thanks for the responses.  The network connection is "working", but
sadly there is still some subtle brokenness.  I'm beginning to wonder,
though, whether this is Windows being broken rather than QEMU...

I looked at Darryl's earlier post, and used that configuration,
i.e. putting the tun0 interface and guest NIC on a different subnet,
because putting it on the same subnet (192.168.0.xxx) didn't work for
me.

Maybe it's time to give XP a whirl, see if that works any better...

 > contents of qemu-ifup:
 > #!/bin/bash
 > 
 > /sbin/iptables --flush      #Clear out all old rules.  You will want to
 > customise this step.
 > 
 > echo 1 >/proc/sys/net/ipv4/ip_forward       #Enable IP Forwarding for
 > the host OS
 > 
 > /sbin/iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE   #Enable
 > MASQUERADEing on the real eth0 NIC
 > 
 > /sbin/ifconfig $1 192.168.0.254         #Bring up tun0 - guest OS NIC
 > should be on the same subnet with
 >                                         #a different address; tun0
 > should be its gateway.
 > 
 > 
 > After that just manually configure your guest to use a static IP address
 > and some external DNS servers and you're away.
 > 

  reply	other threads:[~2004-11-23  9:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-22 10:05 [Qemu-devel] Windows Update on guest William Greenland
2004-11-22 10:14 ` Hetz Ben Hamo
2004-11-22 10:43   ` William Greenland
2004-11-22 11:05     ` Darryl Dixon
2004-11-23  9:26       ` William Greenland [this message]
2004-11-22 14:21 ` Joshua Root
     [not found] <41A21B63.2070104@acwsinc.net>
2004-11-22 19:20 ` Darryl Dixon

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=16803.561.49364.119388@client83.comlab \
    --to=william.greenland@comlab.ox.ac.uk \
    --cc=esrever_otua@pythonhacker.is-a-geek.net \
    --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).